1. 30 Oct, 2020 2 commits
  2. 20 Oct, 2020 1 commit
    • Adrien Faveraux's avatar
      move keyboard to the new approach and refactor the keyboard_interface · 8a6d17f2
      Adrien Faveraux authored and Bhushan Shah's avatar Bhushan Shah committed
      - Get rid of the KF5 deprecated methods related to keymap,
        kwayland-server is not source compatible with kwayland, so we don't
        need to keep the deprecated methods
      - Move the key repeat, modifiers and keymap handling fully into the
        KeyboardInterface.
      - Get rid of some of the keyboard related code base from the
        seat_interface.
      
      Co-Author: Bhushan Shah <bshah@kde.org>
      8a6d17f2
  3. 14 Oct, 2020 2 commits
  4. 07 Oct, 2020 1 commit
    • Bhushan Shah's avatar
      text-input-v3: track commit counts per resource · 50761ce0
      Bhushan Shah authored
      If we track the commit counts at compositor global, this will fail
      horribly for anything other than the first text-input-v3 client, as for
      new client the serial count will not be what it expects in the done()
      request and it will simply consider events as outdated and will refuse
      to accept those events
      50761ce0
  5. 01 Oct, 2020 2 commits
  6. 29 Sep, 2020 2 commits
  7. 11 Sep, 2020 1 commit
    • Vlad Zahorodnii's avatar
      autotests: Fix TestInputMethodInterface · 053c2de4
      Vlad Zahorodnii authored
      If the underlying wl_surface object has been removed, the input panel
      surface will be still alive.
      
      Unfortunately, in order to make the test pass, the input panel surface
      interface must have a destructor request.
      
      So, the code that tests the destruction of an input panel surface had
      been removed.
      053c2de4
  8. 05 Sep, 2020 1 commit
  9. 03 Sep, 2020 1 commit
  10. 17 Aug, 2020 1 commit
  11. 14 Aug, 2020 2 commits
    • David Edmundson's avatar
      Add a workaround to prevent klipper racing with clipboard updates · edbde063
      David Edmundson authored
      We have a situation where some clients drop their old offer before
      creating a new one. This means klipper tries to fill in the empty
      clipboard at the same time the client posts its new real contents.
      
      This adds in a flag (via a hidden mimetype) that klipper is trying to
      replace a null clipboard. If this flag is set and our clipboard is not
      null because the client has updated it in the meantime we ignore the
      klipper update.
      
      It's a workaround, rather than an ideal fix at a data level, but it
      solves the problem in the interim.
      
      CCBUG: 424855
      edbde063
    • David Edmundson's avatar
      [autotests] Cleanup DataControlInterface test · e8a43b6b
      David Edmundson authored
      The tests were not fully self-encapsulating and leaky.
      e8a43b6b
  12. 05 Aug, 2020 1 commit
  13. 23 Jul, 2020 1 commit
  14. 15 Jul, 2020 1 commit
  15. 08 Jul, 2020 1 commit
    • Vlad Zahorodnii's avatar
      Allow creating global objects before Display is started · 1569acb4
      Vlad Zahorodnii authored and Vlad Zahorodnii's avatar Vlad Zahorodnii committed
      It can be especially useful if the compositor wants to ensure that all
      globals have been created before starting to accept client connections.
      
      Unfortunately, start() and terminate() stuff doesn't align well with it,
      so the terminate() method was dropped to ensure that Display always
      returns the same wl_display object.
      1569acb4
  16. 19 Jun, 2020 1 commit
    • Vlad Zahorodnii's avatar
      Introduce surface-to-buffer and buffer-to-surface matrices · 4d210a94
      Vlad Zahorodnii authored and Vlad Zahorodnii's avatar Vlad Zahorodnii committed
      The compositor needs to monitor changes in the mapping between the
      surface local coordinates and the buffer coordinates because texture
      coordinates correspond to the latter. One way to do it is to monitor
      things such as the surface size, the buffer size, the buffer scale,
      etc. The main problem with doing so is that there are so many factors
      that contribute to how mapping between the surface local coordinate
      space and the buffer coordinate space is performed.
      
      In order to provide a generic way for monitoring changes in the mapping
      between the surface local coordinate space and the buffer coordinate
      space, this patch introduces two new matrices. The first one specifies
      how the surface-local coordinates are mapped to buffer coordinates, and
      the other one specifies how to map the buffer coordinates to surface
      local coordinates.
      
      With the new two matrices, the compositor has a generic way to get
      notified when it has to re-compute texture coordinates.
      4d210a94
  17. 02 Jun, 2020 1 commit
    • Vlad Zahorodnii's avatar
      Add support for the wp_viewporter protocol · b9381012
      Vlad Zahorodnii authored
      The wp_viewporter compositor extension allows clients to crop and scale
      their surface. It can be useful for applications such as video players
      because it may potentially reduce their power usage.
      b9381012
  18. 29 May, 2020 2 commits
  19. 28 May, 2020 1 commit
  20. 26 May, 2020 1 commit
    • David Edmundson's avatar
      Add DataControl iface · d8b553e7
      David Edmundson authored
      Summary:
      This patch makes use of wlroot's DataControl interface to support
      clipboard management.
      
      Unlike wl_data_device clipboards are sent on every change to all
      watchers.
      If the data device has a selection set it updates immediately.
      
      Because it was started a year ago it uses the existing style of
      wrapping objects. The unit test uses the new approach.
      
      Test Plan:
      Updated kwin
      used wlroot's wl-copy, wl-paste which are xclip replacements to
      show that the clipboard updated correctly
      
      Reviewers: #kwin
      
      Differential Revision: https://phabricator.kde.org/D29330
      d8b553e7
  21. 18 May, 2020 1 commit
  22. 29 Apr, 2020 2 commits
  23. 19 Mar, 2020 1 commit
  24. 16 Mar, 2020 1 commit
  25. 25 Jan, 2019 1 commit
    • Fabian Vogt's avatar
      Add option to use wl_display_add_socket_auto · d671fcd0
      Fabian Vogt authored
      Summary:
      If automaticSocketNaming is enabled, it will use wl_display_add_socket_auto
      to allocate the next free socket. The resulting name can be retrieved using
      socketName after a successful start afterwards.
      
      Test Plan: Ran the new autotest, passes. kwin_wayland still uses the old behaviour.
      
      Reviewers: #kwin, #plasma, romangg
      
      Reviewed By: #kwin, #plasma, romangg
      
      Subscribers: davidedmundson, zzag, romangg, kde-frameworks-devel
      
      Tags: #frameworks
      
      Differential Revision: https://phabricator.kde.org/D17122
      d671fcd0
  26. 06 Nov, 2018 1 commit
  27. 04 Jul, 2018 1 commit
    • Bhushan Shah's avatar
      Fix some of cppcheck warnings · 84bc3cbd
      Bhushan Shah authored
      Summary:
      - selfInitialization
      - memleak
      
      I could probably suppress the selfInitialization warning, but probably
      is cleaner this way. Opinions welcome. This also fixes the memleak in
      autotest.
      
      Test Plan:
      - arc lint --everything
      - Fix issues
      - build
      - run tests
      
      Reviewers: #frameworks, aacid
      
      Reviewed By: aacid
      
      Subscribers: apol, aacid, kde-frameworks-devel
      
      Tags: #frameworks
      
      Differential Revision: https://phabricator.kde.org/D13559
      84bc3cbd
  28. 29 Jul, 2017 2 commits
  29. 01 Jul, 2017 1 commit
  30. 02 Jun, 2017 2 commits
  31. 11 Oct, 2016 1 commit
    • Martin Flöser's avatar
      [server] Use deleteLater when a ClientConnection gets destroyed · c0aa3a4a
      Martin Flöser authored
      Summary:
      In the situation that a wl_client gets destroyed while still
      wl_resources are around it can happen that one of them calls into the
      ClientConnection during the cleanup handling which gets triggered at the
      same time. This can then trigger a crash.
      
      This change uses deleteLater for the ClientConnection and sets the hold
      wl_client pointer to null instead of deleting directly. So the
      ClientConnection is still around while the Resources gets cleaned up.
      This is similar to the cleanup of Resource where on unbind the
      wl_resource pointer is set to null and the Resource gets delete later.
      
      BUG: 370232
      FIXED-IN: 5.28
      
      Reviewers: #plasma, bshah
      
      Subscribers: plasma-devel
      
      Tags: #plasma_on_wayland
      
      Differential Revision: https://phabricator.kde.org/D3004
      c0aa3a4a