Re: Using GSettings to set for all users

[Bastien Nocera <hadess hadess net>]

On Thu, 2010-06-03 at 17:40 +0200, Ryan Lortie wrote:
> On Thu, 2010-06-03 at 10:30 -0400, Matthias Clasen wrote:
> > On Thu, Jun 3, 2010 at 5:15 AM, Richard Hughes <hughsient gmail com> wrote:
> > >              The only remaining bits to port is the "set default"
> > > button which sets the per-user settings for all users.  ....  I'm
> > > unsure on how to port this in a GSettings/dconf world.
> >
> > This was being discussed between Ryan and David just yesterday. I'm
> > sure Ryan can shed some light on the current plans.
> 
> So first of all, a little bit of knowledge about how dconf and GSettings
> handle access to the system defaults database:
> 
> Both systems support the concept of "context" to allow you to access
> something other than the user's normal database of settings.  You can
> give a context of "default" to access the system default settings, for
> example.
> 
> My current thinking for the write-to-defaults API is along these lines:
> 
> GSettings exposes via is_writable() if a key is writable at this moment.
> In the case that the key may become writable in the future, given proper
> policy kit authentication then this function still returns FALSE.  This
> allows preferences dialogs with "unlock" buttons to work properly and
> show the controls as insensitive while the dialog is "locked".
<snip>

With that API, wouldn't there be a case where the user could change the
value of a setting in between "make default" being called, and the
application actually writing those settings as defaults?

Or is that not something we worry about?