Hello Anakin,
I have investigated and I have asked our engineering staff to examine further the issue with the grid cells not being rendered properly. To ensure that it will receive attention, I have logged this behavior in our internal tracking system with a Development ID of #227111. So I’ve created a case for you CAS-178589-Y5B5W1 and will update you for the progress of this issue via the mentioned case. You could reach your case following the link below: https://ko.infragistics.com/my-account/support-activity
Thank you for using Infragistics Components.
I have the same issue. After upgrading to 16.1.20161.2088 the UltraGrid only displays some text within the cells if I scroll down in the UltraGrid. All other cells in view are shown but do NOT have any text. There does not appear to be a pattern of which cells show text and which cells do not.
As soon as I hover the mouse pointer over the cell the text will appear. I can also select a row to show all the text for that row. But if I scroll up and then back down the cells are redrawn with a different random number of cells displaying the text.
Please see attached screen shot. All cells should have text displayed.
Attached is another example where after scrolling down only the top row in view displayed text. I then moved my mouse over the grid in an X pattern. As you can see, the text becomes visible after hovering over the cell with the mouse pointer.
I added the blurring to protect information.
Did some more investigation and it appears that the issue only occurs when e.Layout.Override.CellDisplayStyle is either CellDisplayStyle.FormattedText or CellDisplayStyle.PlainText. CellDisplayStyle.FullEditorDisplay seems to work fine.
If there is not a response to this I will create a new post.
We are developing a Windows Forms application where I have both Release and Test versions. Both are compiled. The Release version is using version 13.2.20132.2098 and I am able to run the application WITHOUT any of these issues. The Test version of the same application using 16.2.20162.1000 DOES have these issues.
So it is something with the newer Infragistics components as both versions of my application are using the exact same code base when it comes to the UltraGrids. Other parts of the Test version has been updated but that should not matter.
We were planning on testing this application for the next couple of weeks but can't now with this bug. We may have to revert back to a previous version.