1. 04 May, 2021 1 commit
  2. 06 Apr, 2021 1 commit
  3. 30 Mar, 2021 1 commit
  4. 26 Mar, 2021 1 commit
  5. 23 Mar, 2021 1 commit
  6. 16 Mar, 2021 1 commit
  7. 15 Mar, 2021 1 commit
  8. 02 Mar, 2021 1 commit
  9. 23 Feb, 2021 1 commit
  10. 11 Feb, 2021 2 commits
  11. 04 Feb, 2021 1 commit
  12. 02 Feb, 2021 1 commit
  13. 26 Jan, 2021 1 commit
  14. 21 Jan, 2021 2 commits
  15. 12 Jan, 2021 1 commit
    • David Edmundson's avatar
      Send SurfaceInterface::enter events after clients bind to outputs · e1e3a4a0
      David Edmundson authored
      The following order of events are legal:
      Typically order is:
       - server announces a new output
       - client binds to a new output
       - server updates the surface to be on new output
      But we can have events occur in the following order:
       - server announces a new output
       - server updates the surface to be on new output
       - client binds to a new output
      At which point when we update the surface there is no ID to tell the
      client which output the surface is on.
      This patch watches for clients binding to output and updates
  16. 06 Jan, 2021 4 commits
  17. 05 Jan, 2021 1 commit
  18. 16 Dec, 2020 1 commit
  19. 14 Dec, 2020 2 commits
    • Andrey Butirsky's avatar
      keyboard_interface: Always update modifiers cache · f67daa07
      Andrey Butirsky authored and David Edmundson's avatar David Edmundson committed
      We send modifiers to the active client when they change, and when we
      focus an existing client we send the cached state.
      For this reason it's important we always update our internal store of
      modifiers regardless of whether a surface is currently active.
      Unit test is adopted accordingly.
      BUG: 429930
    • Vlad Zahorodnii's avatar
      Remove factory methods in Display · 725e97aa
      Vlad Zahorodnii authored
      The main reason why we have factory methods is that up to some point,
      kwayland had its own signal to indicate when globals have to be removed.
      Now that all globals add destroy listeners for the wl_display object,
      we don't have that signal. Most factory methods are equivalent to doing
      new T(display).
      Besides adding unnecessary boilerplate code, another reason to get rid
      of the factory methods is to reduce the amount of merge conflicts. If
      several persons work on implementing wayland protocols at the same time,
      sooner or later someone will have to resolve merge conflicts in Display.
  20. 12 Dec, 2020 1 commit
  21. 09 Dec, 2020 3 commits
  22. 07 Dec, 2020 1 commit
  23. 01 Dec, 2020 1 commit
  24. 27 Nov, 2020 1 commit
  25. 19 Nov, 2020 1 commit
  26. 17 Nov, 2020 2 commits
    • Aleix Pol Gonzalez's avatar
      Notify subsurfaces about output changes · c58ea3e8
      Aleix Pol Gonzalez authored and Aleix Pol Gonzalez's avatar Aleix Pol Gonzalez committed
      Otherwise they wouldn't notice and wouldn't update to the settings of
      the new output, like the new output's scaling.
    • David Edmundson's avatar
      Allow small timeout intervals in IdleInterface · 9cf51bb1
      David Edmundson authored
      A threshold exists to stop users flooding the server for no reason.
      However, there is a usecase for small timeouts.
      rsibreak has a "please relax for 20 seconds" interface. Here it makes
      perfect sense to know if a user is active in small increments. The plan
      is to start a 1s timer and wait for that. Then we wait locally for 20s
      without a resume event.
  27. 16 Nov, 2020 1 commit
  28. 11 Nov, 2020 2 commits
    • Vlad Zahorodnii's avatar
      Safely end drag if the source data device gets destroyed · d70552f6
      Vlad Zahorodnii authored
      We cannot end a drag after the destroyed() signal for the source data
      device is emitted because DataDeviceInterface and its d pointer are gone
      by that time.
    • Vlad Zahorodnii's avatar
      Destroy all clients before destroying wl_display · e77f9ac2
      Vlad Zahorodnii authored
      One of the most disappointing things when writing autotests is dealing
      with a race condition where destructor requests are processed after all
      globals have been destroyed.
      With this change, the Display object will destroy all clients and their
      resources before destroying the wl_display object. The good thing about
      doing so is that shut down logic becomes simple. We don't have to assume
      that wl_resource objects can outlive their wl_global objects, etc. The
      bad thing is that it exposed a couple of pre-existing latent bugs in the
      data device and the xdg foreign code.
      closes #2
  29. 10 Nov, 2020 1 commit
  30. 09 Nov, 2020 1 commit