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 777627 - 'Use default value' toggle button does not update when setting is changed externally
'Use default value' toggle button does not update when setting is changed ext...
Status: RESOLVED OBSOLETE
Product: dconf-editor
Classification: Other
Component: general
3.22.x
Other Linux
: Normal normal
: ---
Assigned To: dconf-editor maintainer(s)
dconf-editor maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2017-01-22 23:01 UTC by Michael Catanzaro
Modified: 2019-03-20 10:39 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Michael Catanzaro 2017-01-22 23:01:38 UTC 
dconf-editor watches the current value of settings and immediately updates the UI when the setting is changed, so you can open an app's preferences dialog and dconf-editor at the same time, toggle a setting back and forth in the preferences dialog, and watch the current value of the setting update in dconf-editor. However, the 'use default value' toggle button does not update and thus remains set to ON even when the current value is clearly no longer the default.
Comment 1 Arnaud B. 2017-01-23 01:22:57 UTC 
(In reply to Michael Catanzaro from comment #0)
> However, the 'use default value' toggle button does not update and thus
> remains set to ON even when the current value is clearly no longer the
> default.

There’s a problem here, but that’s not the one you think there is. ^(^

In fact, you probably don’t want the “Use default value” and “Custom value” to update without your consent, as that’s where you are choosing the value you want to apply.

But that doesn’t sound obvious. So that’s clearly a bug. Not easy.

One solution might be to have a triple button “Use current value/Use default value/Use custom value” in place of the current “Use default value” toggle. I’ll try that.
Comment 2 Michael Catanzaro 2017-01-23 13:46:35 UTC 
I don't think that's a good idea. The toggle is nice and simple; adding a third state is going to make it a mess. If the toggle is intended to do anything other than simply indicate whether the setting is currently set to the default value, then I think that is a problem.
Comment 3 GNOME Infrastructure Team 2019-03-20 10:39:08 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/dconf-editor/issues/19.