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 89690 - Need a way to change applet default settings
Need a way to change applet default settings
Status: RESOLVED DUPLICATE of bug 32225
Product: gnome-panel
Classification: Other
Component: libpanel-applet
2.0.x
Other All
: Normal enhancement
: ---
Assigned To: Mark McLoughlin
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2002-08-02 11:13 UTC by Calum Benson
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement



Description Calum Benson 2002-08-02 11:13:48 UTC
Currently, when you delete an applet from a panel and re-add it, you've
lost all that applet's preferences and you're back to the defaults.  If you
delete the panel, you lose the preferences of all the applets on there, and
you're back to the defaults next time you add them.  This sucks-- if I have
to type in SUNW and point gweather at Dublin one more time, I'll scream  :)

Ideally, any time you add an applet, it should use the same preferences
that were in force last time you deleted that applet from your panel.  Or,
if you already have another instance of that applet running, it should use
the preferences from that instance.  (If you have multiple instances
running, things get kind of sticky, but just picking the preferences from
any one of them would still be better than what happens now).

At the very least (but way more ugly), there ought to be a way of
specifying defaults on a per-applet basis in each applet's Preferences dialog.
Comment 1 Christophe Fergeau 2002-08-02 12:10:26 UTC
See 89311 for a related bug (though more specific)
Comment 2 Mark McLoughlin 2002-08-04 21:54:19 UTC
#32225 requests a 'save settings as default' option for applets.
Something along the lines of this will solve the problem

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