We have a legacy thick client product with windows forms initially designed using NetAdvantage 2004 Vol2 and NetAdvantage Ultimate 2011 Vol2. On later versions of Windows 10, the font in our results grid appears different from the MS Sans Serif we are accustomed to seeing, and when a cell is selected, WingDings are displayed. We do not explicitly set any specific font. The only thing we ever set font-wise is to either bold and set a font color so it has been a little difficult to step through the control intitialization and see why it is rendering differently. I do not see where the font is being applied or changed during initialization or event handling. This only seems to affect environments running version 1803 (Creator Update) of Windows 10. Older versions of Windows 10 and all versions of Windows 7 are unaffected. I've attempted to update the font in the grid in the Display Layout Appearance section, but it does not make any difference. The grid's font property is set to Microsoft Sans Serif, 8.25pt in Visual Studio properties page. This is happening across the entire thick client, 100's of forms, not just a few few forms.
Is there possibly a default native font defined in Infragistics that is not available in Windows 10 update? Looking at my Surface Tablet which is running the 1703 update of Windows 10, this issue does not appear, and it seems that the same fonts are installed on both machines.
This is what the form looks like the the design view:
This is what it looks like at run time with a cell selected:
Hello David,
I just tested the UltraGrid on my work PC using Windows 10 build 1803 with Infragistics Windows Forms 2011 V2 build 1000.
The only way the cells' font show changes is if I explicitly set the FontName property on the DisplayLayout override as mentioned above.
Please review my sample below and modify it so it reproduces the behavior and send it back here. Let me know if you have any questions.
UltraGridFontTest.zip
I will try to reproduce this issue using Windows 10 1803 update. Once I create a sample and observe this behavior, we will test it further to investigate what’s causing this. If you already have a sample, please send it to us. It will help us in investigating this issue faster.
I will post an update by end of day Thursday.
Please let me know if you have any questions.
The TextRenderingMode was set to Default, I tried both GDI and GDIPlus, but with the same errant results.
Hm, that is really surprising. I was really expecting the other controls on the form to have the same issue once you were not setting the font on them.
The only other thing I can think of that makes the grid different in any way is the TextRenderingMode. That might be worth a try, just as a matter of curiosity.
When I step over the configuration block, it doesn't affect how other controls are configured. The other controls do not have the same problem as the grid. That is very curious to me because I would have expected them to display the wrong font like the grid did. I even looked at the lower level properties of the Font and saw that the System Font Name was configured in the same way the grid's font was before I overwrote it with the specification properties in the configuration code. So I am baffled by the whole thing.
¯\_(ツ)_/¯
If you have a morbid curiosity about it, I can possibly see about setting up a web meeting to demonstrate it, but I'm sure you are as busy as we are and I am good with just modifying the base class behavior with the workaround to make it all go away.
Thanks again for everything.