At 12:52 PM 3/1/99 -0500, you wrote:
>I have an application where I am doing a lot of manipulation of a list
>resource. The items in the list are character strings that are 20
>characters long. Right now I'm storing the strings in an array and using
>the array to populate the list. My test program has about 25 items but I'm
>thinking now it could eventually have up to 500 items. Is using a list the
>wrong approach in this situation? I like the look of a list, but I'll use a
>table if I have to. The list is alphabetized and I have zoom keys to find
>items quickly even though the list might be long.
>
I'd recommend going to a table. The SDK guidelines recommend that you use
lists as a mechanism for users to make a choice, not as a general purpose
browser of n items. Also make sure you have easy to use navigation/search
methods other than scrolling the list. After about 20 or so items, a
listbox, table, grid, tree (regardless of OS/platform) becomes awful to use.
Glenn
Glenn Bachmann
President
Bachmann Software and Services, LLC
http://www.bachmannsoftware.com
Software Development for Handheld & Mobile Computing, Windows and the Internet
Home of Bachmann Print Manager, the only graphical printing solution for
the Palm Computing Platform
