Julian Orth 4ed26b057e protocol: move wl_buffer interpretation to wl_surface.attach ... A wl_buffer is always a dumb collection of color channels whose interpretation is determined ad-hoc at the point of use. For example, is is possible for the same buffer to be attached two wl_surfaces concurrently: - The first surface interprets the color channels as sRGB with   pre-multiplied alpha. - The second surface interprets the color channels as BT.2020/PQ with   straight alpha. Therefore the interpretation is not a property of the wl_buffer itself. Factory interfaces for wl_buffer object should therefore only talk about how the electrical values are communicated between clients and compositors. Signed-off-by: Julian Orth <ju.orth@gmail.com>		2025-06-03 16:24:46 +02:00
..
.gitignore	Update .gitignore for protocol/	2013-11-19 13:26:04 -08:00
generate-shm-formats.py	Add an automated script to update wl_shm.format	2019-09-06 12:09:22 +00:00
tests.xml	Replace initial 8 spaces with a tab for all xml files	2020-04-29 12:21:33 +00:00
wayland.dtd	Add support for the deprecated-since XML attribute	2024-04-24 16:18:28 +00:00
wayland.xml	protocol: move wl_buffer interpretation to wl_surface.attach	2025-06-03 16:24:46 +02:00