Amebis/wxWidgets
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix and update the note about handling EVT_KEY_DOWN preventing

Browse Source 
EVT_CHAR from being sent.


git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@15746 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Robin Dunn
2002-06-04 19:27:33 +00:00
parent c13219d6a8
commit af79fc6f08
1 changed files with 6 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
docs/latex/wx/keyevent.tex
View File

@@ -17,11 +17,6 @@ from the \helpref{keycodes table}{keycodes}. The translated key is, in
general, the character the user expects to appear as the result of the key general, the character the user expects to appear as the result of the key
combination when typing the text into a text entry zone, for example. combination when typing the text into a text entry zone, for example.
If the key up event is caught and the event handler does not call
event.Skip() then the coresponding char event will not happen. This
is by design and enables the programs that handle both types of events
to be a bit simpler.
A few examples to clarify this (all assume that {\sc Caps Lock} is unpressed A few examples to clarify this (all assume that {\sc Caps Lock} is unpressed
and the standard US keyboard): when the {\tt 'A'} key is pressed, the key down and the standard US keyboard): when the {\tt 'A'} key is pressed, the key down
event key code is equal to {\tt ASCII A} $== 65$. But the char event key code event key code is equal to {\tt ASCII A} $== 65$. But the char event key code
@@ -45,6 +40,12 @@ You may discover how the other keys on your system behave interactively by
running the \helpref{text}{sampletext} wxWindows sample and pressing some keys running the \helpref{text}{sampletext} wxWindows sample and pressing some keys
in any of the text controls shown in it. in any of the text controls shown in it.
{\bf Note:} If a key down ({\tt EVT\_KEY\_DOWN}) event is caught and
the event handler does not call {\tt event.Skip()} then the coresponding
char event ({\tt EVT\_CHAR}) will not happen. This is by design and
enables the programs that handle both types of events to be a bit
simpler.
{\bf Note for Windows programmers:} The key and char events in wxWindows are {\bf Note for Windows programmers:} The key and char events in wxWindows are
similar to but slightly different from Windows {\tt WM\_KEYDOWN} and similar to but slightly different from Windows {\tt WM\_KEYDOWN} and
{\tt WM\_CHAR} events. In particular, Alt-x combination will generate a char {\tt WM\_CHAR} events. In particular, Alt-x combination will generate a char