LJN-hzleaper

Results 5 issues of LJN-hzleaper

I have some C++ code from someone else: ``` cv::FileStorage df(FeaturesXMLPath.toStdString(), cv::FileStorage::WRITE); std::vector contour; ... df

I bind PropertyGrid(in ListBox ItemTemplate) PropertyDefinitions to a PropertyDefinitionCollection in my viewmodel, but I find the binding does not work, the PropertyDefinitionCollection of all PropertyGrid is empty, and all PropertyGrid...

In my demo app, ExcelMapper always output extra columns that I dont't want. How to prevent it? ``` ExcelMapper mapper = new(); mapper.AddMapping(typeof(Dto), "Identity", nameof(Dto.Id)); mapper.AddMapping(typeof(Dto), "User Name", nameof(Dto.Name)) .ToExcelOnly();...

If I set Window.DataContext in code behind, everything is ok: ``` public MainWindow() { InitializeComponent(); DataContext = new MainViewModel(); } ``` But if I set Window.DataContext in xaml instead, CanClose...

If 5-level paging is enabled, 16-bit local count will overlap 57-bit address part, which will corrupt memory. Am I right? If so, how does the atomic_shared_ptr class handle this problem?