my most disliked MM5 feature [#17141]

[Barry4679]

There is much about the MM5 that I like, and where I want the release of MM5 to come soon.

There are few other features that I don't like so much ... and then there are a few that I actively dislike.

This is my top hate at the moment. You have changed what happened in MM4, and I think that you have significantly degraded the user experience.

In #1 I doing something with date Added. I am in List view, and I have setup the display so that the Added column is visible and prominent.
#2 I wanted to see the tracks grouped by album more clearly, so I changed the View to List By Albums
===> you switched me to List By Album View, but you threw away my column configuration ... I cannot see the Added column any more.

the same thing would happen with the Column Filter ... you would throw that away too, and my current filter setting. ... ??!!!

To be frank, it sucks.

This does not happen in MM4, when I change from Show Details ==> Show Art with Details.

Maybe a lot of people have asked for this (?) ... and maybe there is a Use Case I can't see (?) ... but I hate it.

Could you consider adding a shift+click view change option where you:

• kept the column settings

• kept the Column Filter, and the active filter setting

• and the sort sequence

ie. just a change of view, and not a disorientation and partial re-navigation

It would good it could also apply to change to another collection ... see #3 in that diagram ... I changed to a different collection ... it would be good if the shift+ navigation could keep the same settings that I am navigating from

[Lowlander]

List (by Albums) has the Added Column, it's part of Properties. MM4 also keeps the sort the View already had, not the sort of the View you came from.

[Barry4679]

List (by Albums) has the Added Column, it's part of Properties.

Look at the diagram I posted. Try it yourself.
You are talking about something different.

MM4 also keeps the sort the View already had, not the sort of the View you came from.

I did not claim that MM4 kept the sort that I came from.

I claimed that when changing View:

• MM4 kept my column selection and layout ... and that MM5 does not

• MM4 kept my Column Filter layout, and my filter position ... and that MM5 does not

I think that these two MM5 changes greatly diminish MM, and I think that I will not be the only customer who hates this change.

I can see that the current MM5 behaviour may have some limited utility when starting a new session, but it is crappy when just changing View during a session, because it toggles column visibility off|on, and resets how the display is filtered. ... MM4 provided a view change ... MM5's view change comes with disorientation if the user has filtered the screen, or has altered normal column layout, to suit what they are trying to achieve at this minute.

Which is why I ask whether they could consider retaining the current behaviour, as an option, via a shift click View change (ie. shift click the tool bar's View icon, or shift click one of the items in the View submenu)

MM4 also keeps the sort the View already had, not the sort of the View you came from.

I did add the Sort sequence into my request for change. But please ignore.
I wasn't thinking clearly, because List By Album has to reset the sort sequence, so that the display groups album tracks.
Sorry confusion.

[Lowlander]

Are you saying that switching from one view to another and then back has changed the columns of the first view?

[Barry4679]

Are you saying that switching from one view to another and then back has changed the columns of the first view?

No.

But say I am changing from list View, to a List By Album View ... and I am doing this so that album tracks are grouped ... or that I can see album art ... or I just want to be able to collapse the album tracks a little.

The new view does not persist my column layout like MM4 did.
The new view does not persist my Column Browser visibility|layout, nor my filter position, like MM4 did.

ie. the change of "view" is destructive in MM5 ... in MM4 it was not destructive.

[Lowlander]

I still don't follow.

I selected a Playlist which was shown in List View. Enabled the Column Browser and switched to List (by Album) and the Column Browser remained.

Like MM4 whatever columns a View has are retained for that View when switching around.

Whatever file was selected remains selected when switching View.

[Barry4679]

I still don't follow.

I selected a Playlist which was shown in List View. Enabled the Column Browser and switched to List (by Album) and the Column Browser remained.
Like MM4 whatever columns a View has are retained for that View when switching around.
Whatever file was selected remains selected when switching View.

I didn't report any problem involving Playlists.

See this tiff video.

• EntireLibary collection, Alltracks sub-node

• In List view

• the Added column is in column position #2

• Column Filter set to a single AlbumArtist ==> 2 albums, 20 tracks

• Change View to List By Album

• ==> Added column removed from display ... no longer filtered to 20 tracks ... now see all 47,000 tracks ... Column Filter and it's current hierarchical layout has been removed from display

I am encouraged that you seem to indicating that this is a bug\, rather than working as designed. Thanks.

[Barry4679]

I selected a Playlist which was ...

A thought. Maybe the difference we are seeing could because of the Manage Views facilities, where default overrides can be configured for List, List By Album, and Grid Views ... but not Playlists AFAIK.

Where are the overrides stored? ... If they are in the json file, my overrides should be blank because I was forced to delete my json file, a day ago, due to problem discussed in another thread. ,,, But if they are stored in the db, there is the possibility that I have configured overrides when beta testing that feature, many months ago.

If this Manage View facility is causing what I see, I think that would increase the case for a shift + ViewChange facility as suggested earlier.

[Lowlander]

Change View to List By Album

==> Added column removed from display ... no longer filtered to 20 tracks ... now see all 47,000 tracks ... Column Filter and it's current hierarchical layout has been removed from display

Yes, Views have independent column settings, so if you didn't have Added in the List (by Albums) it won't be there when switching from a View that had this column. Each View uses it's own column settings.

As for using All Tracks, I can't reproduce as this always crashes MM. I do see no Column Filter on load, but as it never loads fully I can't confirm. It did work fine in an AutoPlaylist. Column Filter and selection remained. However doing this for a specific Genre in a Collection showed the same: https://www.ventismedia.com/mantis/view.php?id=17141

[Barry4679]

Yes, Views have independent column settings, so if you didn't have Added in the List (by Albums) it won't be there when switching from a View that had this column. Each View uses it's own column settings.

And for any MM person where this is TLDR; it is this new MM5 feature change, from MM4, that I am asking be made optional by a shift+click override when changing View.

Maybe that there is a Use Case for this alteration to MM4 behaviour, but I don't understand how or where I would want it.

What I lose with this change however, was useful in my regular use of MM4. Now with MM5 when I have setup display columns for whatever task I am working on at the moment, the setup is lost when I change View ... and I have repeat the config change after changing View. ... not happy.

As for using All Tracks, I can't reproduce as this always crashes MM. I

I am not experiencing this crash. You didn't mention it in your Mantis report.
I am experiencing a crash in 2275. There is a workaround to that crash by deleting the json file.

[Lowlander]

I now see what you mean as I was able to reproduce that adding a column it also added the column to another View in MM4. I prefer the MM5 method where Column settings can be configured per View.

[Barry4679]

I now see what you mean as I was able to reproduce that adding a column

Good, thanks.

I prefer the MM5 method where Column settings can be configured per View.

That's fine. I am not asking for the new behaviour to removed ... just for he MM4 behaviour to be retained, as an option.

Even you may find it useful, when you are working on ion some tasks.