Something strange started happening in my app after I upgraded from 18.104.22.168 to 22.214.171.124.
My app opens up, it fills its GridControl, and then tells it to CurrentCell.MoveTo the
lower-left corner, which contains a MonthCalendar cell. So far, so good.
Then, when I use the keyboard to move up by one cell (to another MonthCalendar), or to
the right (to a custom drop-down cell), this new cell doesn''t render properly. If I move to
the MonthCalendar, it has no drop-down button, and it doesn''t react to the keyboard properly.
If I instead move to the custom drop-down cell, it doesn''t draw its button nor its text contents.
All this happens only when the cell is the SECOND one being shown - that is, after the first
manual move. After that, everything works properly.
I''ve tried all sorts of things to make it stop doing this. Some workarounds (I''ll spare you
the details) make it misbehave on the first cell, rather than the second. This is no better.
In one of my attempted workarounds, I''ve called CurrentCell.ShowDropDown(), which hasn''t fixed
anything, but perhaps provides a clue. In this "misbehaving" state, I can click all I want on
dates in the calendar, but the control doesn''t accept them, and the calendar doesn''t auto-close
after the click. Hmm.
I''ve settled on an eccentric workaround
(MoveTo a nearby cell, Application.DoEvents, MoveTo the intended cell) that makes it render
properly for the first, second and all subsequent cells. Whew! However, the bad behavior still
leaks through if I Alt+Tab to another
app while the grid loads - in which case both the first and second cells misbehave in the usual way.
At least one customer has noticed this, and I do all the time.
So I''m wondering... Have you heard any reports of behavior like this, and if so, what was the resolution or workaround?
I can live with that workaround if I need to...
ADAdministrator Syncfusion Team March 9, 2005 07:39 PM
When I use 126.96.36.199, adn set up a grid as you described with MonthCalendar cells, on the initial display, I do not see the currentcell frame as I should. But I do not see any of the other problems you describe. I then try the same sample using our soon-to-be-released code base build, the currentcell frame that was missing with 3010 appears as it should. So, maybe the problem you see will be handled in this next release.
TJTJMarch 10, 2005 12:37 PM
That''s good, then. I can wait for the next release.
TJTJJune 6, 2005 03:22 PM
I see you''ve fixed this in 188.8.131.52. Thank you!