Amebis/wxWidgets
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

clarify Skip() meaning even more (latest version of patch 1516341)

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@42251 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Vadim Zeitlin
2006-10-22 20:52:45 +00:00
parent f8b35b7b9a
commit 16844d1c3a
1 changed files with 6 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
docs/latex/wx/event.tex
View File

@@ -172,14 +172,12 @@ is currently greater than $0$.
\func{void}{Skip}{\param{bool}{ skip = true}} \func{void}{Skip}{\param{bool}{ skip = true}}
This method can be called by an event handler and controls whether additional 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 event event handlers bound to this event will be called after the current one
handler returns. The default behavior is equivalent to calling Skip(false) returns. Without Skip() (or equivalently if Skip(false) is used),
(which is, hence, usually unnecessary) and will prevent additional event the event will not be processed any more. If Skip(true) is called, the event
handlers from being called and control will be returned to the sender of the processing system continues searching for a further handler function for this
event immediately after the current handler has finished. If Skip(true) is event, even though it has been processed already in the current handler.
called, the event processing system continues searching for a handler
function for this event as if the current handler didn't exist.
In general, it is recommended to skip all non-command events to allow the 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 default handling to take place. The command events are, however, normally not