The DestDefaults enumeration specifies the various types of action that will be taken on behalf of the user for a drag destination site.

• DestDefaultMotion: If set for a widget, GTK+, during a drag over this widget will check if the drag matches this widget's list of possible targets and actions. GTK+ will then call dragStatus as appropriate.
• DestDefaultHighlight: If set for a widget, GTK+ will draw a highlight on this widget as long as a drag is over this widget and the widget drag format and action are acceptable.
• DestDefaultDrop: If set for a widget, when a drop occurs, GTK+ will will check if the drag matches this widget's list of possible targets and actions. If so, GTK+ will call dragGetData on behalf of the widget. Whether or not the drop is successful, GTK+ will call dragFinish. If the action was a move, then if the drag was successful, then True will be passed for the delete parameter to dragFinish
• DestDefaultAll: If set, specifies that all default actions should be taken.

Used in DragContext to indicate the protocol according to which DND is done.

Sets a widget as a potential drop destination.

• The DestDefaults flags specify what actions Gtk should take on behalf of a widget for drops onto that widget. The given actions and any targets set through dragDestSetTargetList only are used if DestDefaultMotion or DestDefaultDrop are given.
• Things become more complicated when you try to preview the dragged data, as described in the documentation for dragMotion. The default behaviors described by flags make some assumptions, that can conflict with your own signal handlers. For instance DestDefaultDrop causes invocations of dragStatus in the handler of dragMotion, and invocations of dragFinish in dragDataReceived. Especially the latter is dramatic, when your own dragMotion handler calls dragGetData to inspect the dragged data.

Sets this widget as a proxy for drops to another window.

Clears information about a drop destination set with dragDestSet. The widget will no longer receive notification of drags.

Looks for a match between the targets mentioned in the context and the TargetList, returning the first matching target, otherwise returning Nothing. If Nothing is given as target list, use the value from destGetTargetList. Some widgets may have different valid targets for different parts of the widget; in that case, they will have to implement a dragMotion handler that passes the correct target list to this function.

Returns the list of targets this widget can accept for drag-and-drop.

Sets the target types that this widget can accept from drag-and-drop. The widget must first be made into a drag destination with dragDestSet.

Add the text targets supported by the selection mechanism to the target list of the drag source. The targets are added with an InfoId of 0. If you need another value, use targetListAddTextTargets and dragSourceSetTargetList.

Add image targets supported by the selection mechanism to the target list of the drag source. The targets are added with an InfoId of 0. If you need another value, use targetListAddTextTargets and dragSourceSetTargetList.

Add URI targets supported by the selection mechanism to the target list of the drag source. The targets are added with an InfoId of 0. If you need another value, use targetListAddTextTargets and dragSourceSetTargetList.

Visualises the actions offered by the drag source.

• This function is called by the drag destination in response to dragMotion called by the drag source. The passed-in action is indicated where Nothing will show that the drop is not allowed.

Informs the drag source that the drop is finished, and that the data of the drag will no longer be required.

Gets the data associated with a drag. When the data is received or the retrieval fails, GTK+ will emit a dragDataReceived signal. Failure of the retrieval is indicated by passing Nothing in the selectionData signal. However, when dragGetData is called implicitely because the DestDefaultDrop was set, then the widget will not receive notification of failed drops.

Queries he source widget for a drag.

• If the drag is occurring within a single application, a pointer to the source widget is returned. Otherwise the return value is Nothing.

Draws a highlight around a widget. This will attach handlers to the expose handlers, so the highlight will continue to be displayed until dragUnhighlight is called.

Removes a highlight set by dragHighlight from a widget.

Changes the icon for a drag to a given widget. GTK+ will not destroy the widget, so if you don't want it to persist, you should connect to the dragEnd signal and destroy it yourself.

• The function must be called with the context of the source side.

Set the given Pixbuf as the icon for the given drag.

Sets the icon for a given drag from a stock ID.

Sets the icon for a given drag from a named themed icon. See the docs for IconTheme for more details. Note that the size of the icon depends on the icon theme (the icon is loaded at the DND size), thus x and y hot-spots have to be used with care. Since Gtk 2.8.

Sets the icon for a particular drag to the default icon. This function must be called with a context for the source side of a drag

Checks to see if a mouse drag starting at (startX, startY) and ending at (currentX, currenty) has passed the GTK+ drag threshold, and thus should trigger the beginning of a drag-and-drop operation.

Sets up a widget so that GTK+ will start a drag operation when the user clicks and drags on the widget. The widget must have a window. Note that a set of possible targets have to be set for a drag to be successful.

Sets the icon that will be used for drags from a particular widget from a Pixbuf.

Sets the icon that will be used for drags from a particular source to a stock icon.

Sets the icon that will be used for drags from a particular source to a themed icon. See the docs for IconTheme for more details.

Undoes the effects of dragSourceSet.

Changes the target types that this widget offers for drag-and-drop. The widget must first be made into a drag source with dragSourceSet.

• Since Gtk 2.4.

Gets the list of targets this widget can provide for drag-and-drop.

• Since Gtk 2.4.

Add the text targets supported by Selection to the target list of the drag source. The targets are added with info = 0. If you need another value, use targetListAddTextTargets and dragSourceSetTargetList.

• Since Gtk 2.6.

Add the image targets supported by Selection to the target list of the drag source. The targets are added with info = 0. If you need another value, use targetListAddTextTargets and dragSourceSetTargetList.

• Since Gtk 2.6.

Add the URI targets supported by Selection to the target list of the drag source. The targets are added with info = 0. If you need another value, use targetListAddTextTargets and dragSourceSetTargetList.

• Since Gtk 2.6.

The dragBegin signal is emitted on the drag source when a drag is started. A typical reason to connect to this signal is to set up a custom drag icon with dragSourceSetIcon.

The dragDataDelete signal is emitted on the drag source when a drag with the action ActionMove is successfully completed. The signal handler is responsible for deleting the data that has been dropped. What "delete" means, depends on the context of the drag operation.

The dragDataGet signal is emitted on the drag source when the drop site requests the data which is dragged. It is the responsibility of the signal handler to set the selection data in the format which is indicated by InfoId. See selectionDataSet and selectionDataSetText.

The dragDataReceived signal is emitted on the drop site when the dragged data has been received. If the data was received in order to determine whether the drop will be accepted, the handler is expected to call dragStatus and not finish the drag. If the data was received in response to a dragDrop signal (and this is the last target to be received), the handler for this signal is expected to process the received data and then call dragFinish, setting the success parameter depending on whether the data was processed successfully.

The handler may inspect and modify dragContextAction before calling dragFinish, e.g. to implement ActionAsk as shown in the following example:

The dragDrop signal is emitted on the drop site when the user drops the data onto the widget. The signal handler must determine whether the cursor 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, the handler must ensure that dragFinish is called to let the source know that the drop is done. The call to dragFinish can be done either directly or in a dragDataReceived handler which gets triggered by calling dropGetData to receive the data for one or more of the supported targets.

The dragEnd signal is emitted on the drag source when a drag is finished. A typical reason to connect to this signal is to undo things done in dragBegin.

The dragFailed signal is emitted on the drag source when a drag has failed. The signal handler may hook custom code to handle a failed DND operation based on the type of error, it returns True is the failure has been already handled (not showing the default "drag operation failed" animation), otherwise it returns False.

• Available since Gtk+ 2.12.0.

The dragLeave signal is emitted on the drop site when the cursor leaves the widget. A typical reason to connect to this signal is to undo things done in dragMotion, e.g. undo highlighting with dragUnhighlight

The dragMotion signal is emitted on the drop site when the user moves the cursor over the widget during a drag. The signal handler must determine whether the cursor 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, the handler is responsible for providing the necessary information for displaying feedback to the user, by calling dragStatus. If the decision whether the drop will be accepted or rejected can't be made based solely on the cursor position and the type of the data, the handler may inspect the dragged data by calling dragGetData and defer the dragStatus call to the dragDataReceived handler.

Note that there is no dragEnter signal. The drag receiver has to keep track of whether he has received any dragMotion signals since the last dragLeave and if not, treat the dragMotion signal as an "enter" signal. Upon an "enter", the handler will typically highlight the drop site with dragHighlight.