
Originally Posted by
DynamoBen
However in the case of a long press (ENTER) they have no idea, short of adding an led/buzzer/clear screen, that they have held the switch long enough to change menus. Basically they have to count in their head.
Is this just something I need to live with? Do you run into any problems with this type of interface?
What about having the menu change happen automatically after a button HOLD of say 1.5 seconds.
The user sees the menu change, so they know they've held the button long enough.
After the menu changes, your code then waits for the button to be released before continuing - avoiding spurious inputs at the new menu.
If the user is goofy enough to continue holding the button, the program just sits waiting until they release it (or rig up a shocker on the button so they get zapped after 20 seconds :-)
Only quicly looked over Melanies samples - maybe she already suggested something like that?
Arch
"Data sheets? I ain't got no data sheets. I don't need no data sheets. I don't have to read any stinking data sheets!"
Bookmarks