diff options
author | Simon Ser <contact@emersion.fr> | 2020-04-07 17:18:18 +0200 |
---|---|---|
committer | Simon Ser <contact@emersion.fr> | 2020-04-07 17:50:45 +0200 |
commit | e8f7d4ebbd3d85b174e965ad601d806a49238696 (patch) | |
tree | 6ddfcf2923a6868adaf111d90131d2c06b49307c | |
parent | b0a25f26d3e8b5ad24773881a9a895dd9cc75466 (diff) |
xdg-shell: describe how to re-map an unmapped toplevel
Signed-off-by: Simon Ser <contact@emersion.fr>
-rw-r--r-- | stable/xdg-shell/xdg-shell.xml | 6 |
1 files changed, 5 insertions, 1 deletions
diff --git a/stable/xdg-shell/xdg-shell.xml b/stable/xdg-shell/xdg-shell.xml index be64354..b77eee1 100644 --- a/stable/xdg-shell/xdg-shell.xml +++ b/stable/xdg-shell/xdg-shell.xml @@ -581,7 +581,11 @@ by the compositor until it is explicitly mapped again. All active operations (e.g., move, resize) are canceled and all attributes (e.g. title, state, stacking, ...) are discarded for - an xdg_toplevel surface when it is unmapped. + an xdg_toplevel surface when it is unmapped. The xdg_toplevel returns to + the state it had right after xdg_surface.get_toplevel. The client + can re-map the toplevel by perfoming a commit without any buffer + attached, waiting for a configure event and handling it as usual (see + xdg_surface description). Attaching a null buffer to a toplevel unmaps the surface. </description> |