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 335895 - don't allow settings to be changed if read-only
don't allow settings to be changed if read-only
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Calendar
2.6.x (obsolete)
Other All
: Normal minor
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
: 335896 (view as bug list)
Depends on:
Blocks: 335923
 
 
Reported: 2006-03-24 21:32 UTC by Jeffrey Stedfast
Modified: 2013-09-06 11:13 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Description Jeffrey Stedfast 2006-03-24 21:32:45 UTC 
if the gconf keys are read-only, don't allow the user to change them by
de-sensitising the setting widget in the preferences dialog (and anywhere else
appropriate).

Other information:
Comment 1 Behdad Esfahbod 2007-09-21 06:16:02 UTC 
*** Bug 335896 has been marked as a duplicate of this bug. ***
Comment 2 Matthew Barnes 2008-03-11 00:27:04 UTC 
Bumping version to a stable release.
Comment 3 Matthew Barnes 2013-09-05 12:44:42 UTC 
Closing as OBSOLETE since we don't using GConf anymore, and read-only settings is a theoretical feature that I've never seen used.
Comment 4 Jeffrey Stedfast 2013-09-06 11:13:26 UTC 
I remember it being a big requirement at Novell to support "Lock Down", which was something I guess business customers wanted so they could prevent changes to certain settings.

Might make sense at kiosks, but I was never clear on what purpose it served otherwise...