1. 29 Feb, 2012 12 commits
  2. 28 Feb, 2012 3 commits
    • Kristian Høgsberg's avatar
      Update TODO · bf53f203
      Kristian Høgsberg authored
      bf53f203
    • Samuel Rødal's avatar
      Allow update function to not be set in wl_display_get_fd · d224714a
      Samuel Rødal authored
      Ignore previous patch, here's the correct version.
      
      From 4e1bedaaf05b576f5191f8fe3a34904ab9707414 Mon Sep 17 00:00:00 2001
      From: =?UTF-8?q?Samuel=20R=C3=B8dal?= <samuel.rodal@nokia.com>
      Date: Mon, 27 Feb 2012 15:17:20 +0100
      Subject: [PATCH] Allow update function to not be set in wl_display_get_fd
      
      The same check is done in connection_update, and now with
      wl_display_flush() there's less need for the client to need to know the
      connection mask.
      d224714a
    • 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
  3. 26 Feb, 2012 1 commit
  4. 23 Feb, 2012 9 commits
  5. 18 Feb, 2012 3 commits
  6. 16 Feb, 2012 4 commits
    • Pekka Paalanen's avatar
      protocol: remove absolute coordinates from pointer · 5536031b
      Pekka Paalanen authored
      
      
      Remove the absolute coordinate fields from the pointer motion and
      pointer_focus events. Clients are not supposed to see any global
      coordinates.
      
      Fix wayland-server code accordingly. wayland-client code is unaffected.
      Signed-off-by: Pekka Paalanen's avatarPekka Paalanen <ppaalanen@gmail.com>
      5536031b
    • Ander Conselvan de Oliveira's avatar
      data_device: get rid of attach request · 7243062f
      Ander Conselvan de Oliveira authored
      
      
      In the effort to make everything a regular surface, remove
      data_device.attach request. To maintan the functionality, add
      an icon surface parameter to data_device.start_drag.
      Signed-off-by: Kristian H. Kristensen's avatarKristian Høgsberg <krh@bitplanet.net>
      Signed-off-by: Ander Conselvan de Oliveira's avatarAnder Conselvan de Oliveira <ander.conselvan.de.oliveira@intel.com>
      7243062f
    • Juan Zhao's avatar
      Add fullscreen protocol · b3981136
      Juan Zhao authored
      Map the surface as a fullscreen surface. On the output the
      surface is assigned to. The client can use different fulllscreen
      method to fix the size mismatch issue: default, scale, driver
      and fill.
      
      Hints to indicate compositor how to deal with this fullscreen surface.
      
      "default" means the client has no preference on fullscreen
                behavior, policies are determined by compositor.
      "scale"   means the client prefers scaling by the compositor.
                Scaling would always preserve surface's aspect ratio.
                And the surface is centered.
      "driver"  means the client wants to switch video mode to the
                smallest mode that can fit the client buffer. If the
                sizes do not match, black borders are added. And the
                framerate parameter is used for "driver" method,
                to indicate the preferred framerate. framerate=0 means
                that the app does not care about framerate
      "fill"    means the client wants to add blackborders to the
                surface. This would be preferring 1:1 pixel mapping
                in the monitor native video mode. The surface is
                centered.
      b3981136
    • Juan Zhao's avatar
      Add maximized protocol · 2eddfce1
      Juan Zhao authored
      A request from the client to ask the compositor to maximize the surface.
      The compositor will reply with a configure event telling
      the expected new surface size.  The operation is completed on the
      next buffer attach to this surface.
      
      A maximized client will fill the fullscreen of the output it is bound
      to, except the panel area. This is the main difference between
      a maximized shell surface and a fullscreen shell surface.
      2eddfce1
  7. 09 Feb, 2012 7 commits
  8. 19 Jan, 2012 1 commit