name wxThreadEvent and YieldFor in wxProgressDialog and in thread overview; update the sample code to use new event macros; minor other changes
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@59002 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
@@ -441,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,
|
||||
paint, mouse, keyboard, etc.) are sent only to the window. Events
|
||||
that have a higher level of meaning or are generated by the window
|
||||
itself, (button click, menu select, tree expand, etc.) are command
|
||||
itself (button click, menu select, tree expand, etc.) are command
|
||||
events and are sent up to the parent to see if it is interested in the event.
|
||||
|
||||
As mentioned above, only command events are recursively applied to the parents
|
||||
event handler in the library itself. As this quite often causes confusion for
|
||||
users, here is a list of system events that will @em not get sent to the
|
||||
parent's event handler:
|
||||
|
||||
@li wxEvent: The event base class
|
||||
@li wxActivateEvent: A window or application activation event
|
||||
@li wxCloseEvent: A close window or end session event
|
||||
@li wxEraseEvent: An erase background event
|
||||
@li wxFocusEvent: A window focus event
|
||||
@li wxKeyEvent: A keypress event
|
||||
@li wxIdleEvent: An idle event
|
||||
@li wxInitDialogEvent: A dialog initialisation event
|
||||
@li wxJoystickEvent: A joystick event
|
||||
@li wxMenuEvent: A menu event
|
||||
@li wxMouseEvent: A mouse event
|
||||
@li wxMoveEvent: A move event
|
||||
@li wxPaintEvent: A paint event
|
||||
@li wxQueryLayoutInfoEvent: Used to query layout information
|
||||
@li wxSetCursorEvent: Used for special cursor processing based on current mouse position
|
||||
@li wxSizeEvent: A size event
|
||||
@li wxScrollWinEvent: A scroll event sent by a scrolled window (not a scroll bar)
|
||||
@li wxSysColourChangedEvent: A system colour change event
|
||||
More precisely, as said above, all event classes @b not deriving from wxCommandEvent
|
||||
(see the wxEvent inheritance map) do @b not propagate upward.
|
||||
|
||||
In some cases, it might be desired by the programmer to get a certain number
|
||||
of system events in a parent window, for example all key events sent to, but not
|
||||
@@ -763,7 +741,7 @@ your identifiers don't conflict accidentally.
|
||||
|
||||
|
||||
|
||||
@subsection overview_events_macros Event Handling Summary
|
||||
@subsection overview_events_list List of wxWidgets events
|
||||
|
||||
For the full list of event classes, please see the
|
||||
@ref group_class_events "event classes group page".
|
||||
|
Reference in New Issue
Block a user