1. 28 Feb, 2012 1 commit
    • Samuel Rødal's avatar
      Rename client side wl_display_destroy() to wl_display_disconnect() · bf5a8fbb
      Samuel Rødal authored
      This avoids the clash with the wayland-server version with the same
      name, and allows linking against both wayland-client and wayland-server
      at the same time, which can be useful for unit testing purposes as
      well as for nested compositing.
      
      Without this there will be crashes as the wrong wl_display_destroy()
      is called.
      bf5a8fbb
  2. 22 Nov, 2011 1 commit
    • Kristian Høgsberg's avatar
      Add support for server allocated object IDs · bdbd6ef8
      Kristian Høgsberg authored
      We set aside a range of the object ID space for use by the server.  This
      allows the server to bind an object to an ID for a client and pass that
      object to the client.  The client can use the object immediately and the
      server can emit events to the object immdiately.
      bdbd6ef8
  3. 04 Sep, 2011 1 commit
  4. 27 Aug, 2011 4 commits
  5. 12 Aug, 2011 1 commit
  6. 07 Jun, 2011 1 commit
  7. 10 May, 2011 1 commit
    • Robert Bragg's avatar
      display: Adds wl_display_flush to send buffered commands · dcfaf4ec
      Robert Bragg authored
      Previously for wayland clients to flush buffered connection data to the
      compositor they needed to first register an event-mask-update-callback
      via wl_display_get_fd() to determine if there is anything writeable
      pending.  (NB: It's considered an error to iterate connection data with
      an invalid mask)
      
      Since it's only possible to register a single update callback currently
      it's a bit awkward if you want to allow multiple orthogonal components
      to flush the connection data, such as Cogl and Clutter which both want
      to interact with wayland and may want to flush commands at different
      times.
      
      This adds a mechanism, wl_display_flush(), which makes it possible to
      flush writeable connection data without first checking the event mask.
      dcfaf4ec
  8. 18 Apr, 2011 1 commit
  9. 13 Apr, 2011 1 commit
  10. 16 Mar, 2011 1 commit
  11. 01 Dec, 2010 1 commit
  12. 29 Nov, 2010 1 commit
  13. 14 Sep, 2010 1 commit
  14. 03 Sep, 2010 1 commit
  15. 18 Aug, 2010 1 commit
  16. 10 Aug, 2010 2 commits
  17. 09 Aug, 2010 1 commit
  18. 05 Aug, 2010 1 commit
  19. 03 Aug, 2010 1 commit
  20. 29 Jul, 2010 1 commit
  21. 20 Jul, 2010 1 commit
  22. 25 Jun, 2010 1 commit
  23. 10 Jun, 2010 1 commit
  24. 09 Jun, 2010 1 commit
  25. 08 Jun, 2010 1 commit
  26. 18 Sep, 2009 1 commit
  27. 24 Feb, 2009 1 commit
  28. 23 Feb, 2009 1 commit
  29. 30 Dec, 2008 1 commit
  30. 22 Dec, 2008 2 commits
  31. 18 Dec, 2008 1 commit
  32. 16 Dec, 2008 1 commit
    • Kristian Høgsberg's avatar
      Redesign the compositor / server interface. · d2412e2c
      Kristian Høgsberg authored
      This lets the compositor directly provide the implementation of the RMI
      objects for the surface object and a new compositor object.  We avoid the
      manual forwarding of requests into the compositor and the clumsy compositor
      interface struct.
      d2412e2c
  33. 07 Dec, 2008 1 commit
  34. 02 Dec, 2008 1 commit
  35. 26 Nov, 2008 1 commit