Charles Yeomans wrote: > Not quite. Listboxes cache data for speed. InvalidateCell clears > the internal buffer for the specified cell(s) and prompts a redraw > using fresh data. If you implement CellTextPaint to pull data from > another object, then you use InvalidateCell to get the Listbox to > show updated data. This is, as far as I know, unrelated to graphics > buffering.
I was the person who opened the original feedback report and pushed RS to put the InvalidateCell in the listbox because I was having problems under Win32 with the listbox flickering badly. After many emails back and forth with RS about this I found a workaround by setting the ScrollPosition to itself such as... ScrollPosition = ScrollPosition This caused the listbox to update its contents without causing a refresh (and flicker). I told them the workaround and said there is something in the undelying code that does the trick, thus was was born InvalidateCell. So you don't need this under OS X, but it doesn't hurt. Refresh will do the same thing for you as InvalidateCell under OS X. _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
