Hi,
Starting accessibility on-the-fly should certainly be possible now that
GTK modules can be loaded on demand via an XSETTING[1], no? A major
reason for this support was to get accessibility working dynamically.
Is there a technical reason this isn't adequate?
-Alex
[1] Bug #117236
Bill Haneman wrote:
The 'accessibility' gconf key has to be set before any apps start, since
there is currently no means for loading accessibility support "after the
fact".
_______________________________________________
desktop-devel-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/desktop-devel-list
