Question:
What is the all-round best way to ask users to select from a list
of 449 items?
Currently I'm trying to choose between 3 different styles of UI design
to get the user's choice of one item out of 449.
(The application is for users to state what food they just ate.)
The options seem to me to be:
1. List object
2. Table object
3. 11 text fields
They all seem to be a bit clumsy or unnatural.
1. List object
I've implemented this option in a form, and it is not too far
from what I want.
2. Table object with 11 rows of text
This sounds attractive because I can put some other additional
info on each line apart from the text to be selected.
3. 11 text fields
I'm currently developing this one. But I have difficulties
getting the text items to highlight while the user
enters text somewhere else. There is no highlighting
feature such as comes with the list object to indicate
what the user has chosen. The FldSetSelection makes text
invert, but only when it has the focus.
Could anyone tell me whetehr there is an accepted
"standard" way to get the user to choose from, say, 449 choices,
while simultaneously having other buttons and fields on the form?
I want the user to be able to quickly scroll through the list
(using up/down buttons, slider, etc.)
Regards,
Alan Kennington.
PS. Regarding the recent post about gcc on linux creating
only 32 kByte or 64 kByte binaries, this is shocking news to me.
I want to write really big software. What's the point in
getting a 4 MB computer if I can only write a 32 kByte program?
Do I have to write multiple .prc files to get around this?
This would be like the "overlay" techniques of the 1970s again!
PPS. Regarding the 96 kByte limit on dynamic memory,
I also regard this as shocking. Why is dynamic memory limited
to 2.5% of my RAM? This means I've got to keep large
data structures in storage memory and use handles for writing etc.
Does anyone know of a way to remove the 96 kByte limit?
I have a CE HPC which has a configuration form for
setting the break-up arbitrarily between "disk" and "ram"
memory in the RAM-only machine. This sounds quite desirable.
