1. 22 May, 2019 2 commits
  2. 21 May, 2019 2 commits
  3. 20 May, 2019 2 commits
  4. 10 May, 2019 1 commit
  5. 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
  6. 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
  7. 30 Apr, 2019 2 commits
  8. 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
  9. 12 Mar, 2019 4 commits
  10. 10 Mar, 2019 1 commit
  11. 04 Mar, 2019 1 commit
  12. 03 Mar, 2019 4 commits
  13. 27 Feb, 2019 1 commit
  14. 11 Feb, 2019 1 commit
  15. 28 Jan, 2019 1 commit
  16. 26 Jan, 2019 1 commit
  17. 15 Jan, 2019 1 commit
  18. 08 Jan, 2019 1 commit
  19. 29 Dec, 2018 1 commit
  20. 18 Nov, 2018 1 commit
  21. 13 Nov, 2018 2 commits
  22. 05 Oct, 2018 1 commit
  23. 04 Oct, 2018 1 commit
  24. 02 Oct, 2018 2 commits
  25. 07 Sep, 2018 1 commit