From 8072ab0a505d8aeb7b34d3ecd297ca501979d905 Mon Sep 17 00:00:00 2001 From: Ben Widawsky Date: Tue, 2 Jan 2024 15:56:25 -0800 Subject: protocol: clarify scale expecations Since the positivity of zero is debatable, and, in some cases scale was simply underspecified, clarify the situation. Signed-off-by: Ben Widawsky --- protocol/wayland.xml | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) (limited to 'protocol') diff --git a/protocol/wayland.xml b/protocol/wayland.xml index 5731d69..1d471c5 100644 --- a/protocol/wayland.xml +++ b/protocol/wayland.xml @@ -1749,11 +1749,11 @@ a buffer that is larger (by a factor of scale in each dimension) than the desired surface size. - If scale is not positive the invalid_scale protocol error is + If scale is not greater than 0 the invalid_scale protocol error is raised. + summary="scale for interpreting buffer contents"/> @@ -1833,6 +1833,8 @@ content and use wl_surface.set_buffer_scale to indicate the scale they have rendered with. This allows clients to supply a higher detail buffer. + + The compositor shall emit a scale value greater than 0. @@ -2838,8 +2840,9 @@ This event contains scaling geometry information that is not in the geometry event. It may be sent after binding the output object or if the output scale changes - later. If it is not sent, the client should assume a - scale of 1. + later. The compositor will emit a non-zero, positive + value for scale. If it is not sent, the client should + assume a scale of 1. A scale larger than 1 means that the compositor will automatically scale surface buffers by this amount -- cgit v1.2.3-70-g09d2