I feel configure events and requests are messed up
scampa.giovanni at gmail.com
Wed Sep 7 13:27:03 PDT 2011
Il giorno mer, 07/09/2011 alle 10.33 -0700, Bill Spitzak ha scritto:
> In Wayland the client allocates the buffer, not the compositor.
> I think this is what is leading to the confusion here. The compositor
> has no say over how big the buffer is. Instead the client controls it
> and tells the compositor what the resulting size is.
> To cause futher confusion there is an assumption that the compositor
> will then map this entire buffer onto the screen as a window, thus
> leading to worry that the client can force the screen to be obscured,
> and that it can ignore compositor resizing limits, etc. This is not
> true, the compositor can do anything it wants with the buffer, it is in
> effect a texture map that it can place part/all of onto the surfaces it
> composites onto the screen.
As Kristian said earlier, we need coordination between the compositor
and the client, which means that when they disagree, we have to decide
who is right. I say that the compositor is always right, and the
client-side winsys implementation (that is, libwayland-client + libEGL)
should enforce this; you say the client is always right and is allowed
to create and map whatever buffer.
In your model, if the compositor does not map exactly what the client
has asked, there is a bug in the compositor; in my model, if the client
provides a buffer of the wrong size, there is a bug in the client.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 316 bytes
Desc: This is a digitally signed message part
More information about the wayland-devel