another batch of topic overviews reviewing (letters e,f)

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

diff --git a/docs/doxygen/overviews/thread.h b/docs/doxygen/overviews/thread.h
index ee90ecf270e41dc761e4a4b07fec2005f98df130..15fe0a5d1804dfbae24472ad251ab7247a87b248 100644 (file)
--- a/docs/doxygen/overviews/thread.h
+++ b/docs/doxygen/overviews/thread.h
@@ -7,16 +7,16 @@
 /////////////////////////////////////////////////////////////////////////////
 
 /*!
- 
+
  @page thread_overview Multithreading overview
- 
- Classes: #wxThread, #wxMutex, 
- #wxCriticalSection, 
+
+ Classes: #wxThread, #wxMutex,
+ #wxCriticalSection,
  #wxCondition
  wxWidgets provides a complete set of classes encapsulating objects necessary in
  multithreaded (MT) programs: the #thread class itself and different
- synchronization objects: #mutexes and 
- @ref criticalsection_overview with 
+ synchronization objects: #mutexes and
+ @ref criticalsection_overview with
  #conditions. The thread API in wxWidgets resembles to
  POSIX1.c threads API (a.k.a. pthreads), although several functions have
  different names and some features inspired by Win32 thread API are there as
@@ -31,7 +31,7 @@
  new thread for each new client), but in others it might be a very poor choice
  (example: launching a separate thread when doing a long computation to show a
  progress dialog). Other implementation choices are available: for the progress
- dialog example it is far better to do the calculations in the 
+ dialog example it is far better to do the calculations in the
  @ref idleevent_overview or even simply do everything at once
  but call wxWindow::Update() periodically to update
  the screen.
@@ -44,7 +44,7 @@
  more robust and will undoubtedly save you countless problems (example: under
  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 
+ For communication between secondary threads and the main thread, you may use
  wxEvtHandler::AddPendingEvent
  or its short version #wxPostEvent. These functions
  have a thread-safe implementation so that they can be used as they are for
@@ -52,10 +52,10 @@
  to send messages to the worker threads and you will need to use the available
  synchronization classes to implement the solution which suits your needs
  yourself. In particular, please note that it is not enough to derive
- your class from #wxThread and 
+ your class from #wxThread and
  #wxEvtHandler to send messages to it: in fact, this does
  not work at all.
- 
+
  */
- 
- 
+
+