diff options
| author | Simon Ser <contact@emersion.fr> | 2020-02-26 18:30:57 +0100 |
|---|---|---|
| committer | Pekka Paalanen <pq@iki.fi> | 2020-03-05 14:48:36 +0000 |
| commit | 8d5fadad47aad420b0d83fffc8ad573766a9c75e (patch) | |
| tree | 0f700cd2270f54c62a36a7f983cd12c68fb2d57e /protocol | |
| parent | util: fix compiler warning (diff) | |
| download | wayland-8d5fadad47aad420b0d83fffc8ad573766a9c75e.tar wayland-8d5fadad47aad420b0d83fffc8ad573766a9c75e.tar.gz wayland-8d5fadad47aad420b0d83fffc8ad573766a9c75e.tar.bz2 wayland-8d5fadad47aad420b0d83fffc8ad573766a9c75e.tar.lz wayland-8d5fadad47aad420b0d83fffc8ad573766a9c75e.tar.xz wayland-8d5fadad47aad420b0d83fffc8ad573766a9c75e.tar.zst wayland-8d5fadad47aad420b0d83fffc8ad573766a9c75e.zip | |
protocol: add invalid_size error to wl_surface
This allows the compositor to send an error when the client submits a buffer
whose size is not divisible by the buffer scale. Previously, the protocol said
it was a client error but didn't specify any error code.
Signed-off-by: Simon Ser <contact@emersion.fr>
Closes: https://gitlab.freedesktop.org/wayland/wayland/issues/145
Diffstat (limited to 'protocol')
| -rw-r--r-- | protocol/wayland.xml | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/protocol/wayland.xml b/protocol/wayland.xml index f1d95c7..d3e54ee 100644 --- a/protocol/wayland.xml +++ b/protocol/wayland.xml @@ -1378,6 +1378,7 @@ </description> <entry name="invalid_scale" value="0" summary="buffer scale value is invalid"/> <entry name="invalid_transform" value="1" summary="buffer transform value is invalid"/> + <entry name="invalid_size" value="2" summary="buffer size is invalid"/> </enum> <request name="destroy" type="destructor"> @@ -1392,8 +1393,9 @@ The new size of the surface is calculated based on the buffer size transformed by the inverse buffer_transform and the - inverse buffer_scale. This means that the supplied buffer - must be an integer multiple of the buffer_scale. + inverse buffer_scale. This means that at commit time the supplied + buffer size must be an integer multiple of the buffer_scale. If + that's not the case, an invalid_size error is sent. The x and y arguments specify the location of the new pending buffer's upper left corner, relative to the current buffer's upper |
