protocol: clarify wl_display.delete_id

The previous description talked about what happens when "a client
deletes an object that it had created", ignoring the possibility of
destructor events.

This commit clarifies the intended behavior of delete_id. It does not
speak to the possibility of delete_id without a destructor message.

Signed-off-by: Julian Orth <ju.orth@gmail.com>
This commit is contained in:
Julian Orth 2026-03-20 13:17:52 +01:00
parent 53509f09ba
commit 866738125c

View file

@ -100,11 +100,15 @@
<event name="delete_id">
<description summary="acknowledge object ID deletion">
This event is used internally by the object ID management
logic. When a client deletes an object that it had created,
the server will send this event to acknowledge that it has
seen the delete request. When the client receives this event,
it will know that it can safely reuse the object ID.
This event is used internally by the object ID management logic.
When the server stops using an object created by the client, the server
sends this event. In particular, after sending this event, the server
will no longer send any events that contain the object as the receiver
or as an argument.
When the client receives this event, it knows that it can reuse the
object ID.
</description>
<arg name="id" type="uint" summary="deleted object ID"/>
</event>