When tiled, clients must obey the window geometry specified in the configure event and can choose to hide some of their decorations.
Signed-off-by: Olivier Fourdan <[email protected]> --- v2: Simplify the proposal and keep only one "tiled" state instead of one per edge. Note that the edges in my initial proposal were surface edges, not monitor edges. Anythow, if some other (tiling) Wayland compositor needs more granularity, we could use the "draw states" from Mike's proposal. I do however reckon that "tiled" is not the same as "maximized", even though a client has to obey the geometry in both cases, a client would need to distinguish between the two states to adapt its decorations accordingly. A single "tiled" state would get my vote (at least ^_~) as it's simple enough. unstable/xdg-shell/xdg-shell-unstable-v6.xml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/unstable/xdg-shell/xdg-shell-unstable-v6.xml b/unstable/xdg-shell/xdg-shell-unstable-v6.xml index ce57153..99465cd 100644 --- a/unstable/xdg-shell/xdg-shell-unstable-v6.xml +++ b/unstable/xdg-shell/xdg-shell-unstable-v6.xml @@ -343,6 +343,12 @@ active. Do not assume this means that the window actually has keyboard or pointer focus. </description> + <entry name="tiled" value="5" summary="the surface is tiled"> + <description summary="the surface is tiled"> + The surface is tiled, either to another surface or a monitor + edge. The window geometry specified in the configure event must + be obeyed by the client. + </description> </entry> </enum> -- 2.7.4 _______________________________________________ wayland-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/wayland-devel
