diff options
| author | Simon Ser <contact@emersion.fr> | 2023-10-25 13:25:44 +0200 |
|---|---|---|
| committer | Simon Ser <contact@emersion.fr> | 2024-02-21 09:14:23 +0000 |
| commit | a74aa93394a6d572eb48b1898658dad3e0c5f720 (patch) | |
| tree | 13a5fd3eb5fccefd428cccd775b3540d495113aa | |
| parent | server: add wl_client_get_user_data/wl_client_set_user_data (diff) | |
| download | wayland-a74aa93394a6d572eb48b1898658dad3e0c5f720.tar wayland-a74aa93394a6d572eb48b1898658dad3e0c5f720.tar.gz wayland-a74aa93394a6d572eb48b1898658dad3e0c5f720.tar.bz2 wayland-a74aa93394a6d572eb48b1898658dad3e0c5f720.tar.lz wayland-a74aa93394a6d572eb48b1898658dad3e0c5f720.tar.xz wayland-a74aa93394a6d572eb48b1898658dad3e0c5f720.tar.zst wayland-a74aa93394a6d572eb48b1898658dad3e0c5f720.zip | |
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>
| -rw-r--r-- | protocol/wayland.xml | 13 |
1 files changed, 7 insertions, 6 deletions
diff --git a/protocol/wayland.xml b/protocol/wayland.xml index 93f9d55..31daa74 100644 --- a/protocol/wayland.xml +++ b/protocol/wayland.xml @@ -2757,6 +2757,10 @@ The geometry event will be followed by a done event (starting from 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 position and identification. Some compositors, for instance those not implementing a desktop-style output layout or those exposing virtual @@ -2862,12 +2866,9 @@ displays where applications rendering at the native resolution would be too small to be legible. - It is intended that scaling aware clients track the - current output of a surface, and if it is on a scaled - output it should use wl_surface.set_buffer_scale with - the scale of the output. That way the compositor can - avoid scaling the surface, and the client can supply - a higher detail image. + Clients should use wl_surface.preferred_buffer_scale + instead of this event to find the preferred buffer + scale to use for a surface. The scale event will be followed by a done event. </description> |