> no, but remember that all the list-related
> functions uses an Int16 (signed) for the
> index, which is 15 bits + 1 bit for the sign..
I have run into that problem myself recently.
My app's main database can, in theory, have 50,000+
records, and my main form shows the records in a
list.
Of course, the question you might want to ask yourself
is: is the list widget the right UI to show so much
data? Is the user really going to use the list the
way lists are (often/usually/traditionally) used --
scroll down/up to the record they are looking for and
then select it? With 32768+ records, that sounds
quite unusable to me.
If you really want or have to stick with a list,
you could view the list object as a "sliding window"
into your record set, i.e., it only shows a portion
of it (all starting with the same letter, 0-32767,
whatever). You then have to somehow manage to change
the position of that "window". One simple way could
be to make the last entry a "more..." and if the
user chooses that one, "fill" the list with the next
set of records ("fill" can be through appropriate
offset in the draw list item callback, of course).
Like I said, I am facing a similar problem and haven't
actually decided yet which road to go, since it's
ultimately a corner case. Would be interested to hear
how you/others solved this.
Oliver
__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus � Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/support/forums/
