Problems using SOME illegal characters in ML Search

[jph6t]

The “Search” and “Refine”* filters within the Media Library (ML)
are NOT working for some illegal characters.

* Must be enabled via Preferences to be visible

Winamp's behavior is identical for me (as in which illegal characters work or don’t work) regardless if I'm using the “Search” or “Refine” filter.

The following illegal characters work:

• *
• |
• /
• "
• <
• >

The following illegal characters do NOT work:

• ?
• \
• :

Note that ALL illegal characters seem to work when used via ML SmartView settings.

Can anyone confirm this behavior?
Is this a bug?

Note that I am using Winamp's current version ... v5.5

[jph6t]

Originally posted by jph6t
Can anyone confirm this behavior?

20+ views and no one can confirm or refute this behavior?
It's any easy test, just type one of the non-working characters in the ML's "Search" filter

[Sawg]

? (at the beginning at least) is used to tell the box to use the query logic and not simple searching. Using a question mark as not the first character works fine.

Backslash works fine. (Use it all the time to search by directory). Backslash alone will return everything, as it should.

Colon works fine, searching for the colon alone returns everything (time is a search field)

So, can't reproduce any of them.

[jph6t]

Originally posted by Sawg
? (at the beginning at least) is used to tell the box to use the query logic and not simple searching. Using a question mark as not the first character works fine.

Ahh yes, I remember seeing that. Never use that functionality.
If I put a question mark in quotes in the "Search" filter ("?") I get the desired sub-set.
So agreed, all OK with the question mark {?}.

Originally posted by Sawg
Backslash works fine. (Use it all the time to search by directory). Backslash alone will return everything, as it should.

Ahh, backslash tells the box to look at the physical files folder/path.
And if start typing the folder name after the slash I will get only files in that folder.
So agreed, all OK with the backslash {\}.

Originally posted by Sawg
Colon works fine, searching for the colon alone returns everything (time is a search field)

Ahh, I didn't think of the colon in the time field.
Yes, that would explain why I get everything.
So agreed, all OK with the colon {:}.

Originally posted by Sawg
So, can't reproduce any of them.

No bugs here. My bad.

Thank you Sawg for straightening out my confusion!