In case anyone's ever had problems with dynamically allocated lists in tables, here's what happened to me. Pretty simple in hindsight: I had one loop that would call LstNewList and then call TblSetItemPtr with the new list. However, on the handspring, the Form object would get moved at every allocation, so all but the last ListPtr was invalidated.
The solution is obvious: have a second loop at the end call TblSetItemPtr after the first loop has allocated all the necessary lists. Maybe it'll help someone else when searching the listserv :-) On 7/23/02 1:13 AM, "Steve Mann" <[EMAIL PROTECTED]> wrote: > At 12:16 AM -0400 7/23/02, Lally Singh wrote: > >> But, in a cowardly attempt to avoid debugging on actual hardware, does >> anyone know of any differences offhand that would make a palm & handspring >> act differently in code that did the following: > > I don't have any specific information related to this question, but I > can definitely tell you that there can be significant differences > between running on POSE and running on real hardware. Also, different > devices can have radical differences that don't show up on POSE. > > The moral of the story is: always, always test on your target > hardware, the more the better. > > Related to your specific question: I have used LstNewList a fair > amount in the past, and it can be a real pain in the ass. > > Regards, > Steve Mann > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
