wayland/protocol
Simon Ser 8c121e1017 protocol: warn clients about some wl_output properties
All wl_output properties don't always make sense for all
compositors.

Some compositors might not implement a "global compositor space",
(e.g. 3D compositors) in which case properties like x and y don't
make sense.

Some compositors might expose virtual outputs, in which case modes,
make and model are not relevant.

In a lot of these situations, information from xdg_output is better
suited.

Compositors also expose output refresh rate, which shouldn't be used
for synchronization purposes.

Signed-off-by: Simon Ser <contact@emersion.fr>
Reviewed-by: Daniel Stone <daniels@collabora.com>
Reviewed-by: Jonas Ådahl <jadahl@gmail.com>
Reviewed-by: Derek Foreman <derek.foreman.wayland@gmail.com>
2019-02-20 10:07:05 -06:00
..
.gitignore Update .gitignore for protocol/ 2013-11-19 13:26:04 -08:00
tests.xml tests: Check for wrong fd delivery with zombie objects 2018-01-09 15:20:00 +00:00
wayland.dtd protocol: add the new bitfields to the dtd 2015-11-17 14:36:21 +02:00
wayland.xml protocol: warn clients about some wl_output properties 2019-02-20 10:07:05 -06:00