From f284a0cb85183affaf41e12c11963667c5d3fb20 Mon Sep 17 00:00:00 2001 From: Pekka Paalanen Date: Thu, 6 Feb 2025 15:41:00 +0200 Subject: [PATCH] color: define global_remove behavior https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/14#note_2756612 https://gitlab.freedesktop.org/wayland/wayland/-/issues/484 Toolkit authors are reluctant to handle the global removal, because on most compositors the removal will never happen. OTOH, there is a compositor author who wants to be able to change color-management capabilities at runtime due to dynamically switching renderers. This new wording strongly suggests the global is never removed to let toolkits avoid all the code that removal tracking would need. Removal is still technically allowed, but it is not generally expected that clients would handle it. Signed-off-by: Pekka Paalanen --- staging/color-management/color-management-v1.xml | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/staging/color-management/color-management-v1.xml b/staging/color-management/color-management-v1.xml index 3159f21..7f8da78 100644 --- a/staging/color-management/color-management-v1.xml +++ b/staging/color-management/color-management-v1.xml @@ -73,11 +73,13 @@ - A global interface used for getting color management extensions for - wl_surface and wl_output objects, and for creating client defined image - description objects. The extension interfaces allow + A singleton global interface used for getting color management extensions + for wl_surface and wl_output objects, and for creating client defined + image description objects. The extension interfaces allow getting the image description of outputs and setting the image description of surfaces. + + Compositors should never remove this global.