I guess you are linking at least to databases, and that should be why it takes so long. Try not to cross-reference databases in a draw procedure... maybe you could provide repeated data in the first database...
If it is not that, then there is some lengthy calculation that should not be made by the handheld but by the computer generating the data... If none of this helps, we would need the source code of the custom draw procedure to be able to see what's taking so long, and how to optimize it. Juan de Dios Santander Vela, Electronics Engineer Palm OS Solutions Development Manager http://www.trevenque.es/ http://www.control-insitu.es/ ----- Original Message ----- From: "Edward P. Ross" <[EMAIL PROTECTED]> To: "Palm Developer Forum" <[EMAIL PROTECTED]> Sent: Wednesday, June 12, 2002 8:27 PM Subject: TblSetCustomDrawProcedure Optimization > I have a table with 4 columns, 9 rows. > > I am using a custom callback routine to draw the items using TblSetCustomDrawProcedure like this: > > for (i = 0; i < 4; i++){ > TblSetColumnSpacing (tableP, i, 0); > TblSetCustomDrawProcedure(tableP, i, ListTableDrawItem); > TblSetColumnUsable (tableP, i, true); > } > > My callback function, ListTableDrawItem takes a while - meaning that it is noticeable as a flicker effect as the rows and > columns are updated. I am looking for the best way or a couple of things that I could do to optimize the display so that the > flicker wouldn't happen. > > Is there something that I could read about or something I should look at specifically? > > Thanks, > Ed. > > > -- > For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/ -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
