Rockbox Development > Feature Ideas

User Experience and Rockbox- A rethink required?

<< < (8/13) > >>

psycho_maniac:

--- Quote from: Llorean on December 26, 2009, 01:11:07 PM ---The idea of showing the setting value in the list has actually been discussed before. I don't know what the results were
--- End quote ---

this what your talking about?
http://forums.rockbox.org/index.php?topic=5881.0
also i like the Rockbox UI_Feedback.pdf link. looks nice, but i want the back button to act as it does now currently when at the main menu.
edit: i think that if we go hit the back button when we are in a context menu we should be taken back to where we were. the only one i know of is when your in the wps and you hold select and when you hit back you are taken back to where you were, which is the wps.

edit: wow i have been a member here for 5 years and i just busted the 800 post mark YAY me!

Llorean:
I think you misunderstood what he's saying - he's not proposing changing the back button (as far as I can tell) but rather fixing a bug where pressing "back" doesn't take you to the previous level of the menu, but rather kicks you out of the menu and back to the WPS.

JdGordon:
the thing with the context menu is not a bug.. its actually by design (and by that I mean thats the way its worked for the last 4 years and wont likly be changed any time soon... in fact, there is actually bandaid code in there to make it work :/ )

My preferred method for showing the setting value in the list is to make the current item 2 lines high with the name of the setting on the top line and the value right aligned on the second line. This is actually fairly fiddly and might not really be doable. There are also problems with showing setting values in the lists, some settings look like settings to the user, but are actually handled differently so either special handling needs to be added for them (not good), or they are displayed differently (also not great).

help text of any type is not really ideal because it wastes alot of space, or it involves alot of disk access (or is done in a plugin which only allows english).

from the pdf...
1) displaying "nothing to resume" in the main menu is possible, just needs someone to do it
2) There was already a discussion about remembering the current theme, I am hugely against this because there is no way to enforce it (unlike remembering the font or wps), search the forums and irc if you want more explanation
3) there is no rule three!

Llorean:
It's by design that you can tap "right" to go into Sound Settings, then "Left" to leave it back to the context menu but tapping "Right" to go into Playlist followed by "Left" doesn't take you back to the context menu, but rather to the WPS?


I do agree with JdGordon that the two-line proposal for the settings looked best if it can ever be achieved (and is probably most compatible with larger fonts, etc, and almost certainly would work better on charcell displays than the shared-line version).

BdN3504:
One thing I found a bit irritating when switching to rockbox was that after you changed the "view file type" setting, you sometimes ended up with an empty filebrowser. For people who don't RTFM this causes panic, because they think all their files have automagically gone and rockbox is an evil disk formatting virus infected OS some jerk put on their beloved DAP. This of course is the consequence of entering the quickscreen and changing that setting without knowing what it does.
These useres couldn't undo this change because they didn't know what they had done. This was mainly because the "display file type" setting wasn't displayed anywhere but in that setting. Now that there is the wonderful feature of customisable satusbars, this is a problem of the past.
On any account, I suggest we include the view file type setting in the default sbs (e.g. with the letter A, P, M, S) and create a manual entry for that.

As for popups, this could easily be done using conditional viewports in combination with the %mv tag. of course the %mv tag would have to adapt to the current screen and represent changes taking place respectively. Am I right in assuming that every screen in rockbox is currently shown in a viewport? If that's really the case and we are in favor of popups (which i understand we're not), I'd suggest we work on an XML interpreter. People could provide XML files in which every menu item is listed including a description which serves as the pop up text. i don't know about the difficulty of implementing a XML reader, so this suggestion might also very well be complete nonsense.

Navigation

[0] Message Index

[#] Next page

[*] Previous page