After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 642516 - user unfriendlyness when bulk resizing images
user unfriendlyness when bulk resizing images
Status: RESOLVED FIXED
Product: gthumb
Classification: Other
Component: general
2.12.x
Other Linux
: Normal normal
: ---
Assigned To: Paolo Bacchilega
Paolo Bacchilega
Depends on:
Blocks:
 
 
Reported: 2011-02-16 22:25 UTC by Paolo Benvenuto
Modified: 2015-12-18 13:39 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Paolo Benvenuto 2011-02-16 22:25:59 UTC
Reproduce it:
- select various images in browser mode, and hit tools -> resize images...
- in the resize dialog, select %. Suppose width=70 and height=70
- write a new value in the width field, i.e. 80 (%)
- hit the tab key twice in order to arrive at the height field
- write a new value, different, i.e. 80 (%)
- press the Exec button or hit the equivalent keystroke: the image is resized with the old height value, in this case 70%, not 80%.

In order to get the 80%, you must press tab after changing the height value, or you must hit the tab key or perform anothe operation in the dialog itself befor pressing the execute button.
Comment 1 Paolo Bacchilega 2011-02-21 20:23:17 UTC
I cannot reproduce this one with current master version.
Comment 2 Anton 2012-01-11 01:45:02 UTC
I can confirm a similar behavior in 2.14.1

Steps to reproduce:
 1. Resize a first picture with w/50% h/50%
 2. Save it and close it.
 3. Open a new image and go to resize again.
 4. The "Height" value will be still 50% in the form, however the actually value is 100% and the image shown with the broken ratio.

Also, it would be helpful to have a "keep proportional ratio" checkbox to keep both values the same. Often, I just want to resize my picture to 50% (or 1024 x whatever) of it's original size.
Comment 3 Michael Chudobiak 2015-12-18 13:39:32 UTC
I believe this works fine in the current version, 3.4.1. Closing as fixed, but please re-open if problems persist.