I have come across a very weird drawing problem with the Grid control, version 1.6.1.8
I''ve enclosed a simple app to demonstrate the problem.
Quick summary:
Virtual grid on a MDI child window that starts out maximized. First child window and grid show up fine. 2nd through N child windows cause the grid to paint slow and re-render a few times with different column widths, etc. Ends up destroying the MDI parent container and min/restore/max buttons.
Run the app, choose File / New Virtual. Everything is fine.
Again, choose File / New Virtual. This time, the grid is painted slowly, and you can see refreshes of the column widths.
Also notice the min/restore/max buttons in the top right. There should only ever be one set of these, but now there are 2.
Again, choose File / New Virtual. Now you''ll see THREE min/restore/max buttons in top right.
Click the restore button to bring the child windows to a "cascaded" state - and you''ll see, the MDI children painting area is ruined.
Note that if the child window property is set to show the window in Normal state (not maximized), I don''t see the problem.
Also - the other menu choice, standard grid, doesn''t show this problem, even with maximized child forms. So it seems to be a problem with the virtual grid.
Some questions:
- Is there a way to turn off the QueryXXX calls during setup of the grid? After I call ResetVolatileData(), it seems that many of the calls to HideRows, AllowSelection, DefaultColWidth, etc. all cause calls to QueryColCount, etc.
I tried Begin/EndUpdate and Suspend/ResumeLayout calls, but doesn''t work.
THANK YOU VERY MUCH for looking into this...
gridtest_6055.zip