Page 1 of 1

Categories in search criteria

Posted: Fri Aug 05, 2022 6:54 pm
by Bob_in_MA
I'm not sure if this will be considered a bug, or just an unavoidable consequence.

I have a large hierarchy of categories, and I have set my preferences so that if I check a sub-category, all the upper level categories are automatically checked.

[Edited to add: Beside that checkbox, it says you can use Ctrl-click to select just the single category. This has never worked for me.]

I have category "Suitable for Printing" and sub categories of that for various size prints, and one subcategory "Printed", which I check after I've successfully made a print.

Now if I want to locate all the images I deemed suitable for 8x10 prints, but are not yet printed, I have one search criteria which says:
Categories : contains : [and the "8x10" category checked, which automatically checks "Suitable for Printing".]

Next I have:
Categories : does not contain : [and the "Printed" category checked. Again, this automatically checks "Suitable for Printing", but I uncheck it.]

If I search immediately, it will work as I intended. But if I save the search, when I reuse it the "Suitable for Printing" box in my second criteria has become checked even though I haven't reopened the drop-down box of categories.

Now the search will find nothing, because it thinks it must find images which both contain and do not contain the "Suitable for Printing" category. If I go into the drop-down box and uncheck "Suitable for Printing", it will again work as intended.

I feel a little silly bringing up such an arcane problem, especially since I have found XnView so incredibly useful, so I will understand if this just isn't worth the time to mess with.

Thanks!

Re: Categories in search criteria

Posted: Fri Aug 19, 2022 9:44 am
by xnview
:bugconfirmed: Thanks to your detailed description I can reproduce the problem.

Re: Categories in search criteria

Posted: Wed Aug 24, 2022 12:50 pm
by xnview
This problem is supposed to be fixed in XnView MP 1.02. Please check and confirm the bug fix here.