View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000538 | MMW v4 | Playlist / Search | public | 2003-07-02 14:18 | 2004-11-14 04:01 |
| Reporter | rusty | Assigned To | |||
| Priority | immediate | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Fixed in Version | 2.3 | ||||
| Summary | 0000538: Improved sorting in 'Playlist' nodes -- Add 'Update Play Order' to context menu | ||||
| Description | 2 friends have indicated a major annoyance with Songs-DB that probably wouldn't be too difficult to rectify: When building a list of 'now playing' tracks (which is often the case--users often decide to save the list as a playlist _afterwards_), it's almost impossible to re-order the playlist: -in the 'Now Playing' dialog, the user can 'Randomize' or 'Reverse' but that's it -in the 'Now Playing' node, the user can't do anything Some of the things that users _would_ like to do are: -Sort by Artist -Sort by track length -Sort by BPM -etc. Two approaches to the usecase can be taken: 1) Always dynamically modify the now playing order in response to any sort (for both the dialog and the node). This is probably the simplest solution from an end-user perspective. In addition, other custom sorts such as 'randomize' or 'reverse' would be available via other dialogs (as described in bug 0000356). 2) A second possibility is to allow the user to maintain play order independent of display order. e.g. if bug 0000132 is fixed, then each track has a playlist order number, which wouldn't have to change even if the user sorted by any set of columns. The user could then click 'Edit : Updated Playlist order' and the tracks would then renumbered to match the display order. This gives the user a bit more flexibility, at the cost of (I think) too much complexity. Recommendation: approach 1) is the better approach. The only downside is that for 'Playlists' subnodes, approach 1) has a negative downside: because playlists are edited in-place (i.e. no save button is needed), if the user changes the sort order by clicking a column, it would change the playlist order, and the user would have no means of reverting to the earlier playlist order. Thus, approach 2) would have to be used for playlist nodes. What do you think? | ||||
| Additional Information | Note: sort behaviour was originally modified in bug #48. The proposed behaviour may require that bug 0000132 be resolved first (depending on the approach taken). Also raised in: http://www.songs-db.com/forum/viewtopic.php?t=328 http://www.songs-db.com/forum/viewtopic.php?t=1203 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
I agree with the proposed solution - I will probably think a bit more about it, but it seems to be good this way. Also priority 'high' seems to be ok. |
|
|
I've thought about this further, and assuming that we want a consistent implementation for 'Now Playing' and 'Playlist' nodes, I now believe that solution 2) is a better approach---unless there's an 'undo' function. Otherwise, it's far too easy to lose hours of work by simply clicking a column header to view tracks in a different order. A very simple implementation of 2) would be to add the following command to the context sensitive menus for the tracklists in Now Playlist and Playlists: 'Change Play Order to Sort Order'. Something along these lines was suggested at: http://www.songs-db.com/forum/viewtopic.php?t=1690 A second issue that also needs to be addressed is what should occur if the user adjusts the Sort Order and then d&d track(s) to a specific location in the list, between Track A and B. For this case, users expectations would be that the track(s) are moved to a play order immediately following track A or preceding track B. The specific order should be determined based on how the d&d arrow is aligned (i.e. when dragging to between A&B, if the arrow is pointing up to A, then the Play order should be A's play order +1; if the arrow is pointing down to B, then the Play order should be B's play order -1). Note also: I've adjusted the bug slightly so that it applies to both Now Playing and Playlist nodes. |
|
|
This bug has mostly been fixed in #1266 (alt-f5 in playlist nodes) and the rest will be fixed in another bug covering Now Playing. The only issue that remains is to add a context menu entry to the tracklist for Playlist nodes: 'Update Play Order'. This entry should appear as follows: playnow,playnext,playlast | Update Play Order | Copy,Cut,Paste.... |
|
|
Please also add tooltip text for 'Update Play Order' that should be shown in order to explain the functionality to the user. |
|
|
Tooltip: Change play order to match sequence in tracklist |
|
|
Fixed in build 804. - I just moved it to the top of menu because it's visible only when it can be applied, i.e. if user sorts playlist items by clicking a column header. |
|
|
This works well, however, it's been implemented in a manner that will result in most users not finding the functionality. i.e. Users adjust the order of tracks clicking the column headers. They would then expect to re-order the tracks by clicking the context menu in that panel. Granted, a context menu normally applies only to the track that is highlighted, however, I think that an exception is warrented in this case. note: the entry should appear above the Play x entries, separated with a divider. |
|
|
Fixed in build 806. |
|
|
Verified in 808. |
