DropTargetSignalName

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 [methodGtk.DropTarget.reject] or ultimately by returning false from a [signalGtk.DropTarget::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 depends on the data, this function should return true, the [propertyGtk.DropTarget:preload] property should be set and the value should be inspected via the notify:value signal, calling [methodGtk.DropTarget.reject] if required.

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 is responsible for using the given value and performing the drop operation.

Emitted on the drop site when the pointer enters the widget.

It can be used to set up custom highlighting.

Emitted on the drop site when the pointer leaves the widget.

Its main purpose it to undo things done in [signalGtk.DropTarget::enter].

Emitted while the pointer is moving over the drop target.

The notify signal is emitted on an object when one of its properties has its value set through g_object_set_property(), g_object_set(), et al.

Note that getting this signal doesn’t itself guarantee that the value of the property has actually changed. When it is emitted is determined by the derived GObject class. If the implementor did not create the property with G_PARAM_EXPLICIT_NOTIFY, then any call to g_object_set_property() results in notify being emitted, even if the new value is the same as the old. If they did pass G_PARAM_EXPLICIT_NOTIFY, then this signal is emitted only when they explicitly call g_object_notify() or g_object_notify_by_pspec(), and common practice is to do that only when the value has actually changed.

This signal is typically used to obtain change notification for a single property, by specifying the property name as a detail in the g_signal_connect() call, like this:

(C Language Example):

g_signal_connect (text_view->buffer, "notify::paste-target-list",
                  G_CALLBACK (gtk_text_view_target_list_notify),
                  text_view)

It is important to note that you must use canonical parameter names as detail strings for the notify signal.

The GdkDragActions that this drop target supports.

The GdkDrop that is currently being performed.

The GdkDrop that is currently being performed.

drop is deprecated: Use [property@Gtk.DropTarget:current-drop] instead

The GdkContentFormats that determine the supported data formats.

The name for this controller, typically used for debugging purposes.

Whether the drop data should be preloaded when the pointer is only hovering over the widget but has not been released.

Setting this property allows finer grained reaction to an ongoing drop at the cost of loading more data.

The default value for this property is false to avoid downloading huge amounts of data by accident.

For example, if somebody drags a full document of gigabytes of text from a text editor across a widget with a preloading drop target, this data will be downloaded, even if the data is ultimately dropped elsewhere.

For a lot of data formats, the amount of data is very small (like GDK_TYPE_RGBA), so enabling this property does not hurt at all. And for local-only Drag-and-Drop operations, no data transfer is done, so enabling it there is free.

The limit for which events this controller will handle.

The propagation phase at which this controller will handle events.

The value for this drop operation.

This is nil if the data has not been loaded yet or no drop operation is going on.

Data may be available before the [signalGtk.DropTarget::drop] signal gets emitted - for example when the [propertyGtk.DropTarget:preload] property is set. You can use the notify signal to be notified of available data.

The widget receiving the GdkEvents that the controller will handle.