diff options
| author | Julian Orth <ju.orth@gmail.com> | 2024-04-24 16:17:58 +0200 |
|---|---|---|
| committer | Jonas Ã…dahl <jadahl@gmail.com> | 2024-11-18 09:25:20 +0000 |
| commit | 10df74c240d3cff4bd56bf17ebfc1a54883e00f5 (patch) | |
| tree | 0a6d685aea7776c3a08fc07c82b3c50af3bf830f /protocol | |
| parent | cursor: add check to ensure wl_shm_create_pool succeeded (diff) | |
| download | wayland-10df74c240d3cff4bd56bf17ebfc1a54883e00f5.tar wayland-10df74c240d3cff4bd56bf17ebfc1a54883e00f5.tar.gz wayland-10df74c240d3cff4bd56bf17ebfc1a54883e00f5.tar.bz2 wayland-10df74c240d3cff4bd56bf17ebfc1a54883e00f5.tar.lz wayland-10df74c240d3cff4bd56bf17ebfc1a54883e00f5.tar.xz wayland-10df74c240d3cff4bd56bf17ebfc1a54883e00f5.tar.zst wayland-10df74c240d3cff4bd56bf17ebfc1a54883e00f5.zip | |
protocol: add wl_fixes interface
This commit describes a new wl_fixes interface that can be used to
destroy wl_registry objects.
Users of libwayland-client should use it as follows:
- call wl_fixes_destroy_registry(registry)
- call wl_registry_destroy(registry)
Users of libwayland-server should, in their implementation of the
request, call wl_resource_destroy(registry).
It should be similar in other protocol implementations.
Signed-off-by: Julian Orth <ju.orth@gmail.com>
Diffstat (limited to 'protocol')
| -rw-r--r-- | protocol/wayland.xml | 27 |
1 files changed, 27 insertions, 0 deletions
diff --git a/protocol/wayland.xml b/protocol/wayland.xml index cd089e1..f32918e 100644 --- a/protocol/wayland.xml +++ b/protocol/wayland.xml @@ -3265,4 +3265,31 @@ </request> </interface> + <interface name="wl_fixes" version="1"> + <description summary="wayland protocol fixes"> + This global fixes problems with other core-protocol interfaces that + cannot be fixed in these interfaces themselves. + </description> + + <request name="destroy" type="destructor"> + <description summary="destroys this object"/> + </request> + + <request name="destroy_registry"> + <description summary="destroy a wl_registry"> + This request destroys a wl_registry object. + + The client should no longer use the wl_registry after making this + request. + + The compositor will emit a wl_display.delete_id event with the object ID + of the registry and will no longer emit any events on the registry. The + client should re-use the object ID once it receives the + wl_display.delete_id event. + </description> + <arg name="registry" type="object" interface="wl_registry" + summary="the registry to destroy"/> + </request> + </interface> + </protocol> |
