1. 14 Sep, 2019 1 commit
  2. 01 Mar, 2018 1 commit
    • Oleg Chernovskiy's avatar
      Implement releasing of client-freed output · 08e7b23c
      Oleg Chernovskiy authored
      Summary:
      Previously KWin supported only version 2 of wl_output interface
      In third version there was an important addition that allowed clients to
      unbind outputs they may previously have bound.
      
      Bumping versions in both client and server part of KWayland to support
      this behaviour.
      
      Reviewers: davidedmundson, graesslin
      
      Reviewed By: graesslin
      
      Subscribers: jgrulich, #frameworks
      
      Tags: #frameworks
      
      Maniphest Tasks: T7785
      
      Differential Revision: https://phabricator.kde.org/D10929
      08e7b23c
  3. 13 Sep, 2016 1 commit
    • Martin Flöser's avatar
      Add support for Surface enter/leave events · 4f9dae46
      Martin Flöser authored
      Summary:
      This change implements support for the wl_surface events enter and
      leave. Those events are emitted whenever a surface becomes visible on
      an output by e.g. mapping the surface, moving or resizing it. Similar
      the leave is sent whenever the surface is no longer on an output.
      
      The server side is not yet fully complete yet. It also needs to emit
      when the client binds the output another time and needs to send a
      leave before destroying the output.
      
      Reviewers: #plasma_on_wayland
      
      Subscribers: plasma-devel
      
      Tags: #plasma_on_wayland
      
      Differential Revision: https://phabricator.kde.org/D2528
      4f9dae46
  4. 17 Nov, 2015 1 commit
    • Martin Flöser's avatar
      [server] Fix possible crash after deleting an output(device)interface · 24c9f457
      Martin Flöser authored
      After deleting an OutputInterface the resources are not necessarily
      destroyed, so unbind might still be called. The existing code just
      casted the resource's user data which could then point to invalidated
      memory.
      
      This change verifies that we still have a Private* for the resource.
      If not, it doesn't have to do any cleanup anyway.
      
      REVIEW: 126097
      24c9f457
  5. 10 Sep, 2015 1 commit
  6. 09 Sep, 2015 2 commits
  7. 18 Feb, 2015 1 commit
  8. 19 Nov, 2014 1 commit
  9. 13 Nov, 2014 2 commits
    • Martin Flöser's avatar
      Global::Private can create the wl_global · 7589dff8
      Martin Flöser authored
      Version and interface get passed to the ctor allowing Global::Private
      to implement ::create instead of providing a pure virtual method.
      Also the static bind method is added to the Global::Private which
      delegates into a pure virtual method.
      7589dff8
    • Martin Flöser's avatar
      Add a base class for all server interfaces of a wl_global · 9b94148a
      Martin Flöser authored
      New base class KWayland::Server::Global which all Interface classes
      for a wl_global inherit. Furthermore there is a shared base class
      for all the Private classes of that type.
      9b94148a
  10. 18 Sep, 2014 1 commit
  11. 17 Sep, 2014 3 commits
  12. 02 Sep, 2014 1 commit
    • Martin Flöser's avatar
      [kwin_wayland] Initial addition of the WaylandServer module · c3286985
      Martin Flöser authored
      So far this new module contains:
      * Display
      * OutputInterface
      
      Display manages the server socket and server event loop. In general it's
      the entry point to any part of the server.
      
      OutputInterface is the abstraction for the wl_output interface on server
      side. An OutputInterface is created through the Display.
      
      The auto tests for ConnectionThread and Output are adjusted to use the
      internal server instead of starting Weston. Especially the Output test
      could be extended to test much more as we have absolute control over
      the server now.
      c3286985