wayland::server::data_device_manager_dnd_action − drag and drop actions
#include <wayland−server−protocol.hpp>
Inherits wayland::detail::bitfield< size, id >.
static const
wayland::detail::bitfield< 3, 6 > none
no action
static const wayland::detail::bitfield< 3, 6 >
copy
copy action
static const wayland::detail::bitfield< 3, 6 >
move
move action
static const wayland::detail::bitfield< 3, 6 >
ask
ask action
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’).
Definition at line 1639 of file wayland−server−protocol.hpp.
ask action
Definition at line 1652 of file wayland−server−protocol.hpp.
copy action
Definition at line 1648 of file wayland−server−protocol.hpp.
move action
Definition at line 1650 of file wayland−server−protocol.hpp.
no action
Definition at line 1646 of file wayland−server−protocol.hpp.
Generated automatically by Doxygen for Wayland++ from the source code.