From 82d8b21827c4f58013a4061fb3c813d9ae80407e Mon Sep 17 00:00:00 2001 From: Kirill Primak Date: Mon, 23 Oct 2023 11:14:02 +0300 Subject: protocol: improve wl_subsurface.{set_position,place_above} description Don't mention when the parent surface state is applied; the parent surface isn't necessarily a sub-surface. Signed-off-by: Kirill Primak --- protocol/wayland.xml | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/protocol/wayland.xml b/protocol/wayland.xml index b4141fc..37a7603 100644 --- a/protocol/wayland.xml +++ b/protocol/wayland.xml @@ -3103,9 +3103,7 @@ surface area. Negative values are allowed. The scheduled coordinates will take effect whenever the state of the - parent surface is applied. When this happens depends on whether the - parent surface is in synchronized mode or not. See - wl_subsurface.set_sync and wl_subsurface.set_desync for details. + parent surface is applied. If more than one set_position request is invoked by the client before the commit of the parent surface, the position of a new request always @@ -3128,9 +3126,7 @@ The z-order is double-buffered. Requests are handled in order and applied immediately to a pending state. The final pending state is copied to the active state the next time the state of the parent - surface is applied. When this happens depends on whether the parent - surface is in synchronized mode or not. See wl_subsurface.set_sync and - wl_subsurface.set_desync for details. + surface is applied. A new sub-surface is initially added as the top-most in the stack of its siblings and parent. -- cgit v1.2.3-70-g09d2