Bugzilla – Bug 3960
Add graphic indicator to denote branches in SB menu
Last modified: 2009-09-08 09:23:59 UTC
The menu tree in the Squeezebox can be confusing to users. Sometimes the correct thing to do is press the right arrow to get the effect you want, while other times you need to press the PLAY button. Can we add some graphic indicators on the right side of the display to denote what choices you have? Here are some situations that could use clarifying: 1. Something to indicate you're at a branch in the menu. 2. Something to indicate that you're at the end of a menu, but there's more to see below. 3. Something to indicate that you're at the end of a menu, but there's nothing to see below. 4. Something to indicate that pressing PLAY here will do something
I talked to Dan about this, and he pointed out that the musical-note indicator that you can hit 'play' is not thoroughly implemented. For example, if you go to Browse -> Albums you can hit play on an album and it will play the album, but that is not indicated with a musical note. I will take the liberty of summarizing his other comments as something like '(4 of 129)' is not really a great indicator that you can go up or down. Dan, you can certainly add additional clarifications as well.
Subject: Re: Add graphic indicator to denote branches in SB menu The note in the UI indicates a song, not a playable thing.
And a right arrow means you can navigate in to see what that item contains, like albums and artists, aka branches. A radio button circle means that you can choose this as a setting. Finally, pressing PLAY should play the current item (a song, an album, etc). If the item is not playable (a settings choice, a top level menu), PLAY should make you go right, like pressing the right arrow button. Much of this is documented in the wiki: http://wiki.slimdevices.com/index.cgi?UserInterfaceGuidelines That said, I'm sure that there are places where we're not consistent in this behavior. Please feel free to file bugs about places in the UI with inconsistent behavior. I'm going close this bug and look forward the new ones...