| Value | Meaning |
|---|---|
| NOTHING-1 | a special code to indicate a null event. |
| DELETE0 | the window manager has requested that the toplevel window be hidden or destroyed, usually when the user clicks on a special icon in the title bar. |
| DESTROY1 | the window has been destroyed. |
| EXPOSE2 | all or part of the window has become visible and needs to be redrawn. |
| MOTION_NOTIFY3 | the pointer (usually a mouse) has moved. |
| BUTTON_PRESS4 | a mouse button has been pressed. |
| DOUBLE_BUTTON_PRESS5 | alias for %GDK_2BUTTON_PRESS, added in 3.6. |
| TRIPLE_BUTTON_PRESS6 | alias for %GDK_3BUTTON_PRESS, added in 3.6. |
| BUTTON_RELEASE7 | a mouse button has been released. |
| KEY_PRESS8 | a key has been pressed. |
| KEY_RELEASE9 | a key has been released. |
| ENTER_NOTIFY10 | the pointer has entered the window. |
| LEAVE_NOTIFY11 | the pointer has left the window. |
| FOCUS_CHANGE12 | the keyboard focus has entered or left the window. |
| CONFIGURE13 | the size, position or stacking order of the window has changed. Note that GTK+ discards these events for %GDK_WINDOW_CHILD windows. |
| MAP14 | the window has been mapped. |
| UNMAP15 | the window has been unmapped. |
| PROPERTY_NOTIFY16 | a property on the window has been changed or deleted. |
| SELECTION_CLEAR17 | the application has lost ownership of a selection. |
| SELECTION_REQUEST18 | another application has requested a selection. |
| SELECTION_NOTIFY19 | a selection has been received. |
| PROXIMITY_IN20 | an input device has moved into contact with a sensing surface (e.g. a touchscreen or graphics tablet). |
| PROXIMITY_OUT21 | an input device has moved out of contact with a sensing surface. |
| DRAG_ENTER22 | the mouse has entered the window while a drag is in progress. |
| DRAG_LEAVE23 | the mouse has left the window while a drag is in progress. |
| DRAG_MOTION24 | the mouse has moved in the window while a drag is in progress. |
| DRAG_STATUS25 | the status of the drag operation initiated by the window has changed. |
| DROP_START26 | a drop operation onto the window has started. |
| DROP_FINISHED27 | the drop operation initiated by the window has completed. |
| CLIENT_EVENT28 | a message has been received from another application. |
| VISIBILITY_NOTIFY29 | the window visibility status has changed. |
| SCROLL31 | the scroll wheel was turned |
| WINDOW_STATE32 | the state of a window has changed. See #GdkWindowState for the possible window states |
| SETTING33 | a setting has been modified. |
| OWNER_CHANGE34 | the owner of a selection has changed. This event type was added in 2.6 |
| GRAB_BROKEN35 | a pointer or keyboard grab was broken. This event type was added in 2.8. |
| DAMAGE36 | the content of the window has been changed. This event type was added in 2.14. |
| TOUCH_BEGIN37 | A new touch event sequence has just started. This event type was added in 3.4. |
| TOUCH_UPDATE38 | A touch event sequence has been updated. This event type was added in 3.4. |
| TOUCH_END39 | A touch event sequence has finished. This event type was added in 3.4. |
| TOUCH_CANCEL40 | A touch event sequence has been canceled. This event type was added in 3.4. |
| EVENT_LAST41 | marks the end of the GdkEventType enumeration. Added in 2.18 |
Specifies the type of the event.
Do not confuse these events with the signals that GTK+ widgets emit. Although many of these events result in corresponding signals being emitted, the events are often transformed or filtered along the way.
In some language bindings, the values %GDK_2BUTTON_PRESS and %GDK_3BUTTON_PRESS would translate into something syntactically invalid (eg Gdk.EventType.2ButtonPress, where a symbol is not allowed to start with a number). In that case, the aliases %GDK_DOUBLE_BUTTON_PRESS and %GDK_TRIPLE_BUTTON_PRESS can be used instead.