[PATCH wayland-protocols v2 11/13] xdg-shell: clarify map/unmap wording
jadahl at gmail.com
Wed Jul 12 01:56:32 UTC 2017
On Tue, Jul 11, 2017 at 11:30:11PM +0100, David Edmundson wrote:
> Can you clarify something here.
> >A newly-unmapped surface is considered to have met condition (1) out
> + of the 3 required conditions for mapping a surface if its role
> + has not been destroyed.
> Attaching a null buffer unmaps the surface
> Unmapping the surface resets the state
> The above implies if we haven't deleted the xdg_toplevel we don't need to
> call get_toplevel again.
> When the client wants to remap, what prompts the server to send a new
> configure event? If it doesn't, how does the client know what the state is
> before it reattaches a buffer.
The idea is that having unmapped by null-attach means the
xdg_surface/xdg_toplevel etc is reset to the exact same state that it
had when first created, thus to map again, one would do what one would
do the same as when mapping it for the first time: set up the state
(set_title, (set_maximized?), set_app_id), commit, wait for configure,
then attach a new buffer given the configure event data.
More information about the wayland-devel