benzo8 wrote: ↑Sun Sep 12, 2021 7:03 am
Barry4679 wrote: ↑Sun Sep 12, 2021 1:48 am
it is easier to find Peter Gabriel if you have forgotten his first name
This is valid, but it wasn't a problem that needed to be solved - I could aways type Gabriel into the search box in MM4 and get Peter, along with a reminder that I really need to listen to Lamb again sometime!
I was going to counter by saying that the MM4 search box was context destroying, ie looks outside the current collection.
But I see that I have already forgotten MM4, and that the MM4 search box has the option of respecting, or ignoring the current context.
So I agree, MM4 was better in that respect, and it wasn't a problem that needed solving.
And It is now an extra migration gotya:
- The MM4 search box on the right is contextual by default
- MM5 has also has a search control on the right, but it is hard wired to global
And it is now klutzy:
- in MM5 you have an extra click to open the criteria box, it was always open in MM4
- as i say, that is now a global search
- once you ahve clicked and the the right hand criteria box has opened, a menu dropdown icon becomes visible, which contains a one-time option to toggle the search to contextual
- but if you take that option, you have to be attentive to your peripheral vison, because instead of using the criteria box that you had just opened (like MM4), it closes that box, an opens a different criteria box way over on the opposite edge of the screen
- and you must take the one-time option before to start typing your filter critera, because the option disappears once you type your first character
I presume that the change was made to de-clutter the toolbar, which has more going on in MM5.
benzo8 wrote: ↑Sun Sep 12, 2021 7:03 am
I think like a lot of these things, they're designed by coders whose ideas are great, but who are not UX specialists. There should be one overriding rule in interface design - it should be intuitive. Thinking for itself is one thing, but changing the scope of a search query because the diplay template has changed is counter-intuitive in the extreme.
I tried that argument during the Beta phase. Their response had some merit.
Paraphrasing their argument from the Beta Test phase:
Grid view shows only albums ... if the user types lamb, they will not expect to see albums like "Streetnoise" by Brian Auger and Julie Driscoll, just because it contains a track with title of "Vauxhall to Lambeth Bridge"
As already discussed, it is less good decision if the user has already made a query, and is just changing Views.
And they don't allow any way to manually override the mechanism, by making an explicit Grid View query like title:lamb