tbessie wrote: ↑Fri Jun 04, 2021 2:01 am
So changing a parent node doesn't bubble down to its children.
Are you saying that this doesn't happen for you when you do the above?- Tim
Yes, and then No, in that order. That is the way that MM5 works (atm).
I think that you may have confused LowLander when you said that someone may have to do this "thousands of times" ... so he probably thought that you were staying in a sub-node, and were saying that you had to do it for every album that you opened in that sub-node.
It is not such a big deal for me to do as you describe, because I working mostly with 4 custom collections, and I only use a couple of the sub-nodes. ... As I said before the impact would be reduced if you could toggle to a specific view via hotkey, as you could in MM4.
Since you are only using a single view, you are not really the person that MM5 has been designed for.
It is designed for some who does something like:
- uses Browser view at the top of the collection
- uses Grid By Album in the Albums sub-node
- and uses List By Album in the AlbumArtist sub-node
That kind of person is going to be happy that each sub-node has it own view memory
Since you are always in List view, you could just use the All Tracks sub-node the whole time ... but you probably have your lists setup with different sort sequences and different columns displayed for each sub-node?
I agree with the general point that the MM5 is new, and is lacking in some customisation options that would make it better. They have a lot of options, but I think that they are missing key ones. ... For my Use Case MM5 is better than MM4, but is not (yet) optimal.
It is difficult for them, eg. the customisation that you are asking for would not be anywhere near the top of my list.
