Fix manual references to the events overview after it's page ID was changed in r58712 (VZ).

git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@58978 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775

docs/doxygen/groups/class_events.h

@@ -14,7 +14,7 @@
 An event object contains information about a specific event. Event handlers
 (usually member functions) have a single, event argument.
 
-Related Overviews: @ref overview_eventhandling
+Related Overviews: @ref overview_events
 
 Related macros/global-functions group: @ref group_funcmacro_events
 

docs/doxygen/mainpages/cat_classes.h

@@ -406,7 +406,7 @@ Related Overviews: @ref overview_bitmap
 An event object contains information about a specific event. Event handlers
 (usually member functions) have a single, event argument.
 
-Related Overviews: @ref overview_eventhandling
+Related Overviews: @ref overview_events
 
 @li wxActivateEvent: A window or application activation event
 @li wxCalendarEvent: Used with wxCalendarCtrl

docs/doxygen/overviews/eventhandling.h

@@ -7,6 +7,7 @@
 /////////////////////////////////////////////////////////////////////////////
 
 /**
+
 @page overview_events Events and Event Handling
 
 Related classes: wxEvtHandler, wxWindow, wxEvent

docs/doxygen/overviews/validator.h

@@ -90,7 +90,7 @@ internally.
 
 You can optionally define event handlers for the validator, to implement
 filtering. These handlers will capture events before the control itself does
-(see @ref overview_eventhandling_processing).
+(see @ref overview_events_processing).
 For an example implementation, see the @c valtext.h and @c valtext.cpp files in the
 wxWidgets library.
 

interface/wx/event.h

@@ -455,7 +455,7 @@ public:
            function was found, in which case the function exits.
         -# The search is applied down the entire chain of event handlers (usually the
            chain has a length of one). This chain can be formed using wxEvtHandler::SetNextHandler():
-              @image html overview_eventhandling_chain.png
+              @image html overview_events_chain.png
            (referring to the image, if @c A->ProcessEvent is called and it doesn't handle
             the event, @c B->ProcessEvent will be called and so on...).
            Note that in the case of wxWindow you can build a stack of event handlers

interface/wx/laywin.h

@@ -106,7 +106,7 @@ enum wxLayoutAlignment
     @library{wxadv}
     @category{winlayout}
 
-    @see wxSashEvent, wxSashLayoutWindow, @ref overview_eventhandling
+    @see wxSashEvent, wxSashLayoutWindow, @ref overview_events
 */
 class wxLayoutAlgorithm : public wxObject
 {
@@ -169,7 +169,7 @@ public:
     @library{wxadv}
     @category{miscwnd}
 
-    @see wxLayoutAlgorithm, wxSashWindow, @ref overview_eventhandling
+    @see wxLayoutAlgorithm, wxSashWindow, @ref overview_events
 */
 class wxSashLayoutWindow : public wxSashWindow
 {

interface/wx/process.h

@@ -270,7 +270,7 @@ public:
     @library{wxbase}
     @category{events}
 
-    @see wxProcess, @ref overview_eventhandling
+    @see wxProcess, @ref overview_events
 */
 class wxProcessEvent : public wxEvent
 {

interface/wx/radiobox.h

@@ -34,7 +34,7 @@
     @category{ctrl}
     @appearance{radiobox.png}
 
-    @see @ref overview_eventhandling, wxRadioButton, wxCheckBox
+    @see @ref overview_events, wxRadioButton, wxCheckBox
 */
 class wxRadioBox : public wxControl, wxItemContainerImmutable
 {

interface/wx/radiobut.h

@@ -40,7 +40,7 @@
     @category{ctrl}
     @appearance{radiobutton.png}
 
-    @see @ref overview_eventhandling, wxRadioBox, wxCheckBox
+    @see @ref overview_events, wxRadioBox, wxCheckBox
 */
 class wxRadioButton : public wxControl
 {

interface/wx/sashwin.h

@@ -63,7 +63,7 @@ enum wxSashDragStatus
     @library{wxadv}
     @category{miscwnd}
 
-    @see wxSashEvent, wxSashLayoutWindow, @ref overview_eventhandling
+    @see wxSashEvent, wxSashLayoutWindow, @ref overview_events
 */
 class wxSashWindow : public wxWindow
 {
@@ -222,7 +222,7 @@ public:
     @library{wxadv}
     @category{events}
 
-    @see wxSashWindow, @ref overview_eventhandling
+    @see wxSashWindow, @ref overview_events
 */
 class wxSashEvent : public wxCommandEvent
 {

interface/wx/scrolbar.h

@@ -107,7 +107,7 @@
     @category{ctrl}
     @appearance{scrollbar.png}
 
-    @see @ref overview_scrolling, @ref overview_eventhandling, wxScrolled
+    @see @ref overview_scrolling, @ref overview_events, wxScrolled
 */
 class wxScrollBar : public wxControl
 {

interface/wx/slider.h

@@ -107,7 +107,7 @@
     @category{ctrl}
     @appearance{slider.png}
 
-    @see @ref overview_eventhandling, wxScrollBar
+    @see @ref overview_events, wxScrollBar
 */
 class wxSlider : public wxControl
 {

interface/wx/splitter.h

@@ -423,7 +423,7 @@ public:
     @library{wxcore}
     @category{events}
 
-    @see wxSplitterWindow, @ref overview_eventhandling
+    @see wxSplitterWindow, @ref overview_events
 */
 class wxSplitterEvent : public wxNotifyEvent
 {

interface/wx/window.h

@@ -1702,7 +1702,7 @@ public:
         Removes and returns the top-most event handler on the event handler stack.
 
         E.g. in the case of:
-            @image html overview_eventhandling_winstack.png
+            @image html overview_events_winstack.png
         when calling @c W->PopEventHandler(), the event handler @c A will be
         removed and @c B will be the first handler of the stack.
 
@@ -1737,7 +1737,7 @@ public:
             W->PushEventHandler(B);
         @endcode
         you will end up with the following situation:
-            @image html overview_eventhandling_winstack.png
+            @image html overview_events_winstack.png
 
         Note that you can use wxWindow::PopEventHandler to remove the event handler.