Comment 3 for bug 605257

(is there really no 'reply' for comments, like there is in bugzilla?)

> It's always needed to restart session in order to activate at-spi?

I *think* so. In this case anyway.

> Could wiican activate at-spi avoiding the user to manually activate
> it?

I don't *think* so.

You can run an individual app in an environment in which you enabled accessibility support, even if that support is not enabled session-wide, e.g.:

    $ env GTK_MODULES=gail:atk-bridge gedit

But in this case, Wiican is not the app that needs to have AT support enabled. It's all the other apps.

As an experiment, try *disabling* AT support for the session, log out, log back in, then try the snippet. For each app you launch setting GTK_MODULES, you should see events; for each one you launch without first setting GTK_MODULES, you won't see events.

As for what would be more convenient for the user.... I think that might depend on the user and thus need to be a preference. Perhaps go with option 1 (ask the user), but add one of those 'do not show this dialog again' checkboxes.

Pressing 1+2 each time won't kill anyone, but it's kind of a drag. Why is this needed? <takes a guess> Perhaps a device could have a single mapping and that mapping could in turn have application-specific items??

Ya know, that might actually be kinda cool [she says, not having actually looked at the code to know if it would make sense. ;-)] Consider the case where there's a default mapping that works perfectly for all apps but Foo. In Foo, only one button needs to be re-mapped. It would be nice to just remap that one button and have the rest be inherited from the default map.