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 350397 - "Scale Image" doesn't keep settings
"Scale Image" doesn't keep settings
Status: RESOLVED DUPLICATE of bug 312950
Product: GIMP
Classification: Other
Component: User Interface
2.2.x
Other All
: Normal minor
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2006-08-08 09:32 UTC by Florian Cramer
Modified: 2008-01-15 13:10 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Florian Cramer 2006-08-08 09:32:41 UTC 
The "Scale Image" dialogue reverts to default settings each time after it has been used. When scaling a larger number of images, typically with the same settings, this behavior is highly annoying. 

The dialog should at least keep the last applied setting of the measuring unit (pixels / percent / inches ...) and the interpolation method (which should perhaps even be remembered across Gimp sessions), preferably also the Width/Height and resolution values.

Other information:
Comment 1 Sven Neumann 2006-08-08 11:16:56 UTC 
You can set the default interpolation method in the preferences. The unit is taken from the image, IIRC.

The dialog isn't meant to keep the settings because in most cases the last used values are not useful. IMO this report should be closed as NOTABUG but I am not going to close it right now. Perhaps the bug reporter wants to add some more information about the workflow so that we can perhaps find a solution to improve it.
Comment 2 saulgoode 2006-08-09 01:34:42 UTC 
One of the issues which I was hoping to tackle when I become more proficient at hacking the GIMP is providing better "last value" support for tools and menu items. I think this would prove beneficial to the GAP (as well as the "filter all layers" command) if some of the "kludged" plugins ("plug-in-wr-color-levels", "plug-in-wr-color-curves", etc) and the currently unavailabe "special case" tools and commands (such as the subject of this report) could be handled in a more generic and consistent manner. It would seem that saved last values of the type employed for plugins are critical to accomplishing this. 

My skill and knowledge levels are currently not sufficient to tackle this project but I do foresee it as worthwhile goal and hope to pursue it over the coming year. This comment isn't completely germaine to the bug report but if I understand things correctly, the report would need to be addressed as a part of my more ambitious plan.
Comment 3 Sven Neumann 2006-08-09 06:28:29 UTC 
saulgoode, improving this for plug-ins is already planned for the next development cycle and a lot of the work that has gone into 2.4 is related to it. But it is also almost off-topic to this bug-report, so please do not continue this discussion here.

I am going to close this bug-report as a duplicate of bug #312950.

*** This bug has been marked as a duplicate of 312950 ***