No subject

"The keys may be pressed in any order, with the exception that if the final=
 key
name is prefixed with an exclamation point then it must be pressed last. The
exclamation point prefix means that the
command is executed as soon as that key is pressed. If not used, the command
is executed as soon as any of the keys is released."

I also should add to my problem list the following:
- When using the AT-SPI2 driver there is no cursor tracking. For some reason
  the display does not follow the cursor, even though cursor tracking is on.

>> If there is going to be some sort of AT-SPI2 driver development, I
>> think that the driver should use the library interface to AT-SPI, instea=
d of
>> directly calling the D-Bus methods - this way the code will probably look
>> better and it will be more tolerant to API changes.

 > Except that there is no such thing any more. With AT-SPI1 we could use
 > one, but for AT-SPI2 only the server part really has bindings.

Isn't libatspi just this. It is part of at-spi2-core package. From it's
README:

"[libatspi is a] C library for use by ATs [(Accessibility Service providers=
)].
Wraps the various D-Bus calls, provides an interface for listening to event=
s,
and caches some information about accessible objects. Also contains some
functions used by at-spi2-atk."

This library is also used by the at-spi Python bindings used by Orca.

 > X window is mostly out of the picture actually, Glib shouldn't be
 > involved much, so it's more about the brltty codebase, AT-SPI and D-Bus,
 > you're welcome for questions etc. in any case.

Thank you! I try to grasp the workings of at-spi2, but it is not at all well
documented.

--=20
Aura