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 <[email protected]> --- protocol/xdg-shell.xml | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/protocol/xdg-shell.xml b/protocol/xdg-shell.xml index 84d39bb..f07ba5e 100644 --- a/protocol/xdg-shell.xml +++ b/protocol/xdg-shell.xml @@ -364,6 +364,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. -- 2.1.4 _______________________________________________ wayland-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/wayland-devel
