aboutsummaryrefslogtreecommitdiffstats
path: root/protocol
diff options
context:
space:
mode:
authorSimon Ser <contact@emersion.fr>2018-09-29 22:25:47 +0200
committerDaniel Stone <daniel@fooishbar.org>2019-04-27 21:44:04 +0000
commit3ab56ef8fa5aa64c07ad10fbaeb09b0c3b708ccf (patch)
treed410f4b530e39d7b69813e64380762c5babc77fa /protocol
parentwayland.xml: document invalid_finish error in wl_data_offer.finish (diff)
downloadwayland-3ab56ef8fa5aa64c07ad10fbaeb09b0c3b708ccf.tar
wayland-3ab56ef8fa5aa64c07ad10fbaeb09b0c3b708ccf.tar.gz
wayland-3ab56ef8fa5aa64c07ad10fbaeb09b0c3b708ccf.tar.bz2
wayland-3ab56ef8fa5aa64c07ad10fbaeb09b0c3b708ccf.tar.lz
wayland-3ab56ef8fa5aa64c07ad10fbaeb09b0c3b708ccf.tar.xz
wayland-3ab56ef8fa5aa64c07ad10fbaeb09b0c3b708ccf.tar.zst
wayland-3ab56ef8fa5aa64c07ad10fbaeb09b0c3b708ccf.zip
protocol: allow to send a zero output refresh rate
Fixed refresh rate doesn't always make sense for all outputs. In case it's not available or not relevant, allow compositors to send zero. For instance the can be the case for virtual outputs. Signed-off-by: Simon Ser <contact@emersion.fr>
Diffstat (limited to 'protocol')
-rw-r--r--protocol/wayland.xml3
1 files changed, 3 insertions, 0 deletions
diff --git a/protocol/wayland.xml b/protocol/wayland.xml
index f19c5b8..dee0ac1 100644
--- a/protocol/wayland.xml
+++ b/protocol/wayland.xml
@@ -2465,6 +2465,9 @@
willing to retrieve the output size in the global compositor
space should use xdg_output.logical_size instead.
+ The vertical refresh rate can be set to zero if it doesn't make
+ sense for this output (e.g. for virtual outputs).
+
Clients should not use the refresh rate to schedule frames. Instead,
they should use the wl_surface.frame event or the presentation-time
protocol.