by Barry4679 » Sun Feb 23, 2020 4:30 am
Peke, that report has been closed, marked as Resolved, without any apparent action.
Is this Working As Designed? It seems as if List layout (column sequence, row sorting, etc) is defined at the Collection level ... so all sub-nodes seem to share the same list layout spec ... so changing from AllTracks in List view, to any sub-node (eg. Album) also in List view, results in no visible difference, which is what he is reporting isn't it?
Is this what was intended? ... it would more logical if each sub-node could have their own specification ... ie Album sub-node could have Album in column 1, and the primary sort could be by album ... while AlbumArtist node could be sorted by AlbumArtist tag, which was in column 1.
In the current situation, if the user changes sub-nodes, and if both are in List View, nothing happens ... MM5 appears to be broken.
Tested with 5.0.0.2228
Also the Manage Views facility seems to be broken in a number of ways;
- Changes to the column sequence (using this control) are never persisted, and are ignored ... but changes to row sort seq specification works OK ... tested while I had List view open
- while testing I got these two crashes ... the second one was after the 1st dump had been sent to you, and MM5 was trying to offer me the [Safe}Restart options
- if I am in List view, and make changes to column layout, and|or row sort spec, by column dragging or column clicking or the Choose Columns dbox, those changes are not persisted to the List View specification, as seen in the Manage Views dbox .... they seem to be persisted only when I leave the sub-node, but not until then ... really confusing
[quote=Peke post_id=465499 time=1582257406 user_id=213]
Thanks for reporting added as https://www.ventismedia.com/mantis/view.php?id=16382
[/quote]
Peke, that report has been closed, marked as Resolved, without any apparent action.
Is this Working As Designed? It seems as if List layout (column sequence, row sorting, etc) is defined at the Collection level ... so all sub-nodes seem to share the same list layout spec ... so changing from AllTracks in List view, to any sub-node (eg. Album) also in List view, results in no visible difference, which is what he is reporting isn't it?
Is this what was intended? ... it would more logical if each sub-node could have their own specification ... ie Album sub-node could have Album in column 1, and the primary sort could be by album ... while AlbumArtist node could be sorted by AlbumArtist tag, which was in column 1.
In the current situation, if the user changes sub-nodes, and if both are in List View, nothing happens ... MM5 appears to be broken.
Tested with 5.0.0.2228
Also the Manage Views facility seems to be broken in a number of ways;
[list]Changes to the column sequence ([url=https://www.dropbox.com/s/wym88e0ck19j48a/list%20config%20changes%20ignored.png?dl=0]using this control[/url]) are never persisted, and are ignored ... but changes to row sort seq specification works OK ... tested while I had List view open[/list]
[list]while testing I got [url=https://www.dropbox.com/s/fa28z3wkicjc38h/List%20config%20dumps.png?dl=0]these two crashes[/url] ... the second one was after the 1st dump had been sent to you, and MM5 was trying to offer me the [Safe}Restart options[/list]
[list]if I am in List view, and make changes to column layout, and|or row sort spec, [i]by column dragging or column clicking or the Choose Columns dbox[/i], those changes are not persisted to the List View specification, as seen in the Manage Views dbox .... they seem to be persisted only when I leave the sub-node, but not until then ... really confusing[/list]
[list][url=https://www.dropbox.com/s/ewjht3he8y847g0/selection%20list%20in%20random%20sequence.png?dl=0]this dropdown selection list[/url] is sorted in a random sequence ... it is hard to find things, because the list is very long[/list]