-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 the screen.

######  [ GtkWidget::mnemonic-activate ](signal.Widget.mnemonic-activate.html)

The default handler for this signal activates ` widget ` if ` group_cycling `
is ` FALSE ` , or just makes ` widget ` grab focus if ` group_cycling ` is `
TRUE ` .

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

The ::motion-notify-event signal is emitted when the pointer moves over the
widget’s ` GdkWindow ` .

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

No description available.

######  [ GtkWidget::parent-set ](signal.Widget.parent-set.html)

The ::parent-set signal is emitted when a new parent has been set on a widget.

######  [ GtkWidget::popup-menu ](signal.Widget.popup-menu.html)

This signal gets emitted whenever a widget should pop up a context menu. This
usually happens through the standard key binding mechanism; by pressing a
certain key while a widget is focused, the user can cause the widget to pop up
a menu. For example, the ` GtkEntry ` widget creates a menu with clipboard
commands. See the [Popup Menu Migration Checklist][checklist-popup-menu] for
an example of how to use this signal.

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

The ::property-notify-event signal will be emitted when a property on the `
widget ` ‘  s window has been changed or deleted.

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

To receive this signal the ` GdkWindow ` associated to the widget needs to
enable the #GDK_PROXIMITY_IN_MASK mask.

######  [ GtkWidget::proximity-out-event ](signal