1. 18 Jul, 2019 2 commits
    • Mike Gorse's avatar
      Add a sender to the AtspiEvent struct. · 8decb77c
      Mike Gorse authored
      Normally, this is set to the application / root accessible from the
      application corresponding to the event source, but screen-reader-generated
      events are actually generated by the screen reader. The sender is set based on
      the application that sent the signal over dbus, so, in the latter case, this
      will be set to the screen reader.
      
      Per discussion at orca#36
      8decb77c
    • Mike Gorse's avatar
      Refactor the API for the screen reader to notify listeners of its status · 36a621aa
      Mike Gorse authored
      Remove atspi_text_notify_reading_position, and instead add a region_changed
      signal. Also make the dbus API more like the API used for other events.
      
      Per discussion at orca#36
      36a621aa
  2. 17 Jun, 2019 2 commits
  3. 16 Jun, 2019 1 commit
  4. 15 Jun, 2019 2 commits
  5. 13 Jun, 2019 1 commit
  6. 11 Jun, 2019 1 commit
  7. 07 Jun, 2019 1 commit
  8. 22 May, 2019 2 commits
  9. 21 May, 2019 2 commits
  10. 20 May, 2019 2 commits
  11. 10 May, 2019 1 commit
  12. 06 May, 2019 3 commits
    • Carlos Garnacho's avatar
      Only use x11 device event controller implementation on X11 sessions · c52d4c20
      Carlos Garnacho authored
      A wayland compositor would be impervious to the actions performed
      there, so it only could only partially work with other X11 clients.
      That doesn't seem like the intended effect.
      c52d4c20
    • Carlos Garnacho's avatar
      Do not rely on getenv("DISPLAY")!=NULL to assume it is a X11 environment · 3bb82072
      Carlos Garnacho authored
      Change/add checks around the AT_SPI_BUS root window property handling so it
      is only done if the session is a real X11 one.
      
      These checks used to work on wayland sessions, as there still is a X server
      to poke, it's strange to use as a side channel but that's about it. However
      in the future mutter will start Xwayland on demand, the DISPLAY environment
      variable will definitely exist so checking for it is definitely not
      sufficient, and opening the display will unintendedly spawn Xwayland.
      
      It is debatable that this should happen in Wayland sessions at all, so let
      the org.a11y.Bus fallbacks take over.
      3bb82072
    • Carlos Garnacho's avatar
      bus-launch: Do not poke X11 to check at-spi-bus-launcher is running · 25f1cc6c
      Carlos Garnacho authored
      The already_running() check first gets the AT_SPI_BUS root window property,
      then tries to open it to check if it exists. For it to exist though there
      must be another at-spi-bus-launcher process around with the org.a11y.Bus
      name.
      
      It seems we can just defer the uniqueness check to g_bus_own_name(), as
      we will get the "name lost" callback right after failing to acquire the
      unique name. Doing it this way works for both x11 and non-x11, and avoids
      assumptions on what the current windowing actually is.
      25f1cc6c
  13. 05 May, 2019 2 commits
    • Mike Gorse's avatar
      More updates related to reading position notifications · 218af4ee
      Mike Gorse authored
      Allow a client to receive notifications through AtspiEventListeners. This
      involves special casing, since the event is generated by the screen reader,
      not the GUI, and is, thus, handled by a different DBus interface, but, from
      the client's perspective, it looks like a normal AT-SPI event.
      Also renamed atspi_text_notify_read_position to
      atspi_text_notify_reading_position and fixed a few warnings.
      218af4ee
    • Mike Gorse's avatar
      Add atspi_text_notify_read_position · 2e14dcd1
      Mike Gorse authored
      #10
      2e14dcd1
  14. 30 Apr, 2019 2 commits
  15. 15 Mar, 2019 1 commit
    • Mike Gorse's avatar
      Remove idl directory · 52968ad5
      Mike Gorse authored
      These files have never been used, are not actually written in a language
      that can be automatically parsed, and have not been part of the tarball
      for some time. Removing them to avoid confusion, since having them in the
      repository makes it appear that they are used.
      52968ad5
  16. 12 Mar, 2019 4 commits
  17. 10 Mar, 2019 1 commit
  18. 04 Mar, 2019 1 commit
  19. 03 Mar, 2019 4 commits
  20. 27 Feb, 2019 1 commit
  21. 11 Feb, 2019 1 commit
  22. 28 Jan, 2019 1 commit
  23. 26 Jan, 2019 1 commit
  24. 15 Jan, 2019 1 commit