Headers moved a bit.

Minor docs updates.


git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@4654 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775

docs/latex/wx/tconfig.tex

@@ -1,4 +1,4 @@
-\section{Config classes overview}\label{wxconfigoverview}
+\section{wxConfig classes overview}\label{wxconfigoverview}
 
 Classes: \helpref{wxConfig}{wxconfigbase}
 

docs/latex/wx/topics.tex

@@ -8,13 +8,7 @@ This chapter contains a selection of topic overviews, first things first:
 \input tguide.tex
 \input hworld.tex
 \input tsamples.tex
-
-Every application need one wxApp class, so we start here:
-
 \input tapp.tex
-
-Not everything in wxWindows is about GUI programming:
-
 \input truntime.tex
 \input tstring.tex
 \input tunicode.tex
@@ -27,9 +21,6 @@ Not everything in wxWindows is about GUI programming:
 \input tconfig.tex
 \input texpr.tex
 \input fs.tex
-
-General overviews concerning windows and events:
-
 \input tevent.tex
 \input tstyles.tex
 \input tdelwin.tex
@@ -38,16 +29,10 @@ General overviews concerning windows and events:
 \input tconstr.tex
 \input tresourc.tex
 \input tscroll.tex
-
-Drawing and device context specific overviews:
-
 \input tbitmap.tex
 \input tdc.tex
 \input tfont.tex
 \input tfontenc.tex
-
-Special controls:
-
 \input tsplittr.tex
 \input ttreectl.tex
 \input tlistctl.tex
@@ -58,9 +43,6 @@ Special controls:
 \input ttoolbar.tex
 \input tgrid.tex
 \input ttips.tex
-
-Advanced topic overviews:
-
 \input tprint.tex
 \input tthreads.tex
 \input tdnd.tex

docs/latex/wx/tstream.tex

@@ -1,4 +1,4 @@
-\section{Streams in wxWindows overview}\label{wxstreamoverview}
+\section{wxStreams overview}\label{wxstreamoverview}
 
 Classes: \helpref{wxStreamBase}{wxstreambase},
  \helpref{wxStreamBuffer}{wxstreambuffer}, \helpref{wxInputStream}{wxinputstream},
@@ -62,13 +62,13 @@ code:
 
  // Ok, read some bytes ... nb_datas is expressed in bytes.
  in_stream.Read(data, nb_datas);
- if (in_stream.LastError() != wxStream_NOERROR) {
+ if (in_stream.LastError() != wxSTREAM_NOERROR) {
    // Oh oh, something bad happens.
    // For a complete list, look into the documentation at wxStreamBase.
  }
 
  // You can also inline all like this.
- if (in_stream.Read(data, nb_datas).LastError() != wxStream_NOERROR) {
+ if (in_stream.Read(data, nb_datas).LastError() != wxSTREAM_NOERROR) {
    // Do something.
  }
 

docs/latex/wx/tthreads.tex

@@ -34,10 +34,10 @@ 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).
 
-Final note: in the current release of wxWindows, there are no specific
-facilities for communicating between the threads. However, the usual 
-\helpref{ProcessEvent()}{wxevthandlerprocessevent} function may be used for
-thread communication too - but you should provide your own synchronisation
-mechanism if you use it (e.g. just use a critical section before sending a
-message) because there is no built-in synchronisation.
+For communication between threads, use 
+\helpref{wxEvtHandler::AddPendingEvent}{wxevthandleraddpendingprocessevent}
+or its short version \helpref{wxPostEvent}{wxpostevent}. These functions
+have thread safe implementation so that they can be used as they are for
+sending event from one thread to another.
+