From b317beb5e69b1cbea5b0bf550df46b6eb7b64afa Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jonas=20=C3=85dahl?= Date: Wed, 18 Mar 2015 20:29:10 +0800 Subject: [PATCH] xdg-shell: Further clarify xdg_surface.move semantics MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Jonas Ådahl Acked-by: Pekka Paalanen --- protocol/xdg-shell.xml | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git a/protocol/xdg-shell.xml b/protocol/xdg-shell.xml index 6479301c..4eeac92d 100644 --- a/protocol/xdg-shell.xml +++ b/protocol/xdg-shell.xml @@ -246,10 +246,19 @@ Start an interactive, user-driven move of the surface. This request must be used in response to some sort of user action - like a button press, key press, or touch down event. + like a button press, key press, or touch down event. The passed + serial is used to determine the type of interactive move (touch, + pointer, etc). The server may ignore move requests depending on the state of - the surface (e.g. fullscreen or maximized). + the surface (e.g. fullscreen or maximized), or if the passed serial + is no longer valid. + + If triggered, the surface will lose the focus of the device + (wl_pointer, wl_touch, etc) used for the move. It is up to the + compositor to visually indicate that the move is taking place, such as + updating a pointer cursor, during the move. There is no guarantee + that the device focus will return when the move is completed.