4.6.0

[Brian J. Tarricone]

Jannis Pohlmann wrote:
> Am Thu, 19 Feb 2009 09:00:57 +0100
> schrieb Mike Massonnet <mmassonnet at gmail.com>:
> 
>> Le Thu, 19 Feb 2009 08:27:36 +0100,
>> Nick Schermer <nickschermer at gmail.com> a écrit :
>>
>>> Please drop:
>>> +    xfconf_g_property_bind (xsettings_channel,
>>> "/Xfce/UseCustomDPI", G_TYPE_BOOLEAN, custom_dpi_check, "active");
>>> +    xfconf_g_property_bind (xsettings_channel,
>>> "/Xfce/UseCustomDPI", G_TYPE_BOOLEAN, custom_dpi_spin, "sensitive");
>>>
>>> And use the toggled signal. Also do a gtk_widget_set_sensitive for
>>> the custom_dpi_spin. Those are property bindings and not set when
>>> the value in xfconf does not exist (ie. they do not behave as an exo
>>> binding).
>> Other way of fixing this will be to set the "default" value inside the
>> galde file, thus set the spin button insensitive.  The bind can be
>> kept and will act as if the initial value is correct.
> 
> No, that's not enough. This doesn't work when the user resets the value
> using "xfconf-query -c xsettings -p /Xfce/UseCustomDPI -r". In that
> case the sensitivity and checked state of the two widgets will be out of
> sync.

Yeah, I wonder if there's a decent way to 'fix' this in xfconf... kinda 
a 'do what I mean' sort of thing.  The idea of the binding api is to 
make things simpler for developers.  It's annoying to have stupid 
limitations like this.

	-brian