wxWindowMSW now eats EVT_CHAR if the key was handled in EVT_KEY_DOWN

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

diff --git a/docs/latex/wx/critsect.tex b/docs/latex/wx/critsect.tex
index 2bc984a0779ab92c896b9c459d10193b399327da..d2c67ee3dfbcc8153ef50ee65c9ab2d6fdd74808 100644 (file)
--- a/docs/latex/wx/critsect.tex
+++ b/docs/latex/wx/critsect.tex
@@ -1,7 +1,7 @@
 \section{\class{wxCriticalSection}}\label{wxcriticalsection}
 
 \section{\class{wxCriticalSection}}\label{wxcriticalsection}
 

-A critical section object is used exactly for the same purpose as 
-\helpref{mutexes}{wxMutex}. The only difference is that under Windows platform
+A critical section object is used for the same exactly purpose as 
+\helpref{mutexes}{wxmutex}. The only difference is that under Windows platform

 critical sections are only visible inside one process, while mutexes may be
 shared between processes, so using critical sections is slightly more
 efficient. The terminology is also slightly different: mutex may be locked (or
 critical sections are only visible inside one process, while mutexes may be
 shared between processes, so using critical sections is slightly more
 efficient. The terminology is also slightly different: mutex may be locked (or


@@ -18,6 +18,10 @@ possible instead of directly using wxCriticalSection for the same reasons
 
 None.
 
 
 None.
 

+\wxheading{Include files}
+
+<wx/thread.h>
+

 \wxheading{See also}
 
 \helpref{wxThread}{wxthread}, \helpref{wxCondition}{wxcondition}, 
 \wxheading{See also}
 
 \helpref{wxThread}{wxthread}, \helpref{wxCondition}{wxcondition},