1. 12 Jun, 2015 6 commits
  2. 05 Jun, 2015 1 commit
  3. 03 Jun, 2015 1 commit
  4. 02 Jun, 2015 1 commit
  5. 01 Jun, 2015 1 commit
  6. 27 May, 2015 4 commits
  7. 21 May, 2015 1 commit
    • Giulio Camuffo's avatar
      tests: add an headers test · 1fab2e7b
      Giulio Camuffo authored
      
      
      This test checks that the protocol and library headers include only what
      they are supposed to include. That is, that the core headers do not
      include the protocol headers and that the core protocol headers do not
      include the non core library headers.
      The build process now generates core protocol headers, but they are only
      used in the test and don't get installed.
      Reviewed-by: default avatarBryce Harrington <bryce@osg.samsung.com>
      1fab2e7b
  8. 16 May, 2015 1 commit
  9. 15 May, 2015 1 commit
    • Michael Vetter's avatar
      remove trailing whitespaces · b409c919
      Michael Vetter authored
      Remove trailing whitespaces because they are not needed and jumping to
      the end of al ine should do just that and not jump to the whitespace.
      b409c919
  10. 08 May, 2015 1 commit
  11. 07 May, 2015 1 commit
  12. 30 Apr, 2015 3 commits
  13. 15 Apr, 2015 1 commit
  14. 08 Apr, 2015 1 commit
  15. 07 Apr, 2015 1 commit
  16. 30 Mar, 2015 1 commit
  17. 27 Mar, 2015 1 commit
  18. 19 Mar, 2015 2 commits
  19. 18 Mar, 2015 2 commits
  20. 05 Mar, 2015 1 commit
  21. 04 Mar, 2015 1 commit
    • Jonas Ådahl's avatar
      protocol: Change wording of subsurface placement scheduling · 8b2fbf87
      Jonas Ådahl authored
      Change wording to be more consistent with other parts of the subsurface
      protocol. Before this change, wl_subsurface.set_position explicitly
      stated that the new state was to be applied on the parents
      wl_surface.commit and wl_subsurface.place_above/below only said "on
      the next commit of the parent surface". What "committed" means is
      ambiguous considering that a wl_surface.commit actually defers the
      actual commit when in synchronized mode, but the intention has always
      been that placement of a subsurface should be considered part of its
      content, i.e. placement state should be applied when other state
      (buffer, regions). This patch makes that more clear.
      
      Note that prior to this patch, one could correctly have interpreted
      the protocol meaning that placements operations takes effect explicitly
      on wl_surface.commit of the parent surface no matter whether other state
      of the parent surface is applied at that point. This patch clarifies that
      that is not the case.
      
      https://bugs.freedesktop.org/show_bug.cgi?id=88857
      
      Signed-off-by: Jonas Ådahl's avatarJonas Ådahl <jadahl@gmail.com>
      Acked-by: Jasper St. Pierre's avatarJasper St. Pierre <jstpierre@mecheye.net>
      Reviewed-by: Pekka Paalanen's avatarPekka Paalanen <pekka.paalanen@collabora.co.uk>
      8b2fbf87
  22. 25 Feb, 2015 1 commit
  23. 18 Feb, 2015 1 commit
  24. 14 Feb, 2015 1 commit
  25. 07 Feb, 2015 1 commit
  26. 06 Feb, 2015 2 commits
  27. 05 Feb, 2015 1 commit