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 81015 - Option to reset to default values in all filters
Option to reset to default values in all filters
Status: RESOLVED OBSOLETE
Product: GIMP
Classification: Other
Component: Plugins
git master
Other All
: Normal enhancement
: Future
Assigned To: GIMP Bugs
GIMP Bugs
: 129927 132599 (view as bug list)
Depends on: 63610 120829
Blocks:
 
 
Reported: 2002-05-07 07:53 UTC by Maurits Rijk
Modified: 2018-05-24 10:44 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement


Description Maurits Rijk 2002-05-07 07:53:36 UTC 
I would like to see an option to reset a filter to its default state. Right
now you have to click 'Cancel' and then select the filter again (or use
Re-Show Last).
Comment 1 Maurits Rijk 2003-07-23 08:35:03 UTC 
This should/could be introduced with a general plug-in framework.
Comment 2 Maurits Rijk 2003-10-20 13:27:04 UTC 
Can be closed as soon as #120829 is implemented.
Comment 3 Maurits Rijk 2004-01-12 21:19:22 UTC 
*** Bug 129927 has been marked as a duplicate of this bug. ***
Comment 4 Raphaël Quinet 2004-01-13 12:26:35 UTC 
This bug could become increasingly important if some plug-ins are
automatically saving some or all of their settings for the current
session or permanently.  See bug #63610.  In this case, adding an
explicit way to go back to the default values (or to some other
presets, as suggested in bug #120829) would be the only way for the
user to get back to some sane values.
Comment 5 Sven Neumann 2004-01-13 12:53:21 UTC 
Nevertheless will we need to rewrite the PDB API to implement this
feature. As soon as this has happened we will get all this for free:
Reset to Factory Defaults, Save as Default, Save as Named Settings, ...
Comment 6 Raphaël Quinet 2004-01-13 17:20:38 UTC 
I agree, but until the new API is available we should make sure that
no new features are introduced that would make it necessary for the
user to have a "reset to defaults" button.  In particular, this means
that no plug-in should save some "session settings" or persistent
settings unless there is a way for the user to restore the defaults.
Otherwise, the user would not be able to go back to the default values
by just cancelling the plug-in as mentioned in the original report.
(cfr. the recent changes in the PNG plug-in mentioned in bug #63610)
Comment 7 Sven Neumann 2004-01-26 20:18:16 UTC 
*** Bug 132599 has been marked as a duplicate of this bug. ***
Comment 8 Michael Natterer 2004-07-26 21:07:53 UTC 
At least something:

2004-07-26  Michael Natterer  <mitch@gimp.org>

	* app/pdb/procedural_db.[ch] (procedural_db_free_data): new
	function which clears the whole list of data set by plug-ins.

	(procedural_db_free): use it.

	* app/actions/plug-in-actions.c
	* app/actions/plug-in-commands.[ch]: added action, callback and
	confirmation dialog for "Reset all filters to default values".
	Somehow addresses bug #81015.

	* app/widgets/gimphelp-ids.h: added a help ID for the new action.

	* menus/image-menu.xml.in: added it to the "Filters" submenu.
Comment 9 weskaggs 2006-06-16 15:43:01 UTC 
Upgrading milestone from Future to 2.6.
Comment 10 Martin Nordholts 2008-05-28 05:54:23 UTC 
Not a crucial issue and not much has happened in the last 3,5 years. Setting
milestone to Future.
Comment 11 GNOME Infrastructure Team 2018-05-24 10:44:54 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gimp/issues/27.