Re: [g-a-devel] A11y always-on in gnome-shell and GTK+ (was Re: A11y always-on in gnome-shell)
- From: Mike Gorse <mgorse alum wpi edu>
- To: Piñeiro <apinheiro igalia com>
- Cc: gnome-accessibility-devel gnome org, desktop-devel-list gnome org
- Subject: Re: [g-a-devel] A11y always-on in gnome-shell and GTK+ (was Re: A11y always-on in gnome-shell)
- Date: Mon, 18 Jun 2012 23:05:00 -0400 (EDT)
On Mon, 18 Jun 2012, Piñeiro wrote:
On 06/15/2012 06:52 PM, Bastien Nocera wrote:
The next step would be to make the atk-bridge not snoop on keys when
there are no clients, so as to reduce the overhead.
Strange, I thought that it was already the case, atk-bridge not
registering to any event (key snooping included) unless one client is
listening.
Mike, could you confirm that?
It probably should be doing this, but, alas, it isn't. Right now
atk-bridge has no way of knowing whether any keystroke listeners are
active. I think we would want to do one of the following:
- add a DBus property that indicates whether any keystroke listeners are
present, and have at-spi2-registryd send a PropertiesChanged signal as
appropriate when this changes.
- Have at-spi2-registryd send signals when a listener is added or removed.
Add a method to retrieve the currently-active listeners. Perhaps have
atk-bridge send keystroke notifications to the listening applications
directly rather than at-spi2-registryd being in the middle.
- Take at-spi2-registryd out of the business of handling listeners
altogether. When a new application starts, have libatspi somehow notify it
if a keystroke listener is present.
The first option seems easiest, and I'm tempted to go with it since I
think that the goal is to eliminate these listeners in the medium to long
term.
-Mike
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]