|
|
To answer your questions: 1) Lets try the FAB for the beta and collect feedback (I would prefer to not add a config entry) 3) I was using the terminology from MMA (which is Play now), but I agree that it's not needed as an explicit command for most views when no tracks are selected. The only question is whether it should be included in Album > AlbumName views as the FAB instead of 'Play shuffled' (i.e. *Play now, Play shuffled, Queue next, Queue last) 4) 'Select all'/'None' should continue to be shown. I also reviewed most cases to make sure the suggestions make sense across different views (see https://docs.google.com/spreadsheets/d/1bDJBkwp-bpYJBpPiUkeVT9vDRSFU4YgKyBLQfb-fo1Y/edit?usp=sharing ), and believe that it does. Based on that exercise, I've clarified the recommendations slightly: - FABs are indicated with an '*' and overflow menu items in brackets. - It's written with the Queue terminology from 0020043 - Elaborated on the cases when no items are selected (entire 'collection' vs subset) - Removed the redundant 'Play all' command when nothing is selected - Clarified that multiple selection also refers to single selection of an attribute So here's the updated summary: When no items are selected - For views representing all tracks (e.g. Music > Tracks, Music > Albums, Music > Genres, etc.) in a root node: *Play shuffled - For most views representing a subset of tracks: *Play Shuffled, Queue next, Queue last For single track selection (as opposed to single attribute selection) in most views: Play now, Queue next, Queue last, Add to playlist, (FMFS, Properties, Delete, Share, Set as...) For multiple track selection OR single/Multiple attribute selection in most views: *Play Shuffled, Play now, Play next, Play last, Add to playlist, (Properties, Delete, Share) For single track selection in Playing view: Queue next, Queue last, Add to playlist, (FMFS, Properties, Remove, Share, Set as..., Move to start, Move to end) For multiple track selection in Playing view: Queue next, Queue last, Add to playlist, (Properties, Remove, Share, Move to start, Move to end) |
|
|
Fixed in build 2.0.0.1088 I can see that Composers are not in list https://docs.google.com/spreadsheets/d/1bDJBkwp-bpYJBpPiUkeVT9vDRSFU4YgKyBLQfb-fo1Y/edit?usp=sharing Is it on purpose? |
|
|
As discussed, composers can be treated like Artists. Tested 1088 and there are a couple of issues. 1) When no items are selected, and the user navigates to views representing a subset of tracks, only *Play shuffled displays, instead of *Play shuffled, Queue next, Queue last e.g. Music > Albums > AlbumName1 Music > Genres > GenresName1 Music > Artist > ArtistName1 etc... 2) For Single/Multiple track/attribute selection (in all views including Playing queue): - 'Add to Playlist' icon is missing (i.e. even when there's plenty of space it appears in the overflow menu instead). 3) For attribute selection: - Share is missing completely 4) Single/Multiple Attribute selection only displays a small subset of icons i.e. *Play Shuffled, Play now (Play next, Play last, Add to playlist, Properties, Delete, Share) instead of *Play Shuffled, Play now, Play next, Play last, Add to playlist, (Properties, Delete, Share) e.g. for Music > Albums > AlbumName1 Music > Genres > GenresName1 Music > Artist > ArtistName1 |
|
|
So the number of visible actions in action mode depends on screen size and orientation. When the width is: <400dp -> 3 items >400dp -> 4 items >460dp -> 5 items >580dp -> 6 items >640dp -> 8 items Fixed in build 2.0.0.1089 |
|
|
Tested 1088 1) Not yet fixed (tbd since the AttributeName that displays when nothing is selected takes up space) 2)/4) Verified 2) that 'Add to playlist' now appears as an icon, but is it possible for both 2/4) to be more aggressive in terms of the number of items that can be displayed by: - moving the number representing the selected items to the left - fitting a bit more in the space to the right (see attached) 3) Verified Space-for-more-action-icons.jpg (112,971 bytes) |
- Anonymous
