summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJonas Ådahl <jadahl@gmail.com>2023-02-21 13:24:51 +0100
committerSimon Ser <contact@emersion.fr>2023-02-27 11:26:25 +0000
commit94482ceaf9be9a128065358aa56f631e3a118f75 (patch)
treefcf35aede3b66827e8a84c0df1a3022114769dc9
parentcf838fd316f74b0a79ca6cbe1a5cf2548c8265c2 (diff)
downloadwayland-protocols-94482ceaf9be9a128065358aa56f631e3a118f75.tar.gz
xdg-output: Remove and tweak contradicting examples
The "logical size" as stated by the first paragraph corresponds to the monitor size in the global compositor space. To most clients, this is unnecessary information, and should be ignored, but some used the listed examples to derive information that contradicts the very definition of what this event communicates. One example tried to add surface size assumptions, which was not correct. Remove this part completely, clients should not try to configure their surface sizes from the logical size of a monitor. The other is the list of size examples; it tried to communicate that a compositor sometimes may not scale the viewport of the monitor in its global compositor coordinate space, in which case, the logical size itself matches the actual resolution. Tweak this wording to make that clear that it does not related to any surface size. Signed-off-by: Jonas Ådahl <jadahl@gmail.com>
-rw-r--r--unstable/xdg-output/xdg-output-unstable-v1.xml14
1 files changed, 5 insertions, 9 deletions
diff --git a/unstable/xdg-output/xdg-output-unstable-v1.xml b/unstable/xdg-output/xdg-output-unstable-v1.xml
index 6bc8149..5d536aa 100644
--- a/unstable/xdg-output/xdg-output-unstable-v1.xml
+++ b/unstable/xdg-output/xdg-output-unstable-v1.xml
@@ -117,10 +117,6 @@
The logical_size event describes the size of the output in the
global compositor space.
- For example, a surface without any buffer scale, transformation
- nor rotation set, with the size matching the logical_size will
- have the same size as the corresponding output when displayed.
-
Most regular Wayland clients should not pay attention to the
logical size and would rather rely on xdg_shell interfaces.
@@ -131,14 +127,14 @@
For example, for a wl_output mode 3840×2160 and a scale factor 2:
- - A compositor not scaling the surface buffers will advertise a
- logical size of 3840×2160,
+ - A compositor not scaling the monitor viewport in its compositing space
+ will advertise a logical size of 3840×2160,
- - A compositor automatically scaling the surface buffers will
+ - A compositor scaling the monitor viewport with scale factor 2 will
advertise a logical size of 1920×1080,
- - A compositor using a fractional scale of 1.5 will advertise a
- logical size of 2560×1440.
+ - A compositor scaling the monitor viewport using a fractional scale of
+ 1.5 will advertise a logical size of 2560×1440.
For example, for a wl_output mode 1920×1080 and a 90 degree rotation,
the compositor will advertise a logical size of 1080x1920.