You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Menu forward and backward navigation by using right arrow key.
Similar as in Phonebook and View contact, it would be handy to thumb navigate using up/down for item selection, and (left/)right for (leaving/)entering a submenu.
Maybe even in every case except where the left/right keys are in use (textbox navigation and in-app use)
This would at least be very handy in the action=GUI_ACTION_SUBMENU
Maybe left arrow could be used as well to navigate back.
I might circle back to this improvement if I can figure out some details.
The text was updated successfully, but these errors were encountered:
The arrow pad has a center button which can be used to enter menu items.
As long as left/right aren't already in use for something else inside other
menus, using them for forward/back makes sense to me.
Yes, agreed: this feature might be considered "with care": I assume everything that is not a submenu will break if this would be implemented too rigorously (not sure if it is even possible to differentiate).
I just noticed that my habit was to navigate "right" to jump into a submenu (currently, I prefer using the left softkey to make sure I don't accidentally press an arrow key when selecting a menu item (I probably have clumsy fingers; see my quick fix subnote in #28 :)
It might take a week for me to look into this so if anyone wants to look into it: I won't feel caught up.
Menu forward and backward navigation by using right arrow key.
Similar as in Phonebook and View contact, it would be handy to thumb navigate using up/down for item selection, and (left/)right for (leaving/)entering a submenu.
Maybe even in every case except where the left/right keys are in use (textbox navigation and in-app use)
This would at least be very handy in the
action=GUI_ACTION_SUBMENU
Maybe left arrow could be used as well to navigate back.
I might circle back to this improvement if I can figure out some details.
The text was updated successfully, but these errors were encountered: