Gtk.DropTargetAsync¶
class — extends EventController
An event controller to receive Drag-and-Drop operations, asynchronously.
It is the more complete but also more complex method of handling drop
operations compared to DropTarget, and you should only use
it if GtkDropTarget doesn't provide all the features you need.
To use a GtkDropTargetAsync to receive drops on a widget, you create
a GtkDropTargetAsync object, configure which data formats and actions
you support, connect to its signals, and then attach it to the widget
with Widget.add_controller.
During a drag operation, the first signal that a GtkDropTargetAsync
emits is DropTargetAsync.accept, which is meant to determine
whether the target is a possible drop site for the ongoing drop. The
default handler for the ::accept signal accepts the drop if it finds
a compatible data format and an action that is supported on both sides.
If it is, and the widget becomes a target, you will receive a
DropTargetAsync.drag-enter signal, followed by
DropTargetAsync.drag-motion signals as the pointer moves,
optionally a DropTargetAsync.drop signal when a drop happens,
and finally a DropTargetAsync.drag-leave signal when the
pointer moves off the widget.
The ::drag-enter and ::drag-motion handler return a GdkDragAction
to update the status of the ongoing operation. The ::drop handler
should decide if it ultimately accepts the drop and if it does, it
should initiate the data transfer and finish the operation by calling
Gdk.Drop.finish.
Between the ::drag-enter and ::drag-leave signals the widget is a
current drop target, and will receive the StateFlags.DROP_ACTIVE
state, which can be used by themes to style the widget as a drop target.
Constructors¶
new¶
@classmethod
def new(cls, formats: Gdk.ContentFormats | None, actions: Gdk.DragAction | int) -> DropTargetAsync
Creates a new GtkDropTargetAsync object.
Parameters:
formats— the supported data formatsactions— the supported actions
Methods¶
get_actions¶
Gets the actions that this drop target supports.
get_formats¶
Gets the data formats that this drop target accepts.
If the result is None, all formats are expected to be supported.
reject_drop¶
Sets the drop as not accepted on this drag site.
This function should be used when delaying the decision on whether to accept a drag or not until after reading the data.
Parameters:
drop— theGdkDropof an ongoing drag operation
set_actions¶
Sets the actions that this drop target supports.
Parameters:
actions— the supported actions
set_formats¶
Sets the data formats that this drop target will accept.
Parameters:
formats— the supported data formats orNonefor any format
Properties¶
actions¶
The GdkDragActions that this drop target supports.
formats¶
The GdkContentFormats that determines the supported data formats.
Signals¶
accept¶
Emitted on the drop site when a drop operation is about to begin.
If the drop is not accepted, False will be returned and the drop target
will ignore the drop. If True is returned, the drop is accepted for now
but may be rejected later via a call to DropTargetAsync.reject_drop
or ultimately by returning False from a DropTargetAsync.drop
handler.
The default handler for this signal decides whether to accept the drop
based on the formats provided by the drop.
If the decision whether the drop will be accepted or rejected needs
further processing, such as inspecting the data, this function should
return True and proceed as is drop was accepted and if it decides to
reject the drop later, it should call DropTargetAsync.reject_drop.
drag-enter¶
Emitted on the drop site when the pointer enters the widget.
It can be used to set up custom highlighting.
drag-leave¶
Emitted on the drop site when the pointer leaves the widget.
Its main purpose it to undo things done in
GtkDropTargetAsync::drag-enter.
drag-motion¶
Emitted while the pointer is moving over the drop target.
drop¶
Emitted on the drop site when the user drops the data onto the widget.
The signal handler must determine whether the pointer position is in a
drop zone or not. If it is not in a drop zone, it returns False and no
further processing is necessary.
Otherwise, the handler returns True. In this case, this handler will
accept the drop. The handler must ensure that Gdk.Drop.finish
is called to let the source know that the drop is done. The call to
Gdk.Drop.finish must only be done when all data has been received.
To receive the data, use one of the read functions provided by
Gdk.Drop such as Gdk.Drop.read_async or
Gdk.Drop.read_value_async.