summaryrefslogtreecommitdiff
path: root/protocol
diff options
context:
space:
mode:
authorJonas Ådahl <jadahl@gmail.com>2015-04-07 12:07:56 +0800
committerJonas Ådahl <jadahl@gmail.com>2015-05-05 14:18:13 +0800
commitdde4955d4cb9bdac1c0ecee52e745d0aa736b355 (patch)
tree2a3ca2afa705b1a53270a8d87d473f6a2ce2d841 /protocol
parent7d1ad1122b7a09cdc2a79f26655c2159e28539bc (diff)
downloadweston-dde4955d4cb9bdac1c0ecee52e745d0aa736b355.tar.gz
xdg-shell: Specify the meaning of 0x0 window geometry in configure
Some times the compositor needs to send a configure request but without having any clue about what size the surface should have. Examples include unmaximizing a surface that was mapped as maximized, or an initial state which doesn't have any size expectations. Signed-off-by: Jonas Ådahl <jadahl@gmail.com> Reviewed-by: Bryce Harrington <bryce@osg.samsung.com> Reviewed-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk>
Diffstat (limited to 'protocol')
-rw-r--r--protocol/xdg-shell.xml5
1 files changed, 5 insertions, 0 deletions
diff --git a/protocol/xdg-shell.xml b/protocol/xdg-shell.xml
index 50ffd9c9..85aa7486 100644
--- a/protocol/xdg-shell.xml
+++ b/protocol/xdg-shell.xml
@@ -317,6 +317,11 @@
about how its surface should be resized in window geometry
coordinates. See set_window_geometry.
+ If the width or height arguments are zero, it means the client
+ should decide its own window dimension. This may happen when the
+ compositor need to configure the state of the surface but doesn't
+ have any information about any previous or expected dimension.
+
The states listed in the event specify how the width/height
arguments should be interpreted, and possibly how it should be
drawn.