protocol: mention wl_surface events from wl_output.{scale,transform}

The wl_output events should not be used anymore for guessing the
preferred scale and transform of a surface. We have explicit events
for that now.

Signed-off-by: Simon Ser <contact@emersion.fr>
This commit is contained in:
Simon Ser 2023-10-25 13:25:44 +02:00
parent 9c4213ed3e
commit a74aa93394

View file

@ -2757,6 +2757,10 @@
The geometry event will be followed by a done event (starting from The geometry event will be followed by a done event (starting from
version 2). version 2).
Clients should use wl_surface.preferred_buffer_transform instead of the
transform advertised by this event to find the preferred buffer
transform to use for a surface.
Note: wl_output only advertises partial information about the output Note: wl_output only advertises partial information about the output
position and identification. Some compositors, for instance those not position and identification. Some compositors, for instance those not
implementing a desktop-style output layout or those exposing virtual implementing a desktop-style output layout or those exposing virtual
@ -2862,12 +2866,9 @@
displays where applications rendering at the native displays where applications rendering at the native
resolution would be too small to be legible. resolution would be too small to be legible.
It is intended that scaling aware clients track the Clients should use wl_surface.preferred_buffer_scale
current output of a surface, and if it is on a scaled instead of this event to find the preferred buffer
output it should use wl_surface.set_buffer_scale with scale to use for a surface.
the scale of the output. That way the compositor can
avoid scaling the surface, and the client can supply
a higher detail image.
The scale event will be followed by a done event. The scale event will be followed by a done event.
</description> </description>