by Barry4679 » Sun Sep 12, 2021 1:48 am
benzo8 wrote: ↑Sat Sep 11, 2021 9:04 pm
And in playing with this, I think I've found a bug:
If I select the Album Artists node, displaying in Grid Mode and type Genesis, it finds Genesis the band. If I click on that I get their albums, but if I then want to change to List mode or List (by Album) Mode, the Genesis search has become a "Any text" search - this is confirmed by then changing to Advanced Mode.
Similarly, if I'm already in List mode or List (by Album) mode, the text I type, despite being show as part of the breadcrumbs as past of the Album Artists node, is a free text search. This is counter-intuitive at best, particularly given how MM4 worked in this regard (it would jump down to the expanded sub-node, which, by definition, would be the Artist your were looking for).
I call that a bug too, but it is working as designed (apparently).
The documentation does not cover this, but search|filter criteria work differently in different contexts.
Your first query was in Grid view, where any supplied criteria looks only at album level criteria, i.e. the albumartist and album title attributes.
When you switched across to one of the list views, you were displaying tracks, so any supplied criteria looks at both track and album level attributes ... ie "Any Text"
If you wanted the same targeted result in a List view the criteria should be albumartist:genesis
But where it becomes entirely indefensible (IMO), is when you go in the reverse direction. ie:
- be in a list mode, and type albumartist:genesis ... all good so far
- then switch to Grid mode ===> and the result is empty !!!
- that is because despite what is inferred in the documentation, or is explicitly stated in the hover tool tip, a fieldname:xxx query is silently ignored in Grid mode,
- and it is also despite what I obviously intended via the supplied citeria
IMO MM5 suffers from thinking that it is an AI in some situations ... and can get it wrong
benzo8 wrote: ↑Sat Sep 11, 2021 9:04 pm
Similarly, if I'm already in List mode or List (by Album) mode, the text I type, despite being show as part of the breadcrumbs as past of the Album Artists node, is a free text search. This is counter-intuitive at best, particularly given how MM4 worked in this regard (it would jump down to the expanded sub-node, which, by definition, would be the Artist your were looking for).
The new MM5 behaviour does have upsides ...
- it is easier to find Peter Gabriel if you have forgotten his first name
- you can regain more space for the centre panel, by leaving the left panel permanently closed
- All Text criteria is a powerful tool, and MM5 elevates it front and centre
it is not real easy to see what a "sub-node" is in MM5:
- every now and then I find out, but then I forget because it doesn't completely make sense (to me)
- each sub-node has its own state ... eg the last view that was in use, and any tailoring of the view (columns displayed, column display order, row sort sequence, etc)
- some sub-nodes have extra views (eg Years)
- some sub-nodes have extra options, eg. Albums view has Sort By options
- but, as you say, a sub-node has no impact upon how sort|filter criteria is interpreted
- some of what you think as being sub-node behaviour, has been outsourced to the View
- on the whole I think it is ok ... but the Grid view should respect fieldname:xxx syntax IMO
[quote=benzo8 post_id=486878 time=1631412256 user_id=12621]
And in playing with this, I think I've found a bug:
If I select the Album Artists node, displaying in Grid Mode and type Genesis, it finds Genesis the band. If I click on that I get their albums, but if I then want to change to List mode or List (by Album) Mode, the Genesis search has become a "Any text" search - this is confirmed by then changing to Advanced Mode.
Similarly, if I'm already in List mode or List (by Album) mode, the text I type, despite being show as part of the breadcrumbs as past of the Album Artists node, is a free text search. This is counter-intuitive at best, particularly given how MM4 worked in this regard (it would jump down to the expanded sub-node, which, by definition, would be the Artist your were looking for).
[/quote]
I call that a bug too, but it is working as designed (apparently).
The documentation does not cover this, but search|filter criteria work differently in different contexts.
Your first query was in Grid view, where any supplied criteria looks only at album level criteria, i.e. the albumartist and album title attributes.
When you switched across to one of the list views, you were displaying tracks, so any supplied criteria looks at both track and album level attributes ... ie "Any Text"
If you wanted the same targeted result in a List view the criteria should be albumartist:genesis
But where it becomes entirely indefensible (IMO), is when you go in the reverse direction. ie:
[list]be in a list mode, and type albumartist:genesis ... all good so far[/list]
[list]then switch to Grid mode ===> and the result [b]is empty[/b] !!![/list]
[list]that is because despite what is inferred in the documentation, or is explicitly stated in the hover tool tip, a fieldname:xxx query is silently ignored in Grid mode, [/list]
[list]and it is also despite what I obviously intended via the supplied citeria[/list]
IMO MM5 suffers from thinking that it is an AI in some situations ... and can get it wrong
[quote=benzo8 post_id=486878 time=1631412256 user_id=12621]
Similarly, if I'm already in List mode or List (by Album) mode, the text I type, despite being show as part of the breadcrumbs as past of the Album Artists node, is a free text search. This is counter-intuitive at best, particularly given how MM4 worked in this regard (it would jump down to the expanded sub-node, which, by definition, would be the Artist your were looking for).
[/quote]
The new MM5 behaviour does have upsides ...
[list]it is easier to find Peter Gabriel if you have forgotten his first name[/list]
[list]you can regain more space for the centre panel, by leaving the left panel permanently closed[/list]
[list]All Text criteria is a powerful tool, and MM5 elevates it front and centre[/list]
it is not real easy to see what a "sub-node" is in MM5:
[list]every now and then I find out, but then I forget because it doesn't completely make sense (to me)[/list]
[list]each sub-node has its own state ... eg the last view that was in use, and any tailoring of the view (columns displayed, column display order, row sort sequence, etc)[/list]
[list]some sub-nodes have extra views (eg Years)[/list]
[list]some sub-nodes have extra options, eg. Albums view has Sort By options [/list]
[list]but, as you say, a sub-node has no impact upon how sort|filter criteria is interpreted [/list]
[list]some of what you think as being sub-node behaviour, has been outsourced to the View[/list]
[list]on the whole I think it is ok ... but the Grid view should respect fieldname:xxx syntax IMO[/list]