From b5fb898e92add82f577367fca9091040cd29e3d9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jonas=20=C3=85dahl?= Date: Sun, 19 Jan 2014 10:32:10 +0100 Subject: [PATCH] protocol: Clarify semantics of sub-surface placement requests MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Clarify some semantics of wl_subsurface.place_below and wl_subsurface.place_below that were not specified. Signed-off-by: Jonas Ã…dahl Reviewed-by: Jasper St. Pierre --- protocol/wayland.xml | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/protocol/wayland.xml b/protocol/wayland.xml index 61fde842..b986c868 100644 --- a/protocol/wayland.xml +++ b/protocol/wayland.xml @@ -1946,8 +1946,9 @@ parent surface. Using any other surface, including this sub-surface, will cause a protocol error. - The z-order is double-buffered state, and will be applied on the - next commit of the parent surface. + The z-order is double-buffered. Requests are handled in order and + applied immediately to a pending state, then committed to the active + state on the next commit of the parent surface. See wl_surface.commit and wl_subcompositor.get_subsurface. A new sub-surface is initially added as the top-most in the stack