command events are not redirected to focused window

[wxWidgets.git] / docs / latex / wx / log.tex

diff --git a/docs/latex/wx/log.tex b/docs/latex/wx/log.tex
index 3c8d763200536ea7337cc5284c182bcbf214780d..6704cdd0a2695822e09ba8d415b2091e58e3dd08 100644 (file)
--- a/docs/latex/wx/log.tex
+++ b/docs/latex/wx/log.tex
@@ -62,13 +62,14 @@ without writing a new log target class (which, aside of being a matter of
 several minutes, allows you to do anything you want).
 
 The verbose messages are the trace messages which are not disabled in the
-release mode and are generated by \helpref{wxLogVerbose}{wxlogverbose}. They are not normally
-shown to the user because they present little interest, but may be activated,
-for example, in order to help the user find some program problem.
+release mode and are generated by \helpref{wxLogVerbose}{wxlogverbose}. They
+are not normally shown to the user because they present little interest, but
+may be activated, for example, in order to help the user find some program
+problem.
 
 As for the (real) trace messages, their handling depends on the settings of
 the (application global) {\it trace mask}. There are two ways to specify it:
-either by using helpref{SetTraceMask}{wxlogsettracemask} and 
+either by using \helpref{SetTraceMask}{wxlogsettracemask} and 
 \helpref{GetTraceMask}{wxloggettracemask} and using 
 \helpref{wxLogTrace}{wxlogtrace} which takes an integer mask or by using 
 \helpref{AddTraceMask}{wxlogaddtracemask} for string trace masks.
@@ -87,7 +88,7 @@ will do something only if the current trace mask contains both
 {\tt wxTraceRefCount} and {\tt wxTraceOle}, but
 \begin{verbatim}
 // wxTRACE_OleCalls is one of standard string masks
-wxLogTrace(wxTACE_OleCalls, "IFoo::Bar() called");
+wxLogTrace(wxTRACE_OleCalls, "IFoo::Bar() called");
 \end{verbatim}
 will log the message if it was preceded by
 \begin{verbatim}