MediaMonkey forum

ok, your suggestions and feature requests are being evaluated.
Some of them makes sense (and will be implemented), some of them does not make much sense (like Ctrl+Shirt+F for contextual search)

2. problem with the search syntax ... *Abc* doesn't work ... ie. *beefheart* doesn't find Captain Beefheart ... neither does *Beefheart*

I don't see why *Abc* should work currently, it has never worked and it is not listed in the tooltip: https://www.dropbox.com/s/p9qccjg48i9j1 ... s.png?dl=0

To find Captain Beefheart you can write just Beefheart (without the stars).
If anything, then the *Abc* is mostly used as infix syntax AFAIK.
i.e. I would expect that *bc* finds abcd (as bc is word infix).

@Ludek
I didn't notice a specific response from you on this issue so i'm not sure if its included in your list of things to consider.

Perhaps there is a technical reason for having to search this way but logically i don't believe that changing a View should require a different search statement. After all, the Collection & the Node have'nt changed. So having performed the search I just want to view the result in different formats (Views). Similar to calculating data in a spreadsheet then viewing the results as a Pie, Column, Line or Bar chart

Ludek wrote: ↑Tue Jun 04, 2019 2:20 pm I don't see why *Abc* should work currently, it has never worked and it is not listed in the tooltip: https://www.dropbox.com/s/p9qccjg48i9j1 ... s.png?dl=0

OK, so what does the 3rd item in that tooltip list say?

I have often suspected the patchy nature of your speed reading skills.

and I know what you are thinking ... "I have a lot of reading to do ... and reading things doesn't get bugs fixed ... and some people write too much"

Ludek wrote: ↑Tue Jun 04, 2019 2:20 pm some of them does not make much sense (like Ctrl+Shirt+F for contextual search)

It might not be important, nor elegant, but it makes sense (to me)

The idea was this:

• you said that there was concern that the just_type_for a _contextual_search behaviour can be hard to discover

• to help address this I suggested a tool tip for the looking glass saying something like "Global (whole database) search ... nb. use Ctrl+Shift+F for contextual search"

• this is shorter, and therefore better, than a tooltip saying "Global (whole database) search ... nb. for a contextual search, click somewhere on the grid or list, without selecting a specific cell, and then just use the keyboard ... a contextual search box will open for you"

• and I was deferring discovery of the just-type behaviour to the "tips" section of enhanced search drop down menu dbox that I was suggesting https://www.dropbox.com/s/1o9ftaj8ttfvv ... 2.png?dl=0

OK, so what does the 3rd item in that tooltip list say?

I have often suspected the patchy nature of your speed reading skills.

The 3rd item in that tooltip list says:
"Abc": finds whole words Abc (exact match)
i.e. I still don't see any *Abc* (and I don't think that it is related to my reading skills)

@Davo:
Don't worry, I read this whole topic carefully. As I already wrote, all the items are being considered and some are going to be implemented.

Ludek wrote: ↑Wed Jun 05, 2019 2:20 am i.e. I still don't see any *Abc* (and I don't think that it is related to my reading skills)

OK, while I am not yet ready to award you Best Reading skills, you do win the Best Vision prize ... (a fairly low bar btw, as you would realise if you knew anything about my situation )

When I switched across to the Monkey Groove skin I can read it a bit clearer, although the low opacity white on orange of Material Design (Dark) still defeats me. ... The rest of the UI with that skin causes me no difficulty. Just the shaded tool tips.

I looked at representative s/w from Microsoft, Google, Mozilla, and MM4 ... all of them have much better tool tips, than MM5, for people with low vision (see below). There is probably a Best Practice guideline somewhere describing the need for this .... something you could change?

https://www.dropbox.com/s/s95c1xjyt4ev0 ... n.png?dl=0

btw the Monkey Groove skin in 2179 also opens up a white screen which sits over the top of MM5
https://www.dropbox.com/s/z2q9gs93u2qjy ... t.png?dl=0

Well, I agree that the tooltips are not well readable in the "Material Design" like skins. To be improved in the next builds.
They are done according the Material Design specs, see: https://material.io/design/components/t ... .html#spec

EDIT: It seems that the issue was that they should have font "Regular" and not "Roboto", will be fixed in 2180

As for the extra window in the Monkey Groove skin, I see the same, added as https://www.ventismedia.com/mantis/view.php?id=15719

Ludek, sounds good. Thanks.