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 794826 - Do not default to last used filter settings
Do not default to last used filter settings
Status: RESOLVED FIXED
Product: GIMP
Classification: Other
Component: General
git master
Other All
: Normal blocker
: 2.10
Assigned To: GIMP Bugs
GIMP Bugs
: 795169 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2018-03-29 23:26 UTC by Jehan
Modified: 2018-04-11 18:50 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jehan 2018-03-29 23:26:02 UTC
There are a few filters where people seem to expect to start with a neutral state. Many of the color filters for instance, like the "Hue-Saturation" which Aryeom uses a lot and expects to start with neutral values.

Ankh was also noting that he had the problem with Levels. He was especially annoyed since he was using the filter on huge images (as always!) and was saying that made him wait for 10 minutes upon opening the dialog just to reset and wait again. This is a bit counter-productive.

I am wondering if we could not improve a bit this situation.
Maybe a blacklist for autosaving settings? Or an option for people to opt-out themselves for some dialogs and keep autosaving on others?
Comment 1 Jehan 2018-03-29 23:27:47 UTC
Setting to blocker because that is new stuff and it might be worth straighten things up before stable release, though that is obviously not a serious blocker if we don't find a suitable solution by the time we decide to release.
Comment 2 Øyvind Kolås (pippin) 2018-03-29 23:37:30 UTC
Levels behaving this, 'more consistent' way has been annoying me as well - and I agree on the blocker status. A way of opting out of the default mechanism of remembering last values for all types of filters would be good.
Comment 3 Elle Stone 2018-03-30 12:03:07 UTC
It would be wonderful to have a way to opt out of having the last values used being automatically loaded.

I use Levels, Exposure, and the Hue-Chroma tool - all on the Colors menu - quite a lot, and having the image displayed with "last used values" every time I use these tools is not at all helpful. Especially the Hue-Chroma tool, having to reset that tool to "no change" before I can dial in the desired change is quite a visual disruption.

Same is true of all the other operations on the Colors menu - almost never are the "last used" values what I want for the next time I use these operation.
Comment 4 Michael Natterer 2018-03-30 12:39:17 UTC
It's the plan to do this, but don't we already have a bug about it?

I even have a patch already...
Comment 6 Michael Natterer 2018-04-01 12:49:04 UTC
Fixed in master:

commit fe932fe7ad5acd3a05be2bb6e934583881c26e7a
Author: Michael Natterer <mitch@gimp.org>
Date:   Sun Apr 1 14:41:20 2018 +0200

    Bug 794826 - Do not default to last used filter settings
    
    Add GimpGuiConfig::filter-tool-use-last-settings wchich defaults to FALSE.
    
    Honor the new option in gimp_gegl_procedure_execute_async() and add
    it to prefs -> dialog defaults.

 app/actions/gimpgeglprocedure.c  |  6 +++++-
 app/config/gimpguiconfig.c       | 14 ++++++++++++++
 app/config/gimpguiconfig.h       |  1 +
 app/config/gimprc-blurbs.h       |  3 +++
 app/dialogs/preferences-dialog.c |  4 ++++
 5 files changed, 27 insertions(+), 1 deletion(-)
Comment 7 Michael Natterer 2018-04-11 18:50:10 UTC
*** Bug 795169 has been marked as a duplicate of this bug. ***