documented wxInitialize and wxUnitialize

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

diff --git a/docs/latex/wx/evthand.tex b/docs/latex/wx/evthand.tex
index 79bec646481c4c3ccdeba4642d656358043b86a0..cc269395f3c522414ddde35ea326fc9e8bdd2881 100644 (file)
--- a/docs/latex/wx/evthand.tex
+++ b/docs/latex/wx/evthand.tex
@@ -37,7 +37,7 @@ each other.
 \func{virtual void}{AddPendingEvent}{\param{wxEvent\& }{event}}
 
 Adds an event to be processed later. The function will return immediately and the
-event will get processed in idle time using the \helpref{wxEvtHandler::ProcessEvent}{wxevthandlerprocessevent}
+event will get processed in idle time using the \helpref{wxEvtHandler::ProcessEvent}{wxevthandlerprocessevent} 
 method.
 
 \wxheading{Parameters}
@@ -46,9 +46,10 @@ method.
 
 \wxheading{Remarks}
 
-Note that this requires that the event has a fully implemented Clone()
+Note that this requires that the event implements 
+\helpref{CopyObject}{wxobjectcopyobject} 
 method so that the event can be duplicated and stored until it gets processed later.
-Not all events in wxWindows currently have a fully implemented Clone() method,
+Not all events in wxWindows currently fully implement this method,
 so you may have to look at the source to verify this.
 
 This methods automatically wakes up idle handling even if the underlying window 
@@ -61,6 +62,7 @@ about the status of other working threads and this has to be done using this
 method - which also means that this method is thread safe by means of using
 crtical sections where needed.
 
+% VZ: bad idea IMHO - we're going to have a lot of problems with this
 Furthermore, it may be noted that some ports of wxWindows will probably move
 to using this method more and more in preference over calling ProcessEvent()
 directly so as to avoid problems with reentrant code.