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

no changes, just some markup fixes

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@55788 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Vadim Zeitlin
2008-09-22 00:49:34 +00:00
parent 92089d00a1
commit 4eda9c09e4
1 changed files with 8 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
docs/doxygen/overviews/eventhandling.h
View File

@@ -272,11 +272,12 @@ Now let us describe the semantic differences:
NULL, // unused extra data parameter NULL, // unused extra data parameter
this); // this indicates the object to connect to this); // this indicates the object to connect to
} }
@endcode will work exactly as expected. Note that you can get the @endcode
object which generated the event -- and which is not the same as the will work exactly as expected. Note that you can get the object which
frame -- via wxEvent::GetEventObject() method of @c event argument generated the event -- and which is not the same as the frame -- via
passed to the event handler. wxEvent::GetEventObject() method of @c event argument passed to the
<li> event handler.
</li>
</ul> </ul>
To summarize, using Connect() requires slightly more typing but is much more To summarize, using Connect() requires slightly more typing but is much more
@@ -296,7 +297,7 @@ wxEvtHandler::ProcessEvent() on the first event handler object belonging to the
window generating the event. The normal order of event table searching by window generating the event. The normal order of event table searching by
ProcessEvent() is as follows, with the event processing stopping as soon as a ProcessEvent() is as follows, with the event processing stopping as soon as a
handler is found (unless the handler calls wxEvent::Skip() in which case it handler is found (unless the handler calls wxEvent::Skip() in which case it
doesn't count as having handled the event): doesn't count as having handled the event and the search continues):
<ol> <ol>
<li value="0"> <li value="0">
Before anything else happens, wxApp::FilterEvent() is called. If it returns Before anything else happens, wxApp::FilterEvent() is called. If it returns
@@ -350,7 +351,7 @@ doesn't count as having handled the event):
</li> </li>
</ol> </ol>
<em>Please pay close attention to step 6!</em>. People often overlook or get <em>Please pay close attention to step 6!</em> People often overlook or get
confused by this powerful feature of the wxWidgets event processing system. The confused by this powerful feature of the wxWidgets event processing system. The
details of event propagation upwards the window hierarchy are described in the details of event propagation upwards the window hierarchy are described in the
next section. next section.