However, in the Help, I read that "If any wildcards are in pattern, the checkbox is ignored"...so why then DOES it matter in this case?
(I'm on ver .60)
I've emphasized the key words...because in my string, I believe I do have a wildcard...the "*"...thus, shouldn't that disable the pre/suffixing?The exact functionality is like this: IF "Exact Match" is unchecked AND "Fuzzy" is unchecked AND no wildcards are present in the search pattern THEN * is internally added to both ends of the pattern resp. of each pattern in a Boolean Expression
Code: Select all
v3.60.0152 - 27.03.05 12:50
* Find Files, Name pattern: slight change to the conditions of
internal "auto-asterisking" (active when "Exact Match" is
unchecked).
Before:
*ab*, ab*, *ab, a*b remain unchanged
ab -> *ab*
Now:
*ab*, ab*, *ab remain unchanged
ab -> *ab*
a*b -> *a*b*
Same with "?", e.g. a?b -> *a?b*, etc.Simple: the ANY-statement is much older! Things progress, man... in this case into the wrong direction. I'll remove it until I remember why I did in the first place.j_c_hallgren wrote:Ok...so how does that match up with the prior post plus help which appears to say that ANY wildcard in a user pattern would block the "*" pre/suffix?