Use atspi_is_initialized to decide whether to expose p2p connection
authorMike Gorse <mgorse@suse.com>
Sun, 16 Jun 2013 19:04:01 +0000 (14:04 -0500)
committerMike Gorse <mgorse@suse.com>
Sun, 16 Jun 2013 19:04:01 +0000 (14:04 -0500)
commit683739dea15d7c02c217a404d8c5d9d7af076a57
treedc5778c24e15b4f8afed6f58cad2b25f37c61d0e
parent58e70049be2e9d80f82225304cf2b6a1529939f1
Use atspi_is_initialized to decide whether to expose p2p connection

Previously, direct D-Bus connections were not exposed if AT_SPI_CLIENT
was set in the environment, since they are causing deadlock if the
application and the AT are in the same process. However, AT_SPI_CLIENT
was only being set by pyatspi, meaning that libatspi consumers not using
pyatspi (Javascript embedded in gnome-shell that uses the libatspi
introspection bindings directly, for instance) would still have problems
when attempting to inspect their own accessibles.

Also removed the code in event.c to disable main loop context switching
when AT_SPI_CLIENT was set. Modifying it to also check
atspi_is_initialized would cause deadlock with gnome-shell when Orca is
running. Hopefully that code is not needed anymore.
atk-adaptor/adaptors/application-adaptor.c
atk-adaptor/event.c
configure.ac