|
|
Also the ability to reverse sort in grids isn't possible: https://www.mediamonkey.com/forum/viewtopic.php?p=482617#p482617 |
|
|
Sorting has been implemented in Grid views via the Views configurator. However, this is kind of hidden and doesn't address the need for multiple sorts or changing the sort order. So the simplest approach to dealing with this would be to: a) Display sort headers at the top of Grid (by album) views for each of the visible album attributes. afaik, this isn't required for any other Grid view. b) We should probably also display the Album date in this view (if sort by Year feature is added) Note: users have asked to sort by other attributes. We could theoretically allow the user to configure sort headers, but I don't think it makes sense since other attributes aren't _album_ attributes. e.g. Sort by 'Date added' or 'Artist' wouldn't make sense since tracks from a given album may not have been added all at once, and tracks from an album may have different artists, so in both cases the Album would have to be represented twice (and without the Sort attribute shown since it isn't album specific). Thoughts? |
|
|
Sorting moved to grid view header, enabled both directions, build 2800. Possible sorting by rating not added yet, it would be very time-consuming now, to be done later with some temporary saving of precomputed album ratings (we currently compute it only for displayed albums, to save CPU load). |
|
|
There was also a request for "Original date" : https://www.mediamonkey.com/forum/viewtopic.php?t=103052 (marked as fixed in 2800 so that the sorting in header implementation gets tested). |
|
|
Sort on Added has also been requested: https://www.mediamonkey.com/forum/viewtopic.php?t=103163 Sort on Composer has also been requested: https://www.mediamonkey.com/forum/viewtopic.php?t=101996 |
|
|
Sort by rating added to build 2800. |
|
|
Resolving, as the other attributes are track attributes, not album, as Rusty wrote. |
|
|
It seems inconsistent that you can sorting in List but not in Grid when you Configure View. Rating sort confirmed on 3523. image.png (34,841 bytes) image-2.png (21,774 bytes) |
|
|
We added sorting configurability to view configuration, however, the original intent was to be able to be able to choose which fields are sortable in Grid (by Album). But we seem to have extended this into an implementation that actually changes Sorting settings (e.g. Ascending vs Descending) across nodes. But this doesn't make sense since Sorts are always a per node setting! To explain this more clearly, assuming column settings are per Collection: In MM 2024: - Music > Genre [List] can be sorted by Genre - Music > Ratings [List] can be sorted by Ratings i.e. each node has different sort settings But in MM 2027: - Music > Genre [List] can be sorted by Genre --> Music > Ratings [List] is now sorted by Genre! i.e. sort settings are no longer saved per node! In other words, in View configuration, it only makes sense to configure which fields are sortable for views that don't have Columns (i.e. Grid views), and it never makes sense to define sort order. Unless we intended to make this change, but I'm not sure whether we'd made such a decision?? Note: The tie between sort order and Node (and sort order's de-coupling from Views) is also why MM 2024 didn't have 'Configure View' as a contextual entry directly in the column heading---because it didn't (doesn't?) make sense for 'Configure view' to configure sort order if it's not tied to the View. --- Assuming that there was never an intent to create common sorting across all nodes in a Collection, we can fix this relatively easily by only configuring Sort order for the current node and by moving it to the bottom: Configure View: Music Name: List (by Album) Columns: Available . . . . Displayed . . . . Actor . . . . . . Artwork . . . . . . . . . Summary: . . . . Album . . . . . [-] . . . . . . . .Album Artist . .[-] . . . . . . . .Rating . . . . .[-] [+] Elements: ... ... ... Sorting (<NodeName>): _Summary_ _A..Z_ Note: this would also help solve the various issues described in item 2. Related to: 0017594 |
- Anonymous
