>I _HATE_ these intermediate menus. They are fine for context stuff, but >they completely put me off for regular use. > I agree.
Putting the Song Info into the context menu, so that touch plays the song completely puts me off using the Touch/Radio interface for navigation/browsing my music library, because it takes longer to get into Song Info (and I have to remember to long-touch and scroll the awkward little context menu so that I can browse to the artist of the currently playing song, for example). An intermediate context menu for single-touch doesn't solve that problem. Although it would stop accidental playback wiping the current playlist, it doesn't suit people that would be okay with the concept of touch=play, and doesn't suite people acustomed to touch track=song info. >What may need improving is the visual feedback telling you what will >play and what will not. > I prefer the suggestion of making the touch action configurable - select whether you want touch=navigate or play (depending on item context), or touch=always navigate. However, there is no Song Info page any more either :-( It's been consumed into a context menu with Song context actions, Mixer actions, song info and a More Info sub-menu. i.e. context menus should contain actions for the item you've selected, not a long list of many things. Or at least a "Song Info" action to navigate to the song info page. Hyperlinking through a music collection is much slower, and you have to think all the time what you are currently looking at to know what to press next. Get it wrong, and you blow away your current playlist :-( _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
