Skip to content
Snippets Groups Projects
  1. Jun 02, 2015
  2. Jun 01, 2015
  3. May 27, 2015
  4. May 21, 2015
    • 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
  5. May 16, 2015
  6. May 15, 2015
    • 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
  7. May 08, 2015
  8. May 07, 2015
  9. Apr 30, 2015
  10. Apr 15, 2015
  11. Apr 08, 2015
  12. Apr 07, 2015
  13. Mar 30, 2015
  14. Mar 27, 2015
  15. Mar 19, 2015
  16. Mar 18, 2015
  17. Mar 05, 2015
  18. Mar 04, 2015
    • 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: default avatarJonas Ådahl <jadahl@gmail.com>
      Acked-by: default avatarJasper St. Pierre <jstpierre@mecheye.net>
      Reviewed-by: default avatarPekka Paalanen <pekka.paalanen@collabora.co.uk>
      8b2fbf87
  19. Feb 25, 2015
  20. Feb 18, 2015
  21. Feb 14, 2015
  22. Feb 07, 2015
  23. Feb 06, 2015
  24. Feb 05, 2015
  25. Jan 31, 2015
  26. Jan 30, 2015
  27. Jan 29, 2015
Loading