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 88433 - Allow "Rollback" of preference change
Allow "Rollback" of preference change
Status: RESOLVED DUPLICATE of bug 95110
Product: gnome-devel-docs
Classification: Applications
Component: hig
unspecified
Other other
: Normal enhancement
: ---
Assigned To: Havoc Pennington
Havoc Pennington
Depends on:
Blocks:
 
 
Reported: 2002-07-17 13:51 UTC by Andrew Sobala
Modified: 2020-12-04 18:21 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement


Description Andrew Sobala 2002-07-17 13:51:45 UTC 
If would be really nice if preference changes could be cancelled; that is,
the changes are made in "real-time" like they are now but if the user
doesn't like them he can hit "cancel" and they all roll back to before the
dialog was opened.

I'm filing this is gconf on a hunch (API change?), but it might need to go
somewhere else.
Comment 1 Ben FrantzDale 2002-07-18 00:12:28 UTC 
This is a human interface issue.

My understanding is that the current behavior is intentional---that
even with a way to revert, most people didn't use that functionality
so it was just getting in the way. Granted, some people did use "revert".

Personally, I think the current behavior minimises clutter more than
it detracts from functionality.
Comment 2 Andrew Sobala 2002-07-18 16:01:45 UTC 
It's just that some capplets - like the sawfish ones - have a "Revert"
button (which is useful and hardly clutters the UI).
Comment 3 Havoc Pennington 2002-07-21 23:17:49 UTC 
My .02 is that either a "Defaults" or a "Undo" button seems reasonable
for prop dialogs (and fairly simple to implement using gconf), but 
if you have both Defaults and Undo buttons it seems kind of cluttered.
Comment 4 Andrew Sobala 2002-11-10 18:18:56 UTC 

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