Re: [g-a-devel] xsettings and GTK+ a11y modules

[Willie Walker <William Walker Sun COM>]

Hi Eitan:

The xsettings change was made late in the 2.24 cycle, and the 
associated gconf property is now what determines whether or not the 
GTK+ a11y modules are loaded or not.  To allow people to prevent a11y 
from being activated, a couple changes were made to GAIL and the 
bridge:

NO_GAIL: http://bugzilla.gnome.org/show_bug.cgi?id=565110
NO_AT_BRIDGE: http://bugzilla.gnome.org/show_bug.cgi?id=563943

I'm not sure if these will do exactly what you want, but they might be 
worth a shot,

Will

On Apr 6, 2009, at 8:03 AM, Eitan Isaacson wrote:

> Hello folks,
>
> I have spent a lot of time trying to understand why simply unsetting
> GTK_MODULES is not doing what I expected: not load the gail and
> atk-bridge modules.
>
> I am writing a script that utilizes GTK+ but has no UI. It is
> important that a11y will be disabled in the script, so that it won't
> appear in the registry.
>
> Anyway, John Carr pointed out that GTK+ modules are loaded via an
> xsettings property called "gtk-modules" that in turn is set by
> gnome-settings-daemon.
>
> I have two concerns/questions:
> 1. How do I make sure that the xsettings values are removed before gtk
> is initialized.
> 2. It looks like the whole point of xsettings is that they are global,
> how do I disable the gtk-modules for one script while all current and
> future apps are not touched?
>
> Cheers,
>   Eitan.
> _______________________________________________
> Gnome-accessibility-devel mailing list
> Gnome-accessibility-devel gnome org
> http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel