From: Jonas Ådahl Date: Tue, 5 May 2015 07:35:17 +0000 (+0800) Subject: xdg-shell: Document the set_maximized and unsetmaximized requests X-Git-Tag: 1.7.93~10 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=7ef8c9144dd38bb59726e82af988242b2407aa0f;p=platform%2Fupstream%2Fweston.git xdg-shell: Document the set_maximized and unsetmaximized requests This patch changes the semantics (compared to the previous version of this patch) of maximizing/unmaximizing an already maximized/unmaximized surface to always result in a configure event. Doing it this way would be more consistent with how the compositor works regarding other configure events i.e. send many, letting the client ignore when needed (for example during resize). Signed-off-by: Jonas Ådahl Reviewed-by: Bryce Harrington Acked-by: Pekka Paalanen --- diff --git a/protocol/xdg-shell.xml b/protocol/xdg-shell.xml index 72570363..44a3a12c 100644 --- a/protocol/xdg-shell.xml +++ b/protocol/xdg-shell.xml @@ -417,8 +417,48 @@ - - + + + Maximize the surface. + + After requesting that the surface should be maximized, the compositor + will respond by emitting a configure event with the "maximized" state + and the required window geometry. The client should then update its + content, drawing it in a maximized state, i.e. without shadow or other + decoration outside of the window geometry. The client must also + acknowledge the configure when committing the new content (see + ack_configure). + + It is up to the compositor to decide how and where to maximize the + surface, for example which output and what region of the screen should + be used. + + If the surface was already maximized, the compositor will still emit + a configure event with the "maximized" state. + + + + + + Unmaximize the surface. + + After requesting that the surface should be unmaximized, the compositor + will respond by emitting a configure event without the "maximized" + state. If available, the compositor will include the window geometry + dimensions the window had prior to being maximized in the configure + request. The client must then update its content, drawing it in a + regular state, i.e. potentially with shadow, etc. The client must also + acknowledge the configure when committing the new content (see + ack_configure). + + It is up to the compositor to position the surface after it was + unmaximized; usually the position the surface had before maximizing, if + applicable. + + If the surface was already not maximized, the compositor will still + emit a configure event without the "maximized" state. + +