Doug,
I had a similar issue when developing Runner's Log; what I did was to
actually make the table a single column, and in the custom draw procedure I
artificially create the apperance of however many columns I want. Then each
row is called only once. I think it greatly improves the speed and (as a
bonus) simplifies the code.
-Marty
----- Original Message -----
From: Gordon, Douglas <[EMAIL PROTECTED]>
To: Palm Developer Forum <[EMAIL PROTECTED]>
Sent: Thursday, February 10, 2000 7:50 AM
Subject: Table drawing technique
> I have a table with four columns that uses custom draw procedures. Each
row
> is associated with a database record, and various fields in a record are
> used to display information in that row. The issue is that my custom draw
> procedure is called for each column in a particular row, so currently it
has
> to query the record, lock it, get the data for the specific column, and
> unlock it. That's four record accesses to display each row. This seems
like
> excessive overhead that could be avoided. What I was thinking was that if
I
> 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.
>
> On the other hand, assumptions like these are what can get you into
trouble.
> It may work like this today, but not be guaranteed to work that way in a
> future O/S release. Any ideas?
>
> Doug Gordon
>
> --
> For information on using the Palm Developer Forums, or to unsubscribe,
please see http://www.palm.com/devzone/mailinglists.html
>
>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
