> What is the default value of these hints? I would propose -1 as default, meaning unset. Compositor has to deal with not knowing the minimum size, preferably this would mean though that the client can be set to any valid size.
> When is the client expected to send this? Can this be sent before > the window gets mapped? After the window was unmapped? I would say this hint could be sent any time after surface object is created. > How does this interact with the protocol sequence to decide the initial > size of a window before it gets mapped? If the maximum was less than initial size, this would need thinking. For now it seems though that maximum might go away? Needs further discussion. > Making surface state double-buffered is desired for all state that > immediately affects the surface's presentation. However, these are > hints and do not change how the surface is presented; they change what > sizes the compositor may ask for in configure events. It that sense, it > is not necessary to make this state double-buffered, and I think not > double-buffering (not demanding a commit) will make it easier to use > and also to define how it works with the initial size negotiation. I agree with this, I don't see any reason for this to be double-buffered either to be honest. _______________________________________________ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel