mirrors/wayland
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/wayland/wayland.git synced 2025-10-29 05:40:16 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

Merge branch 'wip/compositor-dnd-cursors' into 'main'

Browse source 
protocol: Make pointer cursor updates responsibility of compositors

See merge request wayland/wayland!467
This commit is contained in:
Carlos Garnacho 2025-09-20 15:58:51 +00:00
commit bc75e7dfde
1 changed files with 10 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

16
protocol/wayland.xml
View file

@ -518,7 +518,7 @@
</event>
</interface>
<interface name="wl_data_offer" version="3">
<interface name="wl_data_offer" version="4">
<description summary="offer to transfer data">
A wl_data_offer represents a piece of data offered for transfer
by another client (the source client). It is used by the
@ -711,7 +711,7 @@
</event>
</interface>
<interface name="wl_data_source" version="3">
<interface name="wl_data_source" version="4">
<description summary="offer to transfer data">
The wl_data_source object is the source side of a wl_data_offer.
It is created by the source client in a data transfer and
@ -858,15 +858,19 @@
into a "move" operation), so the effects of the final action must
always be applied in wl_data_offer.dnd_finished.
Clients can trigger cursor surface changes from this point, so
they reflect the current action.
Compositors should trigger cursor surface changes based on the
currently active action. This behavior is mandatory with the version 4
of the wl_data_device_manager interface, and optional before that.
Prior to version 3, the client holding the current wl_data_source
may trigger these cursor updates.
</description>
<arg name="dnd_action" type="uint" summary="action selected by the compositor"
enum="wl_data_device_manager.dnd_action"/>
</event>
</interface>
<interface name="wl_data_device" version="3">
<interface name="wl_data_device" version="4">
<description summary="data transfer device">
There is one wl_data_device per seat which can be obtained
from the global wl_data_device_manager singleton.
@ -1027,7 +1031,7 @@
</request>
</interface>
<interface name="wl_data_device_manager" version="3">
<interface name="wl_data_device_manager" version="4">
<description summary="data transfer interface">
The wl_data_device_manager is a singleton global object that
provides access to inter-client data transfer mechanisms such as