From 86f87473ea411e35a1a242152c286470d60f8b51 Mon Sep 17 00:00:00 2001 From: Robin Dunn Date: Thu, 18 Oct 2007 15:47:59 +0000 Subject: [PATCH] Make event overview doc more clear about instances of wxEvtHandler git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/branches/WX_2_8_BRANCH@49223 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775 --- docs/latex/wx/tevent.tex | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/latex/wx/tevent.tex b/docs/latex/wx/tevent.tex index 13a94c1fed..c5e43c4197 100644 --- a/docs/latex/wx/tevent.tex +++ b/docs/latex/wx/tevent.tex @@ -268,8 +268,9 @@ defining the appropriate event table, and then call \rtfsp\helpref{wxWindow::SetEventHandler}{wxwindowseteventhandler} (or, preferably, \rtfsp\helpref{wxWindow::PushEventHandler}{wxwindowpusheventhandler}) to make this event handler the object that responds to events. This way, you can avoid -a lot of class derivation, and use the same event handler object to -handle events from instances of different classes. If you ever have to call a window's event handler +a lot of class derivation, and use use instnaces of the same event handler class (but different +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 manually, use the GetEventHandler function to retrieve the window's event handler and use that to call the member function. By default, GetEventHandler returns a pointer to the window itself unless an application has redirected event handling using SetEventHandler or PushEventHandler.