- Status Closed
- Percent Complete
- Task Type Bugs
- Category User Interface
-
Assigned To
jdgordon - Operating System All players
- Severity Low
- Priority Very Low
- Reported Version Daily build (which?)
- Due in Version Undecided
-
Due Date
Undecided
- Votes
- Private
FS#8105 - Hitting "back" in context menu to go to previous category
The interface would be a lot more symmetrical if hitting back (on the iPod, hitting the rewind key) would go to the previous sub-menu of the context menu interface instead of the original screen in which the context menu was activated. Of course, if there is no previous sub-menu, then it can return to the original menu.
Hitting forwards goes to the next sub-menu, so I don’t see why hitting back shouldn’t go to the previous sub-menu!
example:
WPS
“long hold” → context menu
highlight “Bookmarks” Hit “forward” → “Bookmarks sub-menu” (oops! unintended)
Hit “back” → “context menu” (ah, better! now I can select what I really wanted)
instead of
Hit “back” → “WPS” (on the sub-menu)
once again, hitting back in the context menu to return to the WPS feels natural, but hitting back within a context menu sub-menu would feel more natural if it returned back to the context menu.
Loading...
Available keyboard shortcuts
- Alt + ⇧ Shift + l Login Dialog / Logout
- Alt + ⇧ Shift + a Add new task
- Alt + ⇧ Shift + m My searches
- Alt + ⇧ Shift + t focus taskid search
Tasklist
- o open selected task
- j move cursor down
- k move cursor up
Task Details
- n Next task
- p Previous task
- Alt + ⇧ Shift + e ↵ Enter Edit this task
- Alt + ⇧ Shift + w watch task
- Alt + ⇧ Shift + y Close Task
Task Editing
- Alt + ⇧ Shift + s save task
I agree.
Of course. The menu hierarchy should be respected. It should not return to the WPS until you quit the top level, *or* select an item from one of the submenus (which is what separates the context menus from the main menu, that you leave the menu by selecting an item).
“The menu hierarchy should be respected. It should not return to the WPS until you quit the top level” Already mentioned:
“Of course, if there is no previous sub-menu, then it can return to the original menu.”
The behavior I propose is the same behavior in the database and in other sections of rockbox such as the settings, so we should unify the behavior throughout rockbox for flow purposes anyways. It’s very confusing to have a different interface for one menu, especially if it looks and should behave exactly like the other menus
Remember that there is a context menu in the file browser, so that needs to be changed too if it is a separate function