From 854314132c0ab61d3486cbd6fdcd5c29d906abd3 Mon Sep 17 00:00:00 2001 From: Vladimir Zolotopupov Date: Wed, 12 Jul 2023 03:03:35 +0300 Subject: [PATCH] protocol: add scale120 event to the wl_output --- protocol/wayland.xml | 34 +++++++++++++++++++++++++++++++++- 1 file changed, 33 insertions(+), 1 deletion(-) diff --git a/protocol/wayland.xml b/protocol/wayland.xml index 2d5cbe4..fd41444 100644 --- a/protocol/wayland.xml +++ b/protocol/wayland.xml @@ -2678,7 +2678,7 @@ - + An output describes part of the compositor geometry. The compositor works in the 'compositor coordinate system' and an @@ -2917,6 +2917,38 @@ + + + + + + This event contains scaling geometry information + specific to a scale factor of 120 fractions (v120 scale). + It may be sent after binding the output object or if the + output scale changes later. If it is not sent, + the client should rely on the fixed point scale. + + A scale larger than 120 means that the compositor will + automatically scale surface buffers by (scale_120 / 120.0) + when rendering. This is used for very high resolution + displays where applications rendering at the native + resolution would be too small to be legible. + + Compositor with version 5 support must send both fixed scale + and v120 scale values. If the v120 scale has not been sent, + the client must use a fixed point scale value. + + To ensure proper handling of v120 scale, scaling-aware + clients can utilize the "viewporter" protocol. + By setting the appropriate viewport and scaling + properties using the viewporter protocol, + clients can provide a higher-detail image + that matches the v120 scale of the output. + + The scale_120 event will be followed by a done event. + + +