- A help event is sent when the user has requested
- context-sensitive help. This can either be caused by the
- application requesting context-sensitive help mode via
- wx.ContextHelp, or (on MS Windows) by the system generating a
- WM_HELP message when the user pressed F1 or clicked on the query
- button in a dialog caption.
-
- A help event is sent to the window that the user clicked on, and
- is propagated up the window hierarchy until the event is
- processed or there are no more event handlers. The application
- should call event.GetId to check the identity of the clicked-on
- window, and then either show some suitable help or call
- event.Skip if the identifier is unrecognised. Calling Skip is
- important because it allows wxWindows to generate further events
- for ancestors of the clicked-on window. Otherwise it would be
- impossible to show help for container windows, since processing
- would stop after the first window found.
-
- Events
- EVT_HELP Sent when the user has requested context-
- sensitive help.
- EVT_HELP_RANGE Allows to catch EVT_HELP for a range of IDs
-
+ A help event is sent when the user has requested context-sensitive
+ help. This can either be caused by the application requesting
+ context-sensitive help mode via wx.ContextHelp, or (on MS Windows) by
+ the system generating a WM_HELP message when the user pressed F1 or
+ clicked on the query button in a dialog caption.
+
+ A help event is sent to the window that the user clicked on, and is
+ propagated up the window hierarchy until the event is processed or
+ there are no more event handlers. The application should call
+ event.GetId to check the identity of the clicked-on window, and then
+ either show some suitable help or call event.Skip if the identifier is
+ unrecognised. Calling Skip is important because it allows wxWindows to
+ generate further events for ancestors of the clicked-on
+ window. Otherwise it would be impossible to show help for container
+ windows, since processing would stop after the first window found.