render <TH> contents in bold, as all the browsers do

[wxWidgets.git] / docs / doxygen / overviews / eventhandling.h

diff --git a/docs/doxygen/overviews/eventhandling.h b/docs/doxygen/overviews/eventhandling.h
index 0e4c7f2392cd26e1b9783efed49a43c0c3091c59..de7ba6137495bbdbae47b69676068009563cd73f 100644 (file)
--- a/docs/doxygen/overviews/eventhandling.h
+++ b/docs/doxygen/overviews/eventhandling.h
@@ -7,9 +7,10 @@
 /////////////////////////////////////////////////////////////////////////////\r
 \r
 /**\r
-    @page overview_events Events and Event Handling\r
 \r
-    Related classes: wxEvtHandler, wxWindow, wxEvent\r
+@page overview_events Events and Event Handling\r
+\r
+Related classes: wxEvtHandler, wxWindow, wxEvent\r
 \r
 @li @ref overview_events_introduction\r
 @li @ref overview_events_eventhandling\r
@@ -440,32 +441,10 @@ or unset this flag for the dialogs that have it on by default.
 Typically events that deal with a window as a window (size, motion,\r
 paint, mouse, keyboard, etc.) are sent only to the window.  Events\r
 that have a higher level of meaning or are generated by the window\r
-itself, (button click, menu select, tree expand, etc.) are command\r
+itself (button click, menu select, tree expand, etc.) are command\r
 events and are sent up to the parent to see if it is interested in the event.\r
-\r
-As mentioned above, only command events are recursively applied to the parents\r
-event handler in the library itself. As this quite often causes confusion for\r
-users, here is a list of system events that will @em not get sent to the\r
-parent's event handler:\r
-\r
-@li wxEvent: The event base class\r
-@li wxActivateEvent: A window or application activation event\r
-@li wxCloseEvent: A close window or end session event\r
-@li wxEraseEvent: An erase background event\r
-@li wxFocusEvent: A window focus event\r
-@li wxKeyEvent: A keypress event\r
-@li wxIdleEvent: An idle event\r
-@li wxInitDialogEvent: A dialog initialisation event\r
-@li wxJoystickEvent: A joystick event\r
-@li wxMenuEvent: A menu event\r
-@li wxMouseEvent: A mouse event\r
-@li wxMoveEvent: A move event\r
-@li wxPaintEvent: A paint event\r
-@li wxQueryLayoutInfoEvent: Used to query layout information\r
-@li wxSetCursorEvent: Used for special cursor processing based on current mouse position\r
-@li wxSizeEvent: A size event\r
-@li wxScrollWinEvent: A scroll event sent by a scrolled window (not a scroll bar)\r
-@li wxSysColourChangedEvent: A system colour change event\r
+More precisely, as said above, all event classes @b not deriving from wxCommandEvent\r
+(see the wxEvent inheritance map) do @b not propagate upward.\r
 \r
 In some cases, it might be desired by the programmer to get a certain number\r
 of system events in a parent window, for example all key events sent to, but not\r
@@ -762,7 +741,7 @@ your identifiers don't conflict accidentally.
 \r
 \r
 \r
-@subsection overview_events_macros Event Handling Summary\r
+@subsection overview_events_list List of wxWidgets events\r
 \r
 For the full list of event classes, please see the\r
 @ref group_class_events "event classes group page".\r