wxTextCtrl::OnChar() can't be used to translate the key strokes in the text control

git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@15658 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Vadim Zeitlin
2002-05-24 21:31:43 +00:00
parent dcbd3aed96
commit d2d50a41fc

View File

@@ -581,33 +581,35 @@ Loads and displays the named file, if it exists.
{\tt TRUE} if successful, {\tt FALSE} otherwise. {\tt TRUE} if successful, {\tt FALSE} otherwise.
\membersection{wxTextCtrl::OnChar}\label{wxtextctrlonchar} % VZ: commenting this out as: (a) the docs are wrong (you can't replace
% anything), (b) wxTextCtrl doesn't have any OnChar() anyhow
\func{void}{OnChar}{\param{wxKeyEvent\& }{event}} %% \membersection{wxTextCtrl::OnChar}\label{wxtextctrlonchar}
%%
Default handler for character input. %% \func{void}{OnChar}{\param{wxKeyEvent\& }{event}}
%%
\wxheading{Remarks} %% Default handler for character input.
%%
It is possible to intercept character %% \wxheading{Remarks}
input by overriding this member. Call this function %%
to let the default behaviour take place; not calling %% It is possible to intercept character
it results in the character being ignored. You can %% input by overriding this member. Call this function
replace the {\it keyCode} member of {\it event} to %% to let the default behaviour take place; not calling
translate keystrokes. %% it results in the character being ignored. You can
%% replace the {\it keyCode} member of {\it event} to
Note that Windows and Motif have different ways %% translate keystrokes.
of implementing the default behaviour. In Windows, %%
calling wxTextCtrl::OnChar immediately %% Note that Windows and Motif have different ways
processes the character. In Motif, %% of implementing the default behaviour. In Windows,
calling this function simply sets a flag %% calling wxTextCtrl::OnChar immediately
to let default processing happen. This might affect %% processes the character. In Motif,
the way in which you write your OnChar function %% calling this function simply sets a flag
on different platforms. %% to let default processing happen. This might affect
%% the way in which you write your OnChar function
\wxheading{See also} %% on different platforms.
%%
\helpref{wxKeyEvent}{wxkeyevent} %% \wxheading{See also}
%%
%% \helpref{wxKeyEvent}{wxkeyevent}
\membersection{wxTextCtrl::OnDropFiles}\label{wxtextctrlondropfiles} \membersection{wxTextCtrl::OnDropFiles}\label{wxtextctrlondropfiles}