View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0018210 | MMW 5 | Main Panel | public | 2021-08-19 18:02 | 2024-05-28 08:16 |
Reporter | lowlander | Assigned To | |||
Priority | urgent | Severity | minor | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Product Version | 5.0.1 | ||||
Target Version | 5.1 | Fixed in Version | 5.1 | ||
Summary | 0018210: Allow users to customize which fields are displayed in the Summary column/Simplified List | ||||
Description | In MediaMonkey 4 users could customize which fields were displayed in the Summary column. This is no longer available in MediaMonkey 5. | ||||
Additional Information | Ticket 3517 https://www.mediamonkey.com/forum/viewtopic.php?f=30&t=99826 | ||||
Tags | No tags attached. | ||||
Fixed in build | 2800 | ||||
related to | 0016885 | resolved | michal | Allow users to define fields in Playing |
related to | 0018452 | resolved | petr | Now Playing: Now Playing can't be put on any position except Left or Right in Layout |
related to | 0018019 | new | petr | Allow Playing and Preview elements in locations other than the side Panels |
related to | 0017611 | assigned | rusty | Improved customization of the Playing 'Simplified list' |
related to | 0019416 | assigned | rusty | Views: Ability to 'Group by' x |
related to | 0018314 | closed | michal | Unable to change View / revert to default sorts by clicking on Summary column label |
related to | 0018296 | closed | rusty | Track Browser: Artwork and Summary columns are listed out of order |
related to | 0017972 | closed | lowlander | Sorting in List (by Album) shows hides files in Descending mode |
related to | 0019186 | closed | michal | Track Summary: Ability to customize track Summary per Collection |
related to | 0020945 | closed | petr | Album tracklist changes when it is being played (regression?) |
|
It's both a missing feature after upgrade from MediaMonkey 4 as well as expected behavior based on user feedback. 1) In Playing: A) Simplified List should be user customizable in what it shows. This should be implemented per Type. B) Artwork should be available as an option for Simplified List Tools > Options > Playing list provides enough real estate for this 2) In Filelisting: A) Summary should be user customizable in what it shows. This should be implemented per Type and independent of what's shown in the Player. B) Track Summary (should be File Summary) should be implemented independent of what's shown in the Player. Tools > Options > Playback rules provides enough real estate for this 3) In Player: A) Track summary (should be Player (or Playing) Summary) should allow to accommodate 2 lines of user defined fields B) Skin developer should have option to display those 2 lines or merge them into single line C) Behavior when text is too large should be user definable (and/or Skin developer choice): - Bounce - Horizontal scroll - Vertical scroll - Cutoff (no movement) Tools > Options > Playback rules provides enough real estate for this |
|
I would like to add the following item: 2) . C) ... ie. additional point into "In Filelisting" Re-introduce the column sort action that was lost in the MM4->MM5 migration ... ie. a sort on the (Album) Summary column would re-sequence the display accounting to the tag hierarchy configured for display in the Summary column On other comment ire section 3, is that the Track Summary format is used in the Status Bar and hover tooltip during sync operations ... a multi-line display is suitable in those places? |
|
1) Customization of the Playing list's Simplified list is tracked at 0017611 2) This bug is primarily about configuration of what appears in the 'Summary' column (as opposed to the 'Track Summary/Player' which is already configurable), as was possible in MM4 and no longer is in MM5. This should be relatively simple to implement once we decide: a) Where to configure this. It's similar to other 'Playback rules', but it really has nothing to do with Playback. A possible approach is to have it configured separately just like per-Type settings in the Preview window are. This could be done via a [gear] icon next to the 'Summary' and 'Track summary' entries in the 'Choose columns' dialog. b) As to how to configure it. It could be using a freeform mask-based approach (less friendly) OR by allowing the user to add masks in a manner similar to the criteria chooser OR as shown below e.g. Configure: Summary -------------------------------- Type: _Music__v _Album_v _Album Artist_v _Year_v _Album rating_v --------------------------------- With this field configurable, users could again sort by this attribute. NOTE: this would not really solve the issues described at 2C (described in more detail at 0018314 ), but users probably do expect that sorting by this field should work. 3) TBD (much lower priority) |
|
2) I analyzed this a lot and keeping summary configuration per track type would cause significant problems - impossible to sort (you cannot sort items by different displayed data, e.g. one track type would show rating, other type year, what is greater, 4 stars or year 1975? :) ) and it would significantly complicate binding and displaying, it would be too slow, as we could not use optimizations, if every summary line could contains different fields. I will use similar approach as we use for column configuration (displayed columns and their order and size), it will be most consistent I think and is doable. I.e. Summary configuration will be saved for collection+node, this way one summary could be in Music - All Tracks, other in Video - All Tracks, etc. Configuration of the Summary column then will be accessible just like other column settings, in column header context menu as you wrote (e.g. gear icon next to Summary column, or separate line after Choose columns on Summary column), and user could choose up to 5 fields (we could use another number, but I think 5 should be enough and still mostly displayable next to artwork) and their order. This way it should be sortable, variable enough, more clear and faster. |
|
The approach of having the settings associated with the View for a given Node/Collection seems to make sense (but at the same time, let's keep in mind that we also want to make it easier for users to configure Views to apply across multiple Nodes/Collections). As far as where this could fit, would it make sense in the Configure View dialog? That way it would only appear for grouped views (it's only relevant to grouped views). If we do that, then when the user clicks Choose Columns/Sort, MM could open the configure View dialog (i.e. get rid of the Columns/Sort dialog since it's just a subset of the configure View dialog. This is related to 0019416: the ability to configure 'Group by' functionality, since these summaries only appear in views that are Grouped by x, and are based on what grouping is chosen. Even if we don't add the ability to configure custom groupings, any view that is preconfigured to Group by something can have a section within to configure the 'Group Summary'. |
|
Fixed in build 2800. Columns of summary column can be set in Choose columns dialog and in Configure view of List (by Album), similar way as sorting columns. Sorting by Summary columns does sorting by all columns contained in the summary in given order. |
|
Verified 2805 |