Humm I'm seeing a problem here. What about GNOME/GTK+ applications launched outside a gnome-session? (for example people using KDE).
They won't get the gtk-modules XSETTING and then they won't be accesible at all. I guess that the solution that Kristian pointed (gtk loading auto loading "runtime modules" provided by the platform) may solve this problem: - gtk_init --> load_init_modules: - gnome a11y module --> Check a11y gconf key --> load gail and friends - bug-buddy module --> install segv handler. the downside of this method is that if we have installed gnome a11y modules then we are adding a little bit of overhead to only-gtk applications (loading gnome-module because it is installed, loading gconf, checking a11y). Salu2 On 7/26/06, James Henstridge <[EMAIL PROTECTED]> wrote: > On 26/07/06, Fernando Herrera <[EMAIL PROTECTED]> wrote: > > On 7/26/06, James Henstridge <[EMAIL PROTECTED]> wrote: > > > 1. gnome-settings-daemon is modified to set the gtk-modules XSETTING, > > > based on the existing gconf key. If accessibility is enabled, it sets > > > it to "libgail:libatk-bridge". > > > > So if we are moving to this solution we could also add a > > "gnome_segvhandler" module to this XSETTING in order to get gtk_init > > load this module installing the segv handler, right? > > That would probably also be possible. > > James. > _______________________________________________ Gnome-accessibility-devel mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel
