Quicksearch size selector comparisons

[jupe]

This issue seems to affect both bitnesses, and AFAICT has been around for years. I am getting some confusing returns when using the quicksearch size: selector with comparisons.

I wrote up a quick repro, as an example when I run the repro, < has no return, and <= AND >= both contain the colored folder .ico's you supply (among other bogus results).

Code: Select all

$r=; foreach($c, '<|<=|>|>=') { $r .= "#### $c<crlf>". quicksearch("size: $c 1MB /fn", <xypath>,, n) .<crlf 2>; } text $r;

Actually after I made up the repro, I've now discovered the issue is maybe only the "1MB" unit, eg. if use KB results seem to be as expected.

[admin]

Code: Select all

$r=;

Shocking right from the start...

[admin]

Okay, if you use a unit like MB in the search term, then the sizes of the files are converted to that unit* and they are rounded up* (unless you use a fractional number like "1.2MB"). This explains what you see.
* I remember that there was a good reason for this, but I don't remember the reason out of my head right now, and no time to look it up.

Unfortunately I cannot change this now since it's been like this for many years.

However, I could add something to force converting the size given in the search term to raw bytes *before* passing it to the comparison routine. That way you would get the results you (and admittedly me) expected.

Well, thought about it again, and the results are so strikingly rubbish, that it can only be called a bug. So I'm just going to fix it.