Patches-1851591 ] dataview sample is crashing (under MSW)

[wxWidgets.git] / docs / latex / wx / tevent.tex

diff --git a/docs/latex/wx/tevent.tex b/docs/latex/wx/tevent.tex
index c70048d0b98180f671ca5383bcae8d3d4a69e8b4..084173279101c20be37b019be1eb1b672b85eeaf 100644 (file)
--- a/docs/latex/wx/tevent.tex
+++ b/docs/latex/wx/tevent.tex
@@ -268,9 +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 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
-handle events from instances of different 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
 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.
@@ -544,13 +544,13 @@ public:
         { return m_curve; }
 
     // required for sending with wxPostEvent()
-    wxEvent* Clone();
+    virtual wxEvent *Clone() const;
 
 private:
     wxPlotCurve   *m_curve;
 };
 
-DECLARE_EVENT_MACRO( wxEVT_PLOT_ACTION, -1 )
+DECLARE_EVENT_TYPE( wxEVT_PLOT_ACTION, -1 )
 
 typedef void (wxEvtHandler::*wxPlotEventFunction)(wxPlotEvent&);