X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/1185254d55900be4585c9454f00d311ab465c29b..78cb09ec439962b53ba75fef814b9a3871412287:/docs/latex/wx/event.tex

diff --git a/docs/latex/wx/event.tex b/docs/latex/wx/event.tex
index 5e10db1209..84c54107ca 100644
--- a/docs/latex/wx/event.tex
+++ b/docs/latex/wx/event.tex
@@ -17,6 +17,10 @@ For more information about events, see the \helpref{Event handling overview}{eve
 
 <wx/event.h>
 
+\wxheading{Library}
+
+\helpref{wxBase}{librarieslist}
+
 \wxheading{See also}
 
 \helpref{wxCommandEvent}{wxcommandevent},\rtfsp
@@ -172,13 +176,17 @@ is currently greater than $0$.
 
 \func{void}{Skip}{\param{bool}{ skip = true}}
 
-Called by an event handler, it controls whether additional event
-handlers bound to this event will be called after the current event
-handler returns.  Skip(false) (the default behavior) will prevent
-additional event handlers from being called and control will be
-returned to the sender of the event immediately after the current
-handler has finished.  Skip(true) will cause the event processing
-system to continue searching for a handler function for this event.
+This method can be used inside an event handler to control whether further
+event handlers bound to this event will be called after the current one
+returns. Without Skip() (or equivalently if Skip(false) is used),
+the event will not be processed any more. If Skip(true) is called, the event
+processing system continues searching for a further handler function for this
+event, even though it has been processed already in the current handler.
+
+In general, it is recommended to skip all non-command events to allow the
+default handling to take place. The command events are, however, normally not
+skipped as usually a single command such as a button click or menu item
+selection must only be processed by one handler.
 
 
 \membersection{wxEvent::StopPropagation}\label{wxeventstoppropagation}