X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/12c9c01c2420f56b146cf998e6e58b9f695e2ae3..5852e62f1fe76907832ba2c7f2b4099635e44c4b:/docs/doxygen/overviews/eventhandling.h diff --git a/docs/doxygen/overviews/eventhandling.h b/docs/doxygen/overviews/eventhandling.h index be1365eed3..0c78592351 100644 --- a/docs/doxygen/overviews/eventhandling.h +++ b/docs/doxygen/overviews/eventhandling.h @@ -221,6 +221,8 @@ events. @subsection overview_events_bind Dynamic Event Handling +@see @ref overview_cpp_rtti_disabled + The possibilities of handling events in this way are rather different. Let us start by looking at the syntax: the first obvious difference is that you need not use DECLARE_EVENT_TABLE() nor BEGIN_EVENT_TABLE() and the @@ -428,7 +430,10 @@ in simple situations where this extra flexibility is not needed. The previous sections explain how to define event handlers but don't address the question of how exactly wxWidgets finds the handler to call for the -given event. This section describes the algorithm used in detail. +given event. This section describes the algorithm used in detail. Notice that +you may want to run the @ref page_samples_event while reading this section and +look at its code and the output when the button which can be used to test the +event handlers execution order is clicked to understand it better. When an event is received from the windowing system, wxWidgets calls wxEvtHandler::ProcessEvent() on the first event handler object belonging to the @@ -454,11 +459,11 @@ doesn't count as having handled the event and the search continues):
  • - The list of dynamically bind event handlers, i.e., those for which + The list of dynamically bound event handlers, i.e., those for which Bind<>() was called, is consulted. Notice that this is done before checking the static event table entries, so if both a dynamic and a static event handler match the same event, the static one is never going to be - used. + used unless wxEvent::Skip() is called in the dynamic one.