[PATCH wayland-protocols v2 11/13] xdg-shell: clarify map/unmap wording

Jasper St. Pierre jstpierre at mecheye.net
Mon Jul 17 06:16:25 UTC 2017

(Coming into this one late)

When I first wrote xdg-shell, I maintained that attaching a NULL buffer
should be illegal since it has no benefit compared to destroying the
surface, but compositors might not reset all data attached to the surface,
making a weird exception where clients depend on bugs where state isn't
always reset. And the "resetting of all data" might seem like strange
behavior to clients.

Has this rationale changed?

On Tue, Jul 11, 2017 at 8:11 PM, David Edmundson <davidedmundson at kde.org>

>> 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.
>> Thanks, I'd totally forgotten the commit as I was only looking in this
> interface.
> It's clear now.
> David
> _______________________________________________
> wayland-devel mailing list
> wayland-devel at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/wayland-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/wayland-devel/attachments/20170716/2ca7dce3/attachment.html>

More information about the wayland-devel mailing list