Could this have some text, above the radio buttons, to explain who|what the "preview" is? .... There is nowhere in the UI, where the part of the UI affected by this control, has an on-screen title of "Preview".
#2. Inconsistent names
MM5 UI is already complex enough ... don't make it more complex by referring to the same thing, using different names
(i) what is the "Search Bar"? ... I have not seen anything in the UI with that title, or tooltip.
Do the controls in that box just relate to what is called "Whole Library Search" elsewhere?
BTW it is already hard enough to know which is named what ... ie. here (a) has a title, but (b) does not have a title ... they both should have titles.
(ii) Are these the same thing, just with different names?
#3. Missing tooltip
(A) has a explanatory tooltip, which also discloses the keyboard shortcut
(B) has nothing (?!) ... even though it also has a keyboard shortcut .... AND it is one of the more complex and confusing areas of the MM5 design (eg. Contextual search vs whole db search, as well as unexpected right click behaviour, and initially hidden dropdown menu)
I think that this is the 3rd time I have made this point ... so far without comment nor corrective action ... why? ... are you having trouble describing your own design?
#4. Search syntax tips
I have made this comment before; quoted below
You don't agree? ... I think the current text looks juvenile, wanky & doesn't aid understanding due to the "examples" not relating to anything relevant to the user ... This syntax will be new to everybody, including customers upgrading from MM4, so it is important. ... I get the programmer reference, but do you think that all your customers are going to be programmers?
Barry4679 wrote: ↑Fri Jul 26, 2019 1:03 amSearch tips dbox needs improvement.
#6. ... using Foo Bar for all your examples is not a good idea IMO ... are you expecting that MM5 clientele will be restricted to just Computer Programmers? ... I think that it makes generally confusing, what should be helpful documentation ... and it looks really lame IMO
Suggest you use some music related two word example, eg. Pink Floyd
#7. does a poor job of explaining last item above ... suggest "pin" | finds whole words (e.g. Peace Pin Boogie, but not Pink)"foo | finds words beginning with foo (e.g. Bar Food or foObar )
+Foo | finds words beginning with Foo (case-sensitive, e.g. Football)
"Foo" | finds whole words (e.g. FOO or foo)
#8. Suggest you also include an example for the Album Artist tag ... to clear up any doubt about how to handle the blank space between Album & Artist ... I know that you handle it with, or without, the space (which is good ) ... but it would be good to reduce anxiety levels by by giving an examplefieldname:foo | restricts search to a specific field. For example:
artistfoo | finds words beginning with foo (in Artist) e.g. Bar Food or föObar
yearX..Y | finds matches in range X to Y
rating: X. | finds matches wth X stars or more
The lack of kerning in the instructions font make it appear that there is a blank space between "year:X.." and "Y"
This misunderstanding produces confusing results.
Instead of Year:X..Y
It would clearer if you had a real example, like Year:2000..2001, which wouldn't be so badly affected by the font