On 05.03.2015 05:14, Mike Gorse wrote:
Not really an answer, but the call to process_deferred_messages() is the
interesting bit here. When an AT-SPI event is received, it is queued for
later processing via process_deferred_messages, which is executed either
in an idle handler or at the end of a
Not really an answer, but the call to process_deferred_messages() is the
interesting bit here. When an AT-SPI event is received, it is queued for
later processing via process_deferred_messages, which is executed either
in an idle handler or at the end of a method call. Iirc this is done in
orde
Hey, thank Tou for quick answer.
On 02.03.2015 18:39, Alejandro Piñeiro wrote:
On 02/03/15 18:08, Lukasz Stanislawski wrote:
Hello everyone,
Currently, I'm developing small C application using libatspi and
encountered some problems with event processing.
What I have is two event listeners A a
On 02/03/15 18:08, Lukasz Stanislawski wrote:
> Hello everyone,
>
> Currently, I'm developing small C application using libatspi and
> encountered some problems with event processing.
>
> What I have is two event listeners A and B registered with
> atspi_event_listener_register() on different at-sp
Hello everyone,
Currently, I'm developing small C application using libatspi and
encountered some problems with event processing.
What I have is two event listeners A and B registered with
atspi_event_listener_register() on different at-spi events. Inside main
loop assume that A listener can
