| Version: 3.3.1

Public Member Functions | List of all members
wxKeyEvent Class Reference
Class List by Category » Events

`#include <wx/event.h>`

Inheritance diagram for wxKeyEvent:
[legend]

## Detailed Description

This event class contains information about key press and release events.

The main information carried by this event is the key being pressed or released. It can be accessed using one of GetUnicodeKey(), GetKeyCode() or GetRawKeyCode() functions. For the printable characters, GetUnicodeKey() should be used as it works for any keys, including non-Latin-1 characters that can be entered when using national keyboard layouts. GetKeyCode() should be used to handle special characters (such as cursor arrows keys or `HOME` or `INS` and so on) which correspond to wxKeyCode enum elements above the `WXK_START` constant. While GetKeyCode() also returns the character code for Latin-1 keys for compatibility, it doesn't work for Unicode characters in general and will return `WXK_NONE` for any non-Latin-1 ones. If both GetUnicodeKey() and GetKeyCode() return `WXK_NONE` then the key has no `WXK_xxx` mapping and GetRawKeyCode() can be used to distinguish between keys, but raw key codes are platform specific. For these reasons, it is recommended to always use GetUnicodeKey() and only fall back to GetKeyCode() if GetUnicodeKey() returned `WXK_NONE`, meaning that the event corresponds to a non-printable special keys, then optionally check GetRawKeyCode() if GetKeyCode() also returned `WXK_NONE` or simply ignore that key.

While these three functions can be used with the events of `wxEVT_KEY_DOWN`, `wxEVT_KEY_UP` and `wxEVT_CHAR` types, the values returned by them are different for the first two events and the last one. For the latter, the key returned corresponds to the character that would appear in e.g. a text zone if the user pressed the key in it. As such, its value depends on the current state of the Shift key and, for the letters, on the state of Caps Lock modifier. For example, if `A` key is pressed without Shift being held down, wxKeyEvent of type `wxEVT_CHAR` generated for this key press will return (from either GetKeyCode() or GetUnicodeKey() as their meanings coincide for ASCII characters) key code of 97 corresponding the ASCII value of `a`. And if the same key is pressed but with Shift being held (or Caps Lock being active), then the key could would be 65, i.e. ASCII value of capital `A`.

However for the key down and up events the returned key code will instead be `A` independently of the state of the modifier keys i.e. it depends only on physical key being pressed and is not translated to its logical representation using the current keyboard state.

To summarize: you should handle `wxEVT_CHAR` if you need the character that pressing the key would produce and `wxEVT_KEY_DOWN` if you only need the value of the key itself, independent of the current keyboard state.

In more details, the key codes for the key down and up events are determined as follows:

- For the ASCII letters they correspond to the upper case value of the letter.
- For the other Latin-1 characters, including letters such as `ù` or `ö` but also non-letter characters such as `²`, the key code is the value of the corresponding character without conversion to upper case (this behaviour is inconsistent but preserved for compatibility).
- For the other keys producing (non-Latin) printable characters, the key code is the ASCII code of the character the same key would produce in the standard US keyboard layout.
- For the special non-printable keys the code corresponds to the name of the key, e.g. `WXK_INSERT` for the Insert key, and is the same as for the char events as no translation is performed for such keys.

For example, the key marked with `]` in the US layout generates the key code `$` when using the standard French AZERTY layout because this is the label of this key on the keyboards using this layout. However if the same physical key is pressed in Ukrainian keyboard layout where it would normally produce the non-ASCII letter `ï`, then the key code is the code of the corresponding character in the standard US layout, i.e. `]`. This also applies to the letters, i.e. the key code producing the Cyrillic letter `ц` in Ukrainian layout generates the key code `W` corresponding to the letter of this key in the US layout.

Note
  Not all key down events may be generated by the user. As an example, `wxEVT_KEY_DOWN` with `=` key code can be generated using the standard US keyboard layout but not using the German one because the `=` key corresponds to Shift-0 key combination in this layout and the key code for it is `0`, not `=`. Because of this you should avoid requiring your users to type key events that might be impossible to enter on their keyboard. Similarly, not all possible accelerator can be used in all keyboard layouts, e.g. `Ctrl-;` can't be activated when using the standard French AZERTY layout because `;` is on the same key as `.` in this layout and pressing it generates `Ctrl-.`. Hence it is best to avoid using accelerators using non-alphanumeric characters for the programs that can be used with different keyboard layouts.

Another difference between key and char events is that another kind of translation is done for the latter ones when the Control key is pressed: char events for ASCII letters in this case carry codes corresponding to the ASCII value of Ctrl-Letter, i.e. 1 for Ctrl-A, 2 for Ctrl-B and so on until 26 for Ctrl-Z. This is convenient for terminal-like applications and can be completely ignored by all the other ones (if you need to handle Ctrl-A it is probably a better idea to use the key event rather than the char one). For completeness, the same translation is done for the presses of ``[, `\`, ``], `^` and `_` keys which are mapped to ASCII values from 27 to 31. Since version 2.9.2, the enum values `WXK_CONTROL_A` - `WXK_CONTROL_Z` can be used instead of the non-descriptive constant values 1-26.

Note
  Unfortunately, some keys don't generate consistent events when used with the Control key. Notably:
  - `Ctrl-Backspace` generates events with both key code and Unicode code of WXK_DELETE in wxMSW, but WXK_BACK in wxGTK.
  - `Ctrl-Enter` generates events with both key code and Unicode code of WXK_CONTROL_J in wxMSW, but WXK_RETURN in wxGTK.
  - `Ctrl-Letter` generates events corresponding to the control code even when the letter is mapped to a non-Latin letter in the current keyboard layout in wxMSW, but doesn't generate any `wxEVT_CHAR` events at all in this case in wxGTK. Don't rely on getting these events in wxMSW, this behaviour is only preserved for compatibility.

Finally, modifier keys only generate key events but no char events at all. The modifiers keys are `WXK_SHIFT`, `WXK_CONTROL`, `WXK_ALT` and various `WXK_WINDOWS_XXX` from wxKeyCode enum.

Modifier keys events are special in one additional aspect: usually the keyboard state associated with a key press is well defined, e.g. wxKeyboardState::ShiftDown() returns `true` only if the Shift key was held pressed when the key that generated this event itself was pressed. There is an ambiguity for the key press events for Shift key itself however. By convention, it is considered to be already pressed when it is pressed and already released when it is released. In other words, `wxEVT_KEY_DOWN` event for the Shift key itself will have `wxMOD_SHIFT` in GetModifiers() and ShiftDown() will return true while the `wxEVT_KEY_UP` event for Shift itself will not have `wxMOD_SHIFT` in its modifiers and ShiftDown() will return false.

Tip: You may discover the key codes and modifiers generated by all the keys on your system interactively by running the Key Event Sample wxWidgets sample and pressing some keys in it.

Note
  If a key down (`EVT_KEY_DOWN`) event is caught and the event handler does not call `event.Skip()` then the corresponding char event (`EVT_CHAR`) will not happen. This is by design and enables the programs that handle both types of events to avoid processing the same key twice. As a consequence, if you do not want to suppress the `wxEVT_CHAR` events for the keys you handle, always call `event.Skip()` in your `wxEVT_KEY_DOWN` handler. Not doing may also prevent accelerators defined using this key from working.
  If a key is maintained in a pressed state, you will typically get a lot of (automatically generated) key down events but only one key up one at the end when the key is released so it is wrong to assume that there is one up event corresponding to each down one.
  For Windows programmers: The key and char events in wxWidgets are similar to but slightly different from Windows `WM_KEYDOWN` and `WM_CHAR` events. In particular, Alt-x combination will generate a char event in wxWidgets (unless it is used as an accelerator) and almost all keys, including ones without ASCII equivalents, generate char events too.

## Events using this class

The following event handler macros redirect the events to member function handlers 'func' with prototypes like:

void handlerFuncName(wxKeyEvent& event)

Event macros:

- EVT_KEY_DOWN(func):
  Process a `wxEVT_KEY_DOWN` event (any key has been pressed). If this event is handled and not skipped, `wxEVT_CHAR` will not be generated at all for this key press (but `wxEVT_KEY_UP` will be).
- EVT_KEY_UP(func):
  Process a `wxEVT_KEY_UP` event (any key has been released).
- EVT_CHAR(func):
  Process a `wxEVT_CHAR` event.
- EVT_CHAR_HOOK(func):
  Process a `wxEVT_CHAR_HOOK` event. Unlike all the other key events, this event is propagated upwards the window hierarchy which allows intercepting it in the parent window of the focused window to which it is sent initially (if there is no focused window, this event is sent to the wxApp global object). It is also generated before any other key events and so gives the parent window an opportunity to modify the keyboard handling of its children, e.g. it is used internally by wxWidgets in some ports to intercept pressing Esc key in any child of a dialog to close the dialog itself when it's pressed. By default, if this event is handled, i.e. the handler doesn't call wxEvent::Skip(), neither `wxEVT_KEY_DOWN` nor `wxEVT_CHAR` events will be generated (although `wxEVT_KEY_UP` still will be), i.e. it replaces the normal key events. However by calling the special DoAllowNextEvent() method you can handle `wxEVT_CHAR_HOOK` and still allow normal events generation. This is something that is rarely useful but can be required if you need to prevent a parent `wxEVT_CHAR_HOOK` handler from running without suppressing the normal key events. Finally notice that this event is not generated when the mouse is captured as it is considered that the window which has the capture should receive all the keyboard events too without allowing its parent wxTopLevelWindow to interfere with their processing.

See also
  wxKeyboardState

##

Library: wxCore
Category: Events

## Public Member Functions
| wxKeyEvent (wxEventType keyEventType=wxEVT_NULL)
| Constructor. More...
int | GetKeyCode () const
| Returns the key code of the key that generated this event. More...
bool | IsKeyInCategory (int category) const
| Returns true if the key is in the given key category. More...
bool | IsAutoRepeat () const
| Returns true if this event is an auto-repeat of the key, false if this is the initial key press. More...
wxUint32 | GetRawKeyCode () const
| Returns the raw key code for this event. More...
wxUint32 | GetRawKeyFlags () const
| Returns the low level key flags for this event. More...
wxChar | GetUnicodeKey () const
| Returns the Unicode character corresponding to this key event. More...
wxCoord | GetX () const
| Returns the X position (in client coordinates) of the event. More...
wxCoord | GetY () const
| Returns the Y position (in client coordinates) of the event. More...
void | DoAllowNextEvent ()
| Allow normal key events generation. More...
bool | IsNextEventAllowed () const
| Returns true if DoAllowNextEvent() had been called, false by default. More...
wxPoint | GetPosition () const
| Obtains the position (in client coordinates) at which the key was pressed. More...
void | GetPosition (wxCoord *x, wxCoord *y) const
| Obtains the position (in client coordinates) at which the key was pressed. More...
Public Member Functions inherited from wxEvent
| wxEvent (int id=0, wxEventType eventType=wxEVT_NULL)
| Constructor. More...
virtual wxEvent * | Clone () const =0
| Returns a copy of the event. More...
wxObject * | GetEventObject () const
| Returns the object (usually a window) associated with the event, if any. More...
wxEventType | GetEventType () const
| Returns the identifier of the given event type, such as `wxEVT_BUTTON`. More...
virtual wxEventCategory | GetEventCategory () const
| Returns a generic category for this event. More...
int | GetId () const
| Returns the identifier associated with this event, such as a button command id. More...
wxObject * | GetEventUserData () const
| Return the user data associated with a dynamically connected event handler. More...
bool | GetSkipped () const
| Returns true if the event handler should be skipped, false otherwise. More...
long | GetTimestamp () const
| Gets the timestamp for the event. More...
bool | IsCommandEvent () const
| Returns true if the event is or is derived from wxCommandEvent else it returns false. More...
void | ResumePropagation (int propagationLevel)
| Sets the propagation level to the given value (for example returned from an earlier call to wxEvent::StopPropagation). More...
void | SetEventObject (wxObject *object)
| Sets the originating object. More...
void | SetEventType (wxEventType type)
| Sets the event type. More...
void | SetId (int id)
| Sets the identifier associated with this event, such as a button command id. More...
void | SetTimestamp (long timeStamp=0)
| Sets the timestamp for the event. More...
bool | ShouldPropagate () const
| Test if this event should be propagated or not, i.e. if the propagation level is currently greater than 0. More...
void | Skip (bool skip=true)
| This method can be used inside an event handler to control whether further event handlers bound to this event will be called after the current one returns. More...
int | StopPropagation ()
| Stop the event from propagating to its parent window. More...
Public Member Functions inherited from wxObject
| wxObject ()
| Default ctor; initializes to nullptr the internal reference data. More...
| wxObject (const wxObject &other)
| Copy ctor. More...
virtual | ~wxObject ()
| Destructor. More...
virtual wxClassInfo * | GetClassInfo () const
| This virtual function is redefined for every class that requires run-time type information, when using the wxDECLARE_CLASS macro (or similar). More...
wxObjectRefData * | GetRefData () const
| Returns the wxObject::m_refData pointer, i.e. the data referenced by this object. More...
bool | IsKindOf (const wxClassInfo *info) const
| Determines whether this class is a subclass of (or the same class as) the given class. More...
bool | IsSameAs (const wxObject &obj) const
| Returns true if this object has the same data pointer as obj. More...
void | Ref (const wxObject &clone)
| Makes this object refer to the data in clone. More...
void | SetRefData (wxObjectRefData *data)
| Sets the wxObject::m_refData pointer. More...
void | UnRef ()
| Decrements the reference count in the associated data, and if it is zero, deletes the data. More...
void | UnShare ()
| This is the same of AllocExclusive() but this method is public. More...
void | operator delete (void *buf)
| The delete operator is defined for debugging versions of the library only, when the identifier `__WXDEBUG__` is defined. More...
void * | operator new (size_t size, const wxString &filename=nullptr, int lineNum=0)
| The new operator is defined for debugging versions of the library only, when the identifier `__WXDEBUG__` is defined. More...
Public Member Functions inherited from wxKeyboardState
| wxKeyboardState (bool controlDown=false, bool shiftDown=false, bool altDown=false, bool metaDown=false)
| Constructor initializes the modifier key settings. More...
int | GetModifiers () const
| Return the bit mask of all pressed modifier keys. More...
bool | HasAnyModifiers () const
| Returns true if any modifiers at all are pressed. More...
bool | HasModifiers () const
| Returns true if Control or Alt are pressed. More...
bool | ControlDown () const
| Returns true if the Control key or Apple/Command key under macOS is pressed. More...
bool | RawControlDown () const
| Returns true if the Control key (also under macOS). More...
bool | ShiftDown () const
| Returns true if the Shift key is pressed. More...
bool | MetaDown () const
| Returns true if the Meta/Windows/Apple key is pressed. More...
bool | AltDown () const
| Returns true if the Alt key is pressed. More...
bool | CmdDown () const
| Returns true if the key used for command accelerators is pressed. More...
void | SetControlDown (bool down)
void | SetRawControlDown (bool down)
void | SetShiftDown (bool down)
void | SetAltDown (bool down)
void | SetMetaDown (bool down)

## Additional Inherited Members
Protected Member Functions inherited from wxObject
void | AllocExclusive ()
| Ensure that this object's data is not shared with any other object. More...
virtual wxObjectRefData * | CreateRefData () const
| Creates a new instance of the wxObjectRefData-derived class specific to this object and returns it. More...
virtual wxObjectRefData * | CloneRefData (const wxObjectRefData *data) const
| Creates a new instance of the wxObjectRefData-derived class specific to this object and initializes it copying data. More...
Protected Attributes inherited from wxEvent
int | m_propagationLevel
| Indicates how many levels the event can propagate. More...
Protected Attributes inherited from wxObject
wxObjectRefData * | m_refData
| Pointer to an object which is the object's reference-counted data. More...

## Constructor & Destructor Documentation

## ◆ wxKeyEvent()

wxKeyEvent::wxKeyEvent | ( | wxEventType | keyEventType = `wxEVT_NULL` | ) |

Constructor.

Currently, the only valid event types are `wxEVT_CHAR` and `wxEVT_CHAR_HOOK`.

## Member Function Documentation

## ◆ DoAllowNextEvent()

void wxKeyEvent::DoAllowNextEvent | ( |  | ) |

Allow normal key events generation.

Can be called from `wxEVT_CHAR_HOOK` handler to indicate that the generation of normal events should not be suppressed, as it happens by default when this event is handled.

The intended use of this method is to allow some window object to prevent `wxEVT_CHAR_HOOK` handler in its parent window from running by defining its own handler for this event. Without calling this method, this would result in not generating `wxEVT_KEY_DOWN` nor `wxEVT_CHAR` events at all but by calling it you can ensure that these events would still be generated, even if `wxEVT_CHAR_HOOK` event was handled.

Since
  2.9.3

## ◆ GetKeyCode()

int wxKeyEvent::GetKeyCode | ( |  | ) | const

Returns the key code of the key that generated this event.

ASCII symbols return normal ASCII values, while events from special keys such as "left cursor arrow" (`WXK_LEFT`) return values outside of the ASCII range. See wxKeyCode for a full list of the virtual key codes.

Note that this method returns a meaningful value only for special non-alphanumeric keys or if the user entered a Latin-1 character (this includes ASCII and the accented letters found in Western European languages but not letters of other alphabets such as e.g. Cyrillic). Otherwise it simply method returns `WXK_NONE` and GetUnicodeKey() should be used to obtain the corresponding Unicode character.

Using GetUnicodeKey() is in general the right thing to do if you are interested in the characters typed by the user, GetKeyCode() should be only used for special keys (for which GetUnicodeKey() returns `WXK_NONE`). To handle both kinds of keys you might write:

void MyHandler::OnChar(wxKeyEvent& event)
{
wxChar uc = event.GetUnicodeKey();
if ( uc != WXK_NONE )
{
// It's a "normal" character. Notice that this includes
// control characters in 1..31 range, e.g. WXK_RETURN or
// WXK_BACK, so check for them explicitly.
if ( uc >= 32 )
{
wxLogMessage("You pressed '%c'", uc);
}
else
{
// It's a control character
...
}
}
else // No Unicode equivalent.
{
// It's a special key, deal with all the known ones:
switch ( event.GetKeyCode() )
{
case WXK_LEFT:
case WXK_RIGHT:
... move cursor ...
break;
case WXK_F1:
... give help ...
break;
}
}
}
wxKeyEvent
This event class contains information about key press and release events.
Definition: event.h:1511
wxKeyEvent::GetKeyCode
int GetKeyCode() const
Returns the key code of the key that generated this event.
WXK_NONE
@ WXK_NONE
No key.
Definition: defs.h:879
WXK_LEFT
@ WXK_LEFT
Definition: defs.h:950
WXK_F1
@ WXK_F1
Definition: defs.h:976
WXK_RIGHT
@ WXK_RIGHT
Definition: defs.h:952
wxLogMessage
void wxLogMessage(const char *formatString,...)
For all normal, informational messages.
wxChar
wchar_t wxChar
wxChar is a compatibility typedef always defined as wchar_t now.
Definition: chartype.h:90

## ◆ GetPosition() [1/2]

wxPoint wxKeyEvent::GetPosition | ( |  | ) | const

Obtains the position (in client coordinates) at which the key was pressed.

Notice that under most platforms this position is simply the current mouse pointer position and has no special relationship to the key event itself.

x and y may be nullptr if the corresponding coordinate is not needed.

## ◆ GetPosition() [2/2]

void wxKeyEvent::GetPosition | ( | wxCoord * | x,
|  | wxCoord * | y
| ) |  | const

Obtains the position (in client coordinates) at which the key was pressed.

Notice that under most platforms this position is simply the current mouse pointer position and has no special relationship to the key event itself.

x and y may be nullptr if the corresponding coordinate is not needed.

## ◆ GetRawKeyCode()

wxUint32 wxKeyEvent::GetRawKeyCode | ( |  | ) | const

Returns the raw key code for this event.

The flags are platform-dependent and should only be used if the functionality provided by other wxKeyEvent methods is insufficient.

Under MSW, the raw key code is the value of `wParam` parameter of the corresponding message.

Under GTK, the raw key code is the `keyval` field of the corresponding GDK event.

Under macOS, the raw key code is the `keyCode` field of the corresponding NSEvent.

Note
  Currently the raw key codes are not supported by all ports, use #ifdef wxHAS_RAW_KEY_CODES to determine if this feature is available.

## ◆ GetRawKeyFlags()

wxUint32 wxKeyEvent::GetRawKeyFlags | ( |  | ) | const

Returns the low level key flags for this event.

The flags are platform-dependent and should only be used if the functionality provided by other wxKeyEvent methods is insufficient.

Under MSW, the raw flags are just the value of `lParam` parameter of the corresponding message.

Under GTK, the raw flags contain the `hardware_keycode` field of the corresponding GDK event.

Under macOS, the raw flags contain the modifiers state.

Note
  Currently the raw key flags are not supported by all ports, use #ifdef wxHAS_RAW_KEY_CODES to determine if this feature is available.

## ◆ GetUnicodeKey()

wxChar wxKeyEvent::GetUnicodeKey | ( |  | ) | const

Returns the Unicode character corresponding to this key event.

If the key pressed doesn't have any character value (e.g. a cursor key) this method will return `WXK_NONE`. In this case you should use GetKeyCode() to retrieve the value of the key.

## ◆ GetX()

wxCoord wxKeyEvent::GetX | ( |  | ) | const

Returns the X position (in client coordinates) of the event.

See also
  GetPosition()

## ◆ GetY()

wxCoord wxKeyEvent::GetY | ( |  | ) | const

Returns the Y position (in client coordinates) of the event.

See also
  GetPosition()

## ◆ IsAutoRepeat()

bool wxKeyEvent::IsAutoRepeat | ( |  | ) | const

Returns true if this event is an auto-repeat of the key, false if this is the initial key press.

Since
  3.1.6
  Availability: only available for the wxOSX/Cocoa, wxMSW, wxQt ports.

## ◆ IsKeyInCategory()

bool wxKeyEvent::IsKeyInCategory | ( | int | category | ) | const

Returns true if the key is in the given key category.

Parameters

  category | A bitwise combination of named wxKeyCategoryFlags constants.

Since
  2.9.1

## ◆ IsNextEventAllowed()

bool wxKeyEvent::IsNextEventAllowed | ( |  | ) | const

Returns true if DoAllowNextEvent() had been called, false by default.

This method is used by wxWidgets itself to determine whether the normal key events should be generated after `wxEVT_CHAR_HOOK` processing.

Since
  2.9.3