socialmedialkp.blogg.se

Codejock in spanish
Codejock in spanish









codejock in spanish

When I feed in 16 or 32 pixel icons and enable this option, the command war will do what with these icons? I want to avoid blurry icons. PCommandBars->GetPaintManager()->m_bAutoResizeIcons = TRUE So far unfortunately only if you work on monitors with 96 DPI - which seem to die out quickly. I consider the (albeit limited) XAML support in XTP indeed as a great feature, because it makes a lot of things easier or more flexible. Using pixel values for these measurements makes it impossible to write XAML markup that adapts to different DPI settings in the output device context. I would also very much like to have the ability in markup to use point sizes (or maybe something like 'em)' for Margins, Padding etc. You have hard-coded 96 DPI in your XAML source code. to match the DPI of the output device context. So far I need to manually parse all XAML produced by my users and manually correct the font sizes etc. I'm also looking forward to proper DPI-aware XAML code.

codejock in spanish

I really hope that your new update gets all this fixed without breaking existing code. This is annoying for me and the customers, and expensive as well. My code automatically adapted to all high-DPI screens, but I had to spend far too much time making XTP work - and in some places could not make it work at all. No way to change them, even if my application is configured to use 32 or even 64 pixel icons. Panel icons use a hard-coded size of 16 pixels. Maybe using the default Windows control font size or the menu font size would be better.

codejock in spanish

As far as I could tell, this control uses a font derived from the system icon font (?) and so should work. Just had the case today that a CXTPControlComboBox on a 200% screen produces unreadable text because each line folds half-way into the previous line. Having 3200 pixels on a 13" screen (Dell) is no fun if the application you work with messes up the font sizes. Many of my users work on screens with 150% to 250% (144 - over 200 DPI, compared to the 96 DPI you hardcoded in several places). I'm really waiting for the numerous High-DPI fixes you have promised. But since I don't use it, I'm looking forward to the other promised changes in the next release.











Codejock in spanish