XnView Software

I have not been able to pin down the circumstances, but IMHO the Resize dialog may be "messed up". Sometimes the resize does not respect the image aspect ratio, even with "Keep Ratio" enabled. This has happened 3 times... in all cases the resulting image's horizontal dimension is much less than I indicated, resulting in a "squat" image.

Also, sometimes the dialog appears to be multiplying resolutions (or something similar) because sometimes changing the DPI generates enormous pixel sizes, much larger than a simple multiple of the (new dpi)/(old dpi)... This latter issue has happened several times.

Restarting XnView seems to help with these issues, though in one example I gave up trying and did the resize in PhotoFiltre.

Has anyone else encountered a similar problem?

Yes there is a new bug

Looks like it is happening because of this change:

Changed:
* Resize value kept - http://newsgroup.xnview.com/viewtopic.php?t=14554

XnView always shows last used values ignoring actual image ratio. If the ratio changed between the last image and the current one then the values are quite off and the only way to fix it is to uncheck "keep ratio" and set the values manually.

Pierre et alter

Hello !

• Maybe that I showed HERE could help ?

KR
Claude
Clo

I can confirm this!

Since the last version XnView remembers the picture size in the "print size" dialog since the first resize.

For example:

- resize a picture with size 800x600 -50% to 400*300
- now close "resize" dialog
- open new picture with size 400*600 an press OK in "resize" dialog
- now new picture has 400*300 dots just like picture 1

or

Change the size of a picture to 50%. Then undo the change. Repeat size change to 50%. The picture is only 25% in size now.

________________________________

Matthias

This is a serious bug that has strongly affected my use of XnView.

Please, Pierre, fix it soon!!!

JohnFredC wrote:This is a serious bug that has strongly affected my use of XnView.

Please, Pierre, fix it soon!!!

wiil be fixed in a 1.93.2 this week

After some moderate testing I conclude that this issue appears to be fixed in version 1.93.2

Thanks!

Closed.