TRUE ` . In this case, the handler is responsible for
providing the necessary information for displaying feedback to the user, by
calling gdk_drag_status().

######  [ GtkWidget::draw ](signal.Widget.draw.html)

This signal is emitted when a widget is supposed to render itself. The `
widget ` ‘  s top left corner must be painted at the origin of the passed in
context and be sized to the values returned by `
gtk_widget_get_allocated_width() ` and gtk_widget_get_allocated_height().

since: 3.0

######  [ GtkWidget::enter-notify-event ](signal.Widget.enter-notify-
event.html)

The ::enter-notify-event will be emitted when the pointer enters the ` widget
` ‘  s window.

######  [ GtkWidget::event ](signal.Widget.event.html)

The  GTK  \+ main loop will emit three signals for each  GDK  event delivered
to a widget: one generic ::event signal, another, more specific, signal that
matches the type of event delivered (e.g. ` GtkWidget::key-press-event ` ) and
finally a generic ` GtkWidget::event-after ` signal.

######  [ GtkWidget::event-after ](signal.Widget.event-after.html)

After the emission of the ` GtkWidget::event ` signal and (optionally) the
second more specific signal, ::event-after will be emitted regardless of the
previous two signals handlers return values.

######  [ GtkWidget::focus ](signal.Widget.focus.html)

No description available.

######  [ GtkWidget::focus-in-event ](signal.Widget.focus-in-event.html)

The ::focus-in-event signal will be emitted when the keyboard focus enters the
` widget ` ‘  s window.

######  [ GtkWidget::focus-out-event ](signal.Widget.focus-out-event.html)

The ::focus-out-event signal will be emitted when the keyboard focus leaves
the ` widget ` ‘  s window.

######  [ GtkWidget::grab-broken-event ](signal.Widget.grab-broken-event.html)

Emitted when a pointer or keyboard grab on a window belonging to ` widget `
gets broken.

since: 2.8

######  [ GtkWidget::grab-focus ](signal.Widget.grab-focus.html)

No description available.

######  [ GtkWidget::grab-notify ](signal.Widget.grab-notify.html)

The ::grab-notify signal is emitted when a widget becomes shadowed by a  GTK
\+ grab (not a pointer or keyboard grab) on another widget, or when it becomes
unshadowed due to a grab being removed.

######  [ GtkWidget::hide ](signal.Widget.hide.html)

The ::hide signal is emitted when ` widget ` is hidden, for example with
gtk_widget_hide().

######  [ GtkWidget::hierarchy-changed ](signal.Widget.hierarchy-changed.html)

The ::hierarchy-changed signal is emitted when the anchored state of a widget
changes. A widget is “anchored” when its toplevel ancestor is a ` GtkWindow `
. This signal is emitted when a widget changes from un-anchored to anchored or
vice-versa.

######  [ GtkWidget::key-press-event ](signal.Widget.key-press-event.html)

The ::key-press-event signal is emitted when a key is pressed. The signal
emission will reoccur at the key-repeat rate when the key is kept pressed.

######  [ GtkWidget::key-release-event ](signal.Widget.key-release-event.html)

The ::key-release-event signal is emitted when a key is released.

######  [ GtkWidget::keynav-failed ](signal.Widget.keynav-failed.html)

Gets emitted if keyboard navigation fails. See ` gtk_widget_keynav_failed() `
for details.

since: 2.12

######  [ GtkWidget::leave-notify-event ](signal.Widget.leave-notify-
event.html)

The ::leave-notify-event will be emitted when the pointer leaves the ` widget
` ‘  s window.

######  [ GtkWidget::map ](signal.Widget.map.html)

The ::map signal is emitted when ` widget ` is going to be mapped, that is
when the widget is visible (which is controlled with gtk_widget_set_visible())
and all its parents up to the toplevel widget are also visible. Once the map
has occurred, ` GtkWidget::map-event ` will be emitted.

######  [ GtkWidget::map-event ](signal.Widget.map-event.html)

The ::map-event signal will be emitted when the ` widget ` ‘  s window is
mapped. A window is mapped when it becomes visible on