> can assume (dangerous word!) that the column draw procedures are always
> called in ascending sequence, then the draw procedure for column 0 could
> save the display information for the other columns in a static structure,
> and I would only have to do a record access once per row instead of once per
> column per row.
This is where the rowID comes in handy. I whould save the row ID of
the last drawn row. If this row ID changes, reload your cache. This
would be independant of the order and not much harder to code.
The only drawback is that you have to set the rowID invalid anlong with
calls to TblMark*Invalid.
HTH,
Holger Klawitter
--
Holger Klawitter +49 (0)251 484 0637
[EMAIL PROTECTED] http://www.klawitter.de/
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
