Behaviour of "compare" (shift C)

Bugs which are supposed to be fixed in the next test version (not available yet)

Moderators: XnTriq, helmut, xnview, Dreamer

simon
Posts: 64
Joined: Wed Aug 23, 2006 4:51 pm

Behaviour of "compare" (shift C)

Post by simon »

Hello,

A long-standing issue (still in version 1.0) of the compare function (under windows 10 at least) is a follows:

When comparing 3 or 4 images, if one of them is closed, the remaining 2 or 3 are reorganized to fill the whole available space; which is fine.
In contrast, if one image is deleted, the behavior depends on whether 3 or 4 images were compared:
+ If 3 images were compared, the two remaining ones are expanded to fill the whole space, which is fine
+ In contrast, if 4 images are compared, the 3 remaining images are not reorganized. Furthermore, if one additional image is deleted, the remained two are reorganized only if they are contigu (i.e. they are not reorganized if the two remaining images are in the diagonal ... see screen copy attached).

It would be fine if the remaining images would be systematically reorganized after deletion, as occurs when an image is close without being deleted.

Thanks
Simon
You do not have the required permissions to view the files attached to this post.
simon
Posts: 64
Joined: Wed Aug 23, 2006 4:51 pm

Re: Behaviour of "compare" (shift C)

Post by simon »

Hi,
No way to have"compare" with 4 images behaving as with 2 or 3? (i.e. deleting one of them leads to an automatic reorganization)
I have just tested with on MP 1.4 (64 bits on windows 10 pro), the issue is still present.
Thanks
simon
User avatar
xnview
Author of XnView
Posts: 40595
Joined: Mon Oct 13, 2003 7:31 am
Location: France

Re: Behaviour of "compare" (shift C)

Post by xnview »

:bugconfirmed: Thanks to your detailed description I can reproduce the problem.
Pierre.