Hi,
> > Good point. Setting an invalid state should probably result in a > > protocol error. > > No this cannot be a protocol error because that makes it difficult to > change the size range to a new one that does not intersect the old one. > > Perhaps having the commit of an invalid state be a protocol error is ok. We'd reach an invalid state only once it's applied, ie after the commit. So the client can (and must) set a Min <= Max before the commit, otherwise it's an invalid state that will lead to a protocol error. That's what I've tried to specify in v6: Values set in this way are double-buffered. They will get applied on the next commit. [...] Requesting a minimum size to be larger than the maximum size of a surface is illegal and will result in a protocol error. Cheers, Olivier _______________________________________________ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel