Image Crop: number doesn't match cropbox and result

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

cdytoby
Posts: 4
Joined: Thu Mar 23, 2023 5:25 pm

Image Crop: number doesn't match cropbox and result

Post by cdytoby »

Subject: 1.4.3: Image Crop: number doesn't match cropbox and result

XnView: MP 1.4.3 64bits
OS: Windows 11 Pro 22H2 64bit

Sometimes, the number of image doesn't match crop visual box, and will affect result of crop.

Effect: Crop feature sometimes unusable

To reproduce:
1. Select whatever png image in XnView MP Browser tab
2. Open the image by double clicking the png file
3. Click Crop button
4. Choose Aspect Ratio 16:9, and then draw a square in the image.
5. There are 4 number up down (NumericUpDown?) Control on the right side of Aspect Ratio, mouse hover to the 3rd one, this is suppose to the width of the crop area
6. Scroll the mouse when mouse is on it
Actual behaviour (bug): When mouse is scroll down, the value decreased, the HEIGHT of the crop area is enlarged! and when mouse is scroll up, the value increased, the HEIGHT of the crop area is shrinked :bug:

Expected behaviour: Whe width value of the crop size should always control the width of the crop size, the height value of the cropsize should always control the height of the crop size.

Additionally, if I input number into that control, the image crop size will be completely something else other than the value I input, makes it unusable.
User avatar
xnview
Author of XnView
Posts: 43723
Joined: Mon Oct 13, 2003 7:31 am
Location: France

Re: Image Crop: number doesn't match cropbox and result

Post by xnview »

See issue for current status and some details.
Pierre.
User avatar
xnview
Author of XnView
Posts: 43723
Joined: Mon Oct 13, 2003 7:31 am
Location: France

Re: Image Crop: number doesn't match cropbox and result

Post by xnview »

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