wayland::server::data_device_manager_dnd_action(3) | Wayland++ | wayland::server::data_device_manager_dnd_action(3) |
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:
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 1638 of file wayland-server-protocol.hpp.
ask action
Definition at line 1651 of file wayland-server-protocol.hpp.
copy action
Definition at line 1647 of file wayland-server-protocol.hpp.
move action
Definition at line 1649 of file wayland-server-protocol.hpp.
no action
Definition at line 1645 of file wayland-server-protocol.hpp.
Generated automatically by Doxygen for Wayland++ from the source code.
Mon Apr 22 2024 09:52:15 | Version 1.0.0 |