always define wxUSE_RICHEDIT[2] -- this is better than never defining them (closes...

[wxWidgets.git] / docs / doxygen / overviews / thread.h

diff --git a/docs/doxygen/overviews/thread.h b/docs/doxygen/overviews/thread.h
index 37b6d2ae3036eafedaf86a3d3fe89fe0d875824d..27344955838e6dfc83cf31480ffd64c41bc3fa02 100644 (file)
--- a/docs/doxygen/overviews/thread.h
+++ b/docs/doxygen/overviews/thread.h
@@ -45,7 +45,7 @@ Win32 a thread can only access GDI objects such as pens, brushes, c created by
 itself and not by the other threads).
 
 For communication between secondary threads and the main thread, you may use
 itself and not by the other threads).
 
 For communication between secondary threads and the main thread, you may use

-wxEvtHandler::AddPendingEvent or its short version wxPostEvent. These functions
+wxEvtHandler::QueueEvent or its short version ::wxQueueEvent. These functions

 have a thread-safe implementation so that they can be used as they are for
 sending events from one thread to another. However there is no built in method
 to send messages to the worker threads and you will need to use the available
 have a thread-safe implementation so that they can be used as they are for
 sending events from one thread to another. However there is no built in method
 to send messages to the worker threads and you will need to use the available