This is interesting. When this is done, all files that are not top of stack disappear not showing at all except for the top of stack. MC never always did this. This was changed.
I promise you, nothing has changed in regard to stack behaviour. They have
always behaved this way, since the day they were conceived.
In order to see all files now so that they are not invisible, I have to make the changes you are suggesting? I have no other way to see all files that are stacked?
You can, naturally, keep your stacks expanded, and then you will always see all stack members. If you do that though, what is the point of stacking them in the first place? Besides that, yes, creating a view such as the one I linked to is the only other way.
Something must have changed in your workflow for this to become an issue out of the blue in the way that it has.
I note that you sourced the files that first brought your attention to this, from a smart list. You could, if you liked, keep your stacks expanded, then, add an extra rule to your smart lists that excludes any files that are in a stack, but not the top file... Something like so would do that, but if I'm honest, feels counter intuitive.
([=isequal([stack files],)]=0 or [=isequal([stack top],-1)]=1)
I can't help but wonder what, if anything, changed that brought your attention to this. Maybe, it's possible that you have been playing "not top of stack" files for longer than you think, and it's just now that you have noticed?
Here is how you could check that if you were curious too...
List all of your audio files, select all, right click and expand the stacks.
Next, paste this into the search field in the top right:
-[stack top]=-1 [stack files]=[] ~sort=[last played]-d
Now, the list should only contain files that are stack members, excluding top of stack files and files that are not stacked, sorted with the most recent played at the top. Does that look correct, or does it show that some "not top of stack" files have been played more recently that you expected?
-marko