We have an application that uses Infragistics controls throughout the UI. We use the UltraFormManager for all forms. We used AppStylist to create an isl that we always apply when the app starts. We have deployed the application to hundreds of issues without serious display issues. Recently we deployed to a user and are seeing something very strange. On this particular user's machine the application installed properly but displays no text in any Infragistics control. The only exception appears to be the UltraTextEditor. We see text when entering the username and password on our login screen. When a generic Windows message box is displayed we see text on that. But nowhere else.
This user has 3 monitors at various resolutions and they are using Windows 10 v1809. Their other applications are working fine. We have spent a number of hours logged on to their machine remotely with no success. Of course, I suspect this issue is related to screen resolution and scaling but any changes we have attempted have had no effect.
I know this is a long shot, but is there anything else we might try to fix this issue?
Thank you for posting.In order to understand the issue, I have some follow up questions/recommendations to try:
1) What is the screen resolution and scaling of all three screens? Does the issue occur on all three screens?
2) What version of Infragistics for Windows Forms controls are they using?
3) Try turn off the GUI+ and check if it changes the behavior. (You can change this either for individual controls (via the TextRenderingMode property) or the default for all of our controls (using the static DrawUtility.UseGDIPlusTextRendering property).
4) Try to set the focus of the control and see if something highlighted and can you type?
5) Also, try to exclude the isl, may be isl file is setting the forecolor same as the background color.
Looking forward to hear you back.
Thanks for your response!
Again, keep in mind that we have many users with many different configurations, almost all of them with multiple screens and we have never seen this problem before, so we know it's something different about that machine. Our support staff is working with this user, who is not on site, Our user's machine is provided by the IT department at his company. We are in the process of having that IT department provide an additional machine for testing to see if we also have the problem on that machine,
Is this an isl file that you created or one of ours? The reason I ask is that if you create an isl file with some UI Roles that set the BackColor, but not the ForeFolor, you could end up in a situation like the one you describe. The isl could be setting the BackColor and by coincidence, that color just happens to be the same as the ForeColor on the user's system, and thus the text is not visible. This could also happen if your isl file is not turning off system themes.
This is was the reason behind question #3, because if you have a control that supports selection, such as selecting rows in the WinGrid or WinTree, then the selection is likely to change the default BackColor and ForeColor and so if you select something and the text suddenly becomes visible for the selected items, that could be an indication that the ForeColor is the problem.I suppose another way you could test this without having to recompile your application would be to ask the affected use to change the Windows Theme on their system to something that uses a different foreground color for text and see if that helps.