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

Another typo. I should really wake up before writing...

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/branches/WX_2_8_BRANCH@49227 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Robin Dunn
2007-10-18 16:14:50 +00:00
parent 6275bcf28d
commit e388b63f0d
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/latex/wx/tevent.tex
View File

@@ -268,7 +268,7 @@ defining the appropriate event table, and then call
\rtfsp\helpref{wxWindow::SetEventHandler}{wxwindowseteventhandler} (or, preferably, \rtfsp\helpref{wxWindow::SetEventHandler}{wxwindowseteventhandler} (or, preferably,
\rtfsp\helpref{wxWindow::PushEventHandler}{wxwindowpusheventhandler}) to make this \rtfsp\helpref{wxWindow::PushEventHandler}{wxwindowpusheventhandler}) to make this
event handler the object that responds to events. This way, you can avoid event handler the object that responds to events. This way, you can avoid
a lot of class derivation, and use use instances of the same event handler class (but different a lot of class derivation, and use instances of the same event handler class (but different
objects as the same event handler object shouldn't be used more than once) to objects as the same event handler object shouldn't be used more than once) to
handle events from instances of different widget classes. If you ever have to call a window's event handler handle events from instances of different widget classes. If you ever have to call a window's event handler
manually, use the GetEventHandler function to retrieve the window's event handler and use that manually, use the GetEventHandler function to retrieve the window's event handler and use that