XYplorer Beta Club

Hey,

Okay so I'm reading the help about Column-wise Selection Filter (ie select items using another column than Name) and I can't really get it to work

I want to make selection of files that are at least 100 000 000 bytes (~100MB we'll say it is ) ie. 9 digits, and I do use "Bytes" for my size column (ie exact bytes number, with thousand sep (space for me))

I tried both "size:### ### ###" and "size:#########" but I never get anything selected
I did also try "size:*### ### ###" (and "size:*### ### ###" too) but nothing.

If I switch to "MB" (Size column format) and do "size:###,## MB" it works (even for 1 234,56 MB files without a * first!)

BTW same thing in regexp mode, I mean "size:>([0-9]{3})" did work (all files >= 100bytes) ; but sadly "size:>([0-9]{6})" nor "size:>([0-9]{3}) ([0-9]{3})" did work

Last Minute: if I use "Raw Bytes Count" (ie no thousand sep) it does work:
size:>([0-9]{9})
size:#########

so... is it a bug, or is there a trick I don't know??

I did not read your post in detail but i can refer you to this post:

http://www.xyplorer.com/xyfc/viewtopic. ... ght=regexp

because it seems somewhat similar, but dont curse me if i got you wrong.

Thanks.. some other regexp on that topic, but I actually have the same problem with them too, works fine with "Raw Bytes Count", but not with "Bytes" and the thousand separator...

I tried "size:#.###.###" (. is my 1000 sep) and it works alright. I guess your "space" is not a space but some weird char looking like a space??

admin wrote:I tried "size:#.###.###" (. is my 1000 sep) and it works alright. I guess your "space" is not a space but some weird char looking like a space??

hmmm.. oh yeah, confirmed! Stupid MS!!

Seems it's using A0 (chr(160)) instead of 20 (chr(32)) for some weird reason... Gotta write that down somewhere and remember to use Alt+0160 instead of space when I need to.

jacky wrote:

admin wrote:I tried "size:#.###.###" (. is my 1000 sep) and it works alright. I guess your "space" is not a space but some weird char looking like a space??

hmmm.. oh yeah, confirmed! Stupid MS!!

Seems it's using A0 (chr(160)) instead of 20 (chr(32)) for some weird reason... Gotta write that down somewhere and remember to use Alt+0160 instead of space when I need to.

I think it's a "hard space" (does not wrap).

admin wrote:I think it's a "hard space" (does not wrap).

Yeah.. Still kinda stupid IMO since for people using . (for example) it does wrap, so why make it so special?? Esp. since it can't be easilly done, as neither Ctrl+Space nor Alt+Space does anything but a regular space....

bah, w/e

jacky wrote:Esp. since it can't be easilly done, as neither Ctrl+Space nor Alt+Space does anything but a regular space....

Did you try this: size:#?###

Also beware if you use a "-" in some programs. Sometimes it's a 002D (Hyphen) other times, usually from a word processor, it's 00AD (Soft hyphen). There may be others but the " " and "-" have caught me several times!

admin wrote:Did you try this: size:#?###

Yeah, and actually Im not sure why but ###?###?### will select will items with a size of 9 digits, while ### ### ### (with alt+0160 of course) will select all thoose with a size of at least 9 digits...

jacky wrote:

admin wrote:Did you try this: size:#?###

Yeah, and actually Im not sure why but ###?###?### will select will items with a size of 9 digits, while ### ### ### (with alt+0160 of course) will select all thoose with a size of at least 9 digits...

Well, I am sure why : wildcards are automatically added at both ends of your pattern (*...*) IF no wildcards are present in the pattern. The same is done with search patterns... (which the reason of the "Exact Match" box: to supress this service).
Maybe I should not do this with the selection filter??

admin wrote:Well, I am sure why : wildcards are automatically added at both ends of your pattern (*...*) IF no wildcards are present in the pattern. The same is done with search patterns... (which the reason of the "Exact Match" box: to supress this service).
Maybe I should not do this with the selection filter??

Oh right... well yeah maybe here it should be an Exact Match, or you should consider # being a wildchars just like ? and * are (I mean after all... ) Cause with ### one might want all files >=100 and <1000; or else you'd use *###

jacky wrote:... or you should consider # being a wildchars just like ? and * are (I mean after all... ) ...

Yes, that should be no problem.