What is desired for an autoscroll preferences UI (so it isn't made twice)?
Simple would be a sentence with 2 dropdowns underneath 'Font' in preferences
form:
Autoscroll: [\/ 1 line] every [\/ 15] ticks.
3 drop downs would allow more flexibility with less listings:
Autoscroll [\/ 1/2] [\/ page] every [\/ 15] ticks.
What choices are most desired for a drop down?
1 pixel,
2 pixels, [to make pixel scroll faster on slow PDAs].
1 line, [most useful but not implemented yet, very non-trivial].
1 page,
...others?
Other interface?
If taking 3 dropdowns, 2 pages wouldn't be that useful, neither would 1/2 of
a pixel (just do a pixel if they have this).
Also a box for:
[x] Stay on while autoscrolling
Also, one feature discussed awhile back was to allow user setting of what
happens on clicking on the scrollbar arrows since a single pixel scroll was
a bit slow for some users' applications. Roll the two into one to conserve
space in the program (and in preferences form) or allow separate options for
each like:
Autoscroll [\/ 3] [\/ pixels] every [\/ 4] ticks.
Scrollbar moves: [\/ 1] [\/ page].
Can probably fit 3 more lines in preferences form right now. If more options
come in, it is going to be more crowded though. For long term, might be best
to divide up somehow into logical bits.
-Separate forms, as is done for Button Action/Gesture Action/Tap Action
(bring out Scroll/Autoscroll/Scrollbar preferences into a separate form?)
but bit of extra code for the form resource and handlers.
-A corner dropdown is the most logical in PalmOS world and lowest overhead,
similar to the PalmOS built-in PalmOS app. Drawback is that is sometimes
easy to miss up in the corner.
-Tabs (like HandyShopper 2.0) look good and are harder to miss than the
PalmOS corner dropdown, but significantly more code size required, may have
to add some extra bits to specifify the tab widths for localizations.
Best wishes, Robert
