MP 1.6.3: Catalog Filter Match selection combination broken

Older bugs which are supposed to be fixed in 0.84. *** Please try to reproduce your bug and confirm the bug fix. ***

Moderators: XnTriq, helmut, xnview, Dreamer

Devil505
Posts: 7
Joined: Mon Mar 17, 2008 3:32 am

MP 1.6.3: Catalog Filter Match selection combination broken

Post by Devil505 »

Subject: MP 1.6.3: Catalog Filter Match selection combination broken

XnView: MP 1.6.3 - 64 bit
OS: Windows - 64bit

Combining "Rating" and "Categories" with AND matching doesn't AND but OR instead

Effect: Selects too many items


To reproduce:
1. set match to AND (and Global)
2. select a specific Rating
3. select a specific Category
Actual behaviour (bug): shows all items belonging in selected Rating as well as all in selected Category (OR matching)

Expected behaviour: Should show only items that are in both the Rating AND Category selected

Additional info:
The bug didn't come up with the current version (1.6.3) but with one of the last few updates, though I can't remember exactly what version introduced it - in older versions selecting Rating and Categories worked as expected for AND matching.
AND matching works as expected when only selecting different Categories - it's when trying to combine Rating and Categories that it simply shows both.
Another unexpected effect is that OR matching is glitched too: I've selected a Rating group with 57 objects and a Category with 530 objects, and matching OR shows 518 objects (while matching AND just shows 530) - no idea what 12 objects are not shown or why
User avatar
xnview
Author of XnView
Posts: 45062
Joined: Mon Oct 13, 2003 7:31 am
Location: France

Re: MP 1.6.3: Catalog Filter Match selection combination broken

Post by xnview »

:bugconfirmed: Thanks to your detailed description I can reproduce the problem.
Pierre.
User avatar
xnview
Author of XnView
Posts: 45062
Joined: Mon Oct 13, 2003 7:31 am
Location: France

Re: MP 1.6.3: Catalog Filter Match selection combination broken

Post by xnview »

This problem is supposed to be fixed in XnView MP 1.6.4. Please check and confirm the bug fix here.
Pierre.