wl_data_device_manager¤
Data transfer interface
The wl_data_device_manager is a singleton global object that provides access to inter-client data transfer mechanisms such as copy-and-paste and drag-and-drop. These mechanisms are tied to a wl_seat and this interface lets a client get a wl_data_device corresponding to a wl_seat.
Depending on the version bound, the objects created from the bound wl_data_device_manager object will have different requirements for functioning properly. See wl_data_source.set_actions, wl_data_offer.accept and wl_data_offer.finish for details.
Methods:
-
create_data_source–Create a new data source
-
get_data_device–Create a new data device
Drag and drop actions
This is a bitmask of the available/preferred actions in a drag-and-drop operation.
In the compositor, the selected action is a result of matching the actions offered by the source and destination sides. "action" events with a "none" action will be sent to both source and destination if there is no match. All further checks will effectively happen on (source actions ∩ destination actions).
In addition, compositors may also pick different actions in reaction to key modifiers being pressed. One common design that is used in major toolkits (and the behavior recommended for compositors) is:
- If no modifiers are pressed, the first match (in bit order) will be used.
- Pressing Shift selects "move", if enabled in the mask.
- Pressing Control selects "copy", if enabled in the mask.
Behavior beyond that is considered implementation-dependent. Compositors may for example bind other modifiers (like Alt/Meta) or drags initiated with other buttons than BTN_LEFT to specific actions (e.g. "ask").
create_data_source() -> wl_data_source
Create a new data source
Create a new data source.
Returns:
-
wl_data_source(wl_data_source) –The created object
get_data_device(seat: wl_seat) -> wl_data_device
Create a new data device
Create a new data device for a given seat.
Parameters:
Returns:
-
wl_data_device(wl_data_device) –The created object