The wxGrid demos that use a custom table exhibit weird behavior on my W95
and WNT4.0 systems. If I just grab the scroll bars and drag them around for
a while (20-40 large scrolls seems to do it) the grid will start leaving the
grid lines on the screen instead of erasing them, or not painting the grid
cell contents, or not show the shading in the colName area, or all of the
above. If I continue to force repaints the behavior gets worse until the
grid is all black or has vestigal data on it that will never be painted
over. Once this starts to happen, the two systems show different behavior
when I stop and restart the app. I can restart the app on WNT and it
restarts behaving correctly but will exhibit the same behavior if I do the
same tests. On W95, once the above behavior starts, the damage is permanent
and even a restarted app shows the same behavior until I reboot the machine.
The first two wxGrid demos (the ones not using custom tables) do not show
this behavior.
I have not tried this yet on other systems than W95 and NT4, because
those are the systems my client is using and so that is how I am currently
set up.
At first I thought this was short-on-storage behavior but WNT memory
diagnostic does not seem to show problems there. Lots of memory and lots of
handles free.
Has anyone else seen this? I looked in wxWindows bug list and did not see
anything that looked like this. Could be a known problem (I hope)? Perhaps I
need a patch to my OS's? Anyone who has seen this or can direct me to a
solution will have my undying gratitude.
-- Rob Dickinson --