1 /////////////////////////////////////////////////////////////////////////////
3 // Purpose: interface of wxEvtHandler, wxEventBlocker and many
4 // wxEvent-derived classes
5 // Author: wxWidgets team
7 // Licence: wxWindows licence
8 /////////////////////////////////////////////////////////////////////////////
13 The predefined constants for the number of times we propagate event
14 upwards window child-parent chain.
16 enum wxEventPropagation
18 /// don't propagate it at all
19 wxEVENT_PROPAGATE_NONE
= 0,
21 /// propagate it until it is processed
22 wxEVENT_PROPAGATE_MAX
= INT_MAX
26 The different categories for a wxEvent; see wxEvent::GetEventCategory.
28 @note They are used as OR-combinable flags by wxEventLoopBase::YieldFor.
33 This is the category for those events which are generated to update
34 the appearance of the GUI but which (usually) do not comport data
35 processing, i.e. which do not provide input or output data
36 (e.g. size events, scroll events, etc).
37 They are events NOT directly generated by the user's input devices.
39 wxEVT_CATEGORY_UI
= 1,
42 This category groups those events which are generated directly from the
43 user through input devices like mouse and keyboard and usually result in
44 data to be processed from the application
45 (e.g. mouse clicks, key presses, etc).
47 wxEVT_CATEGORY_USER_INPUT
= 2,
49 /// This category is for wxSocketEvent
50 wxEVT_CATEGORY_SOCKET
= 4,
52 /// This category is for wxTimerEvent
53 wxEVT_CATEGORY_TIMER
= 8,
56 This category is for any event used to send notifications from the
57 secondary threads to the main one or in general for notifications among
58 different threads (which may or may not be user-generated).
59 See e.g. wxThreadEvent.
61 wxEVT_CATEGORY_THREAD
= 16,
64 This mask is used in wxEventLoopBase::YieldFor to specify that all event
65 categories should be processed.
68 wxEVT_CATEGORY_UI
|wxEVT_CATEGORY_USER_INPUT
|wxEVT_CATEGORY_SOCKET
| \
69 wxEVT_CATEGORY_TIMER
|wxEVT_CATEGORY_THREAD
75 An event is a structure holding information about an event passed to a
76 callback or member function.
78 wxEvent used to be a multipurpose event object, and is an abstract base class
79 for other event classes (see below).
81 For more information about events, see the @ref overview_events overview.
84 In wxPerl custom event classes should be derived from
85 @c Wx::PlEvent and @c Wx::PlCommandEvent.
91 @see wxCommandEvent, wxMouseEvent
93 class wxEvent
: public wxObject
99 Notice that events are usually created by wxWidgets itself and creating
100 e.g. a wxPaintEvent in your code and sending it to e.g. a wxTextCtrl
101 will not usually affect it at all as native controls have no specific
102 knowledge about wxWidgets events. However you may construct objects of
103 specific types and pass them to wxEvtHandler::ProcessEvent() if you
104 want to create your own custom control and want to process its events
105 in the same manner as the standard ones.
107 Also please notice that the order of parameters in this constructor is
108 different from almost all the derived classes which specify the event
109 type as the first argument.
112 The identifier of the object (window, timer, ...) which generated
115 The unique type of event, e.g. @c wxEVT_PAINT, @c wxEVT_SIZE or
116 @c wxEVT_COMMAND_BUTTON_CLICKED.
118 wxEvent(int id
= 0, wxEventType eventType
= wxEVT_NULL
);
121 Returns a copy of the event.
123 Any event that is posted to the wxWidgets event system for later action
124 (via wxEvtHandler::AddPendingEvent, wxEvtHandler::QueueEvent or wxPostEvent())
125 must implement this method.
127 All wxWidgets events fully implement this method, but any derived events
128 implemented by the user should also implement this method just in case they
129 (or some event derived from them) are ever posted.
131 All wxWidgets events implement a copy constructor, so the easiest way of
132 implementing the Clone function is to implement a copy constructor for
133 a new event (call it MyEvent) and then define the Clone function like this:
136 wxEvent *Clone() const { return new MyEvent(*this); }
139 virtual wxEvent
* Clone() const = 0;
142 Returns the object (usually a window) associated with the event, if any.
144 wxObject
* GetEventObject() const;
147 Returns the identifier of the given event type, such as @c wxEVT_COMMAND_BUTTON_CLICKED.
149 wxEventType
GetEventType() const;
152 Returns a generic category for this event.
153 wxEvent implementation returns @c wxEVT_CATEGORY_UI by default.
155 This function is used to selectively process events in wxEventLoopBase::YieldFor.
157 virtual wxEventCategory
GetEventCategory() const;
160 Returns the identifier associated with this event, such as a button command id.
165 Return the user data associated with a dynamically connected event handler.
167 wxEvtHandler::Connect() and wxEvtHandler::Bind() allow associating
168 optional @c userData pointer with the handler and this method returns
169 the value of this pointer.
171 The returned pointer is owned by wxWidgets and must not be deleted.
175 wxObject
*GetEventUserData() const;
178 Returns @true if the event handler should be skipped, @false otherwise.
180 bool GetSkipped() const;
183 Gets the timestamp for the event. The timestamp is the time in milliseconds
184 since some fixed moment (not necessarily the standard Unix Epoch, so only
185 differences between the timestamps and not their absolute values usually make sense).
188 wxWidgets returns a non-NULL timestamp only for mouse and key events
189 (see wxMouseEvent and wxKeyEvent).
191 long GetTimestamp() const;
194 Returns @true if the event is or is derived from wxCommandEvent else it returns @false.
196 @note exists only for optimization purposes.
198 bool IsCommandEvent() const;
201 Sets the propagation level to the given value (for example returned from an
202 earlier call to wxEvent::StopPropagation).
204 void ResumePropagation(int propagationLevel
);
207 Sets the originating object.
209 void SetEventObject(wxObject
* object
);
214 void SetEventType(wxEventType type
);
217 Sets the identifier associated with this event, such as a button command id.
222 Sets the timestamp for the event.
224 void SetTimestamp(long timeStamp
= 0);
227 Test if this event should be propagated or not, i.e.\ if the propagation level
228 is currently greater than 0.
230 bool ShouldPropagate() const;
233 This method can be used inside an event handler to control whether further
234 event handlers bound to this event will be called after the current one returns.
236 Without Skip() (or equivalently if Skip(@false) is used), the event will not
237 be processed any more. If Skip(@true) is called, the event processing system
238 continues searching for a further handler function for this event, even though
239 it has been processed already in the current handler.
241 In general, it is recommended to skip all non-command events to allow the
242 default handling to take place. The command events are, however, normally not
243 skipped as usually a single command such as a button click or menu item
244 selection must only be processed by one handler.
246 void Skip(bool skip
= true);
249 Stop the event from propagating to its parent window.
251 Returns the old propagation level value which may be later passed to
252 ResumePropagation() to allow propagating the event again.
254 int StopPropagation();
258 Indicates how many levels the event can propagate.
260 This member is protected and should typically only be set in the constructors
261 of the derived classes. It may be temporarily changed by StopPropagation()
262 and ResumePropagation() and tested with ShouldPropagate().
264 The initial value is set to either @c wxEVENT_PROPAGATE_NONE (by default)
265 meaning that the event shouldn't be propagated at all or to
266 @c wxEVENT_PROPAGATE_MAX (for command events) meaning that it should be
267 propagated as much as necessary.
269 Any positive number means that the event should be propagated but no more than
270 the given number of times. E.g. the propagation level may be set to 1 to
271 propagate the event to its parent only, but not to its grandparent.
273 int m_propagationLevel
;
281 @class wxEventBlocker
283 This class is a special event handler which allows to discard
284 any event (or a set of event types) directed to a specific window.
289 void MyWindow::DoSomething()
292 // block all events directed to this window while
293 // we do the 1000 FunctionWhichSendsEvents() calls
294 wxEventBlocker blocker(this);
296 for ( int i = 0; i 1000; i++ )
297 FunctionWhichSendsEvents(i);
299 } // ~wxEventBlocker called, old event handler is restored
301 // the event generated by this call will be processed:
302 FunctionWhichSendsEvents(0)
309 @see @ref overview_events_processing, wxEvtHandler
311 class wxEventBlocker
: public wxEvtHandler
315 Constructs the blocker for the given window and for the given event type.
317 If @a type is @c wxEVT_ANY, then all events for that window are blocked.
318 You can call Block() after creation to add other event types to the list
321 Note that the @a win window @b must remain alive until the
322 wxEventBlocker object destruction.
324 wxEventBlocker(wxWindow
* win
, wxEventType type
= -1);
327 Destructor. The blocker will remove itself from the chain of event handlers for
328 the window provided in the constructor, thus restoring normal processing of events.
330 virtual ~wxEventBlocker();
333 Adds to the list of event types which should be blocked the given @a eventType.
335 void Block(wxEventType eventType
);
341 Helper class to temporarily change an event to not propagate.
343 class wxPropagationDisabler
346 wxPropagationDisabler(wxEvent
& event
);
347 ~wxPropagationDisabler();
352 Helper class to temporarily lower propagation level.
354 class wxPropagateOnce
357 wxPropagateOnce(wxEvent
& event
);
368 A class that can handle events from the windowing system.
369 wxWindow is (and therefore all window classes are) derived from this class.
371 When events are received, wxEvtHandler invokes the method listed in the
372 event table using itself as the object. When using multiple inheritance
373 <b>it is imperative that the wxEvtHandler(-derived) class is the first
374 class inherited</b> such that the @c this pointer for the overall object
375 will be identical to the @c this pointer of the wxEvtHandler portion.
380 @see @ref overview_events_processing, wxEventBlocker, wxEventLoopBase
382 class wxEvtHandler
: public wxObject
, public wxTrackable
393 If the handler is part of a chain, the destructor will unlink itself
396 virtual ~wxEvtHandler();
400 @name Event queuing and processing
405 Queue event for a later processing.
407 This method is similar to ProcessEvent() but while the latter is
408 synchronous, i.e. the event is processed immediately, before the
409 function returns, this one is asynchronous and returns immediately
410 while the event will be processed at some later time (usually during
411 the next event loop iteration).
413 Another important difference is that this method takes ownership of the
414 @a event parameter, i.e. it will delete it itself. This implies that
415 the event should be allocated on the heap and that the pointer can't be
416 used any more after the function returns (as it can be deleted at any
419 QueueEvent() can be used for inter-thread communication from the worker
420 threads to the main thread, it is safe in the sense that it uses
421 locking internally and avoids the problem mentioned in AddPendingEvent()
422 documentation by ensuring that the @a event object is not used by the
423 calling thread any more. Care should still be taken to avoid that some
424 fields of this object are used by it, notably any wxString members of
425 the event object must not be shallow copies of another wxString object
426 as this would result in them still using the same string buffer behind
427 the scenes. For example:
429 void FunctionInAWorkerThread(const wxString& str)
431 wxCommandEvent* evt = new wxCommandEvent;
433 // NOT evt->SetString(str) as this would be a shallow copy
434 evt->SetString(str.c_str()); // make a deep copy
436 wxTheApp->QueueEvent( evt );
440 Note that you can use wxThreadEvent instead of wxCommandEvent
441 to avoid this problem:
443 void FunctionInAWorkerThread(const wxString& str)
448 // wxThreadEvent::Clone() makes sure that the internal wxString
449 // member is not shared by other wxString instances:
450 wxTheApp->QueueEvent( evt.Clone() );
454 Finally notice that this method automatically wakes up the event loop
455 if it is currently idle by calling ::wxWakeUpIdle() so there is no need
456 to do it manually when using it.
461 A heap-allocated event to be queued, QueueEvent() takes ownership
462 of it. This parameter shouldn't be @c NULL.
464 virtual void QueueEvent(wxEvent
*event
);
467 Post an event to be processed later.
469 This function is similar to QueueEvent() but can't be used to post
470 events from worker threads for the event objects with wxString fields
471 (i.e. in practice most of them) because of an unsafe use of the same
472 wxString object which happens because the wxString field in the
473 original @a event object and its copy made internally by this function
474 share the same string buffer internally. Use QueueEvent() to avoid
477 A copy of @a event is made by the function, so the original can be deleted
478 as soon as function returns (it is common that the original is created
479 on the stack). This requires that the wxEvent::Clone() method be
480 implemented by event so that it can be duplicated and stored until it
484 Event to add to the pending events queue.
486 virtual void AddPendingEvent(const wxEvent
& event
);
489 Asynchronously call the given method.
491 Calling this function on an object schedules an asynchronous call to
492 the method specified as CallAfter() argument at a (slightly) later
493 time. This is useful when processing some events as certain actions
494 typically can't be performed inside their handlers, e.g. you shouldn't
495 show a modal dialog from a mouse click event handler as this would
496 break the mouse capture state -- but you can call a method showing
497 this message dialog after the current event handler completes.
499 The method being called must be the method of the object on which
500 CallAfter() itself is called.
502 Notice that it is safe to use CallAfter() from other, non-GUI,
503 threads, but that the method will be always called in the main, GUI,
508 class MyFrame : public wxFrame {
509 void OnClick(wxMouseEvent& event) {
510 CallAfter(&MyFrame::ShowPosition, event.GetPosition());
513 void ShowPosition(const wxPoint& pos) {
515 wxString::Format("Perform click at (%d, %d)?",
516 pos.x, pos.y), "", wxYES_NO) == wxYES )
518 ... do take this click into account ...
524 @param method The method to call.
525 @param x1 The (optional) first parameter to pass to the method.
526 @param x2 The (optional) second parameter to pass to the method.
528 Note that currently only up to 2 arguments can be passed.
530 @note This method is not available with Visual C++ before version 8
531 (Visual Studio 2005) as earlier versions of the compiler don't
532 have the required support for C++ templates to implement it.
536 template<typename T
, typename T1
, ...>
537 void CallAfter(void (T::*method
)(T1
, ...), T1 x1
, ...);
540 Processes an event, searching event tables and calling zero or more suitable
541 event handler function(s).
543 Normally, your application would not call this function: it is called in the
544 wxWidgets implementation to dispatch incoming user interface events to the
545 framework (and application).
547 However, you might need to call it if implementing new functionality
548 (such as a new control) where you define new event types, as opposed to
549 allowing the user to override virtual functions.
551 Notice that you don't usually need to override ProcessEvent() to
552 customize the event handling, overriding the specially provided
553 TryBefore() and TryAfter() functions is usually enough. For example,
554 wxMDIParentFrame may override TryBefore() to ensure that the menu
555 events are processed in the active child frame before being processed
556 in the parent frame itself.
558 The normal order of event table searching is as follows:
559 -# wxApp::FilterEvent() is called. If it returns anything but @c -1
560 (default) the processing stops here.
561 -# TryBefore() is called (this is where wxValidator are taken into
562 account for wxWindow objects). If this returns @true, the function exits.
563 -# If the object is disabled (via a call to wxEvtHandler::SetEvtHandlerEnabled)
564 the function skips to step (7).
565 -# Dynamic event table of the handlers bound using Bind<>() is
566 searched. If a handler is found, it is executed and the function
567 returns @true unless the handler used wxEvent::Skip() to indicate
568 that it didn't handle the event in which case the search continues.
569 -# Static events table of the handlers bound using event table
570 macros is searched for this event handler. If this fails, the base
571 class event table is tried, and so on until no more tables
572 exist or an appropriate function was found. If a handler is found,
573 the same logic as in the previous step applies.
574 -# The search is applied down the entire chain of event handlers (usually the
575 chain has a length of one). This chain can be formed using wxEvtHandler::SetNextHandler():
576 @image html overview_events_chain.png
577 (referring to the image, if @c A->ProcessEvent is called and it doesn't handle
578 the event, @c B->ProcessEvent will be called and so on...).
579 Note that in the case of wxWindow you can build a stack of event handlers
580 (see wxWindow::PushEventHandler() for more info).
581 If any of the handlers of the chain return @true, the function exits.
582 -# TryAfter() is called: for the wxWindow object this may propagate the
583 event to the window parent (recursively). If the event is still not
584 processed, ProcessEvent() on wxTheApp object is called as the last
587 Notice that steps (2)-(6) are performed in ProcessEventLocally()
588 which is called by this function.
593 @true if a suitable event handler function was found and executed,
594 and the function did not call wxEvent::Skip.
596 @see SearchEventTable()
598 virtual bool ProcessEvent(wxEvent
& event
);
601 Try to process the event in this handler and all those chained to it.
603 As explained in ProcessEvent() documentation, the event handlers may be
604 chained in a doubly-linked list. This function tries to process the
605 event in this handler (including performing any pre-processing done in
606 TryBefore(), e.g. applying validators) and all those following it in
607 the chain until the event is processed or the chain is exhausted.
609 This function is called from ProcessEvent() and, in turn, calls
610 TryBefore() and TryAfter(). It is not virtual and so cannot be
611 overridden but can, and should, be called to forward an event to
612 another handler instead of ProcessEvent() which would result in a
613 duplicate call to TryAfter(), e.g. resulting in all unprocessed events
614 being sent to the application object multiple times.
621 @true if this handler of one of those chained to it processed the
624 bool ProcessEventLocally(wxEvent
& event
);
627 Processes an event by calling ProcessEvent() and handles any exceptions
628 that occur in the process.
629 If an exception is thrown in event handler, wxApp::OnExceptionInMainLoop is called.
634 @return @true if the event was processed, @false if no handler was found
635 or an exception was thrown.
637 @see wxWindow::HandleWindowEvent
639 bool SafelyProcessEvent(wxEvent
& event
);
642 Processes the pending events previously queued using QueueEvent() or
643 AddPendingEvent(); you must call this function only if you are sure
644 there are pending events for this handler, otherwise a @c wxCHECK
647 The real processing still happens in ProcessEvent() which is called by this
650 Note that this function needs a valid application object (see
651 wxAppConsole::GetInstance()) because wxApp holds the list of the event
652 handlers with pending events and this function manipulates that list.
654 void ProcessPendingEvents();
657 Deletes all events queued on this event handler using QueueEvent() or
660 Use with care because the events which are deleted are (obviously) not
661 processed and this may have unwanted consequences (e.g. user actions events
664 void DeletePendingEvents();
667 Searches the event table, executing an event handler function if an appropriate
671 Event table to be searched.
673 Event to be matched against an event table entry.
675 @return @true if a suitable event handler function was found and
676 executed, and the function did not call wxEvent::Skip.
678 @remarks This function looks through the object's event table and tries
679 to find an entry that will match the event.
680 An entry will match if:
681 @li The event type matches, and
682 @li the identifier or identifier range matches, or the event table
683 entry's identifier is zero.
685 If a suitable function is called but calls wxEvent::Skip, this
686 function will fail, and searching will continue.
688 @todo this function in the header is listed as an "implementation only" function;
689 are we sure we want to document it?
693 virtual bool SearchEventTable(wxEventTable
& table
,
700 @name Connecting and disconnecting
705 Connects the given function dynamically with the event handler, id and
708 Notice that Bind() provides a more flexible and safer way to do the
709 same thing as Connect(), please use it in any new code -- while
710 Connect() is not formally deprecated due to its existing widespread
711 usage, it has no advantages compared to Bind().
713 This is an alternative to the use of static event tables. It is more
714 flexible as it allows to connect events generated by some object to an
715 event handler defined in a different object of a different class (which
716 is impossible to do directly with the event tables -- the events can be
717 only handled in another object if they are propagated upwards to it).
718 Do make sure to specify the correct @a eventSink when connecting to an
719 event of a different object.
721 See @ref overview_events_bind for more detailed explanation
722 of this function and the @ref page_samples_event sample for usage
725 This specific overload allows you to connect an event handler to a @e range
727 Do not confuse @e source IDs with event @e types: source IDs identify the
728 event generator objects (typically wxMenuItem or wxWindow objects) while the
729 event @e type identify which type of events should be handled by the
730 given @e function (an event generator object may generate many different
734 The first ID of the identifier range to be associated with the event
737 The last ID of the identifier range to be associated with the event
740 The event type to be associated with this event handler.
742 The event handler function. Note that this function should
743 be explicitly converted to the correct type which can be done using a macro
744 called @c wxFooEventHandler for the handler for any @c wxFooEvent.
746 Optional data to be associated with the event table entry.
747 wxWidgets will take ownership of this pointer, i.e. it will be
748 destroyed when the event handler is disconnected or at the program
749 termination. This pointer can be retrieved using
750 wxEvent::GetEventUserData() later.
752 Object whose member function should be called. It must be specified
753 when connecting an event generated by one object to a member
754 function of a different object. If it is omitted, @c this is used.
757 In wxPerl this function takes 4 arguments: @a id, @a lastid,
758 @a type, @a method; if @a method is undef, the handler is
764 void Connect(int id
, int lastId
, wxEventType eventType
,
765 wxObjectEventFunction function
,
766 wxObject
* userData
= NULL
,
767 wxEvtHandler
* eventSink
= NULL
);
770 See the Connect(int, int, wxEventType, wxObjectEventFunction, wxObject*, wxEvtHandler*)
771 overload for more info.
773 This overload can be used to attach an event handler to a single source ID:
777 frame->Connect( wxID_EXIT,
778 wxEVT_COMMAND_MENU_SELECTED,
779 wxCommandEventHandler(MyFrame::OnQuit) );
783 Not supported by wxPerl.
786 void Connect(int id
, wxEventType eventType
,
787 wxObjectEventFunction function
,
788 wxObject
* userData
= NULL
,
789 wxEvtHandler
* eventSink
= NULL
);
792 See the Connect(int, int, wxEventType, wxObjectEventFunction, wxObject*, wxEvtHandler*)
793 overload for more info.
795 This overload will connect the given event handler so that regardless of the
796 ID of the event source, the handler will be called.
799 Not supported by wxPerl.
802 void Connect(wxEventType eventType
,
803 wxObjectEventFunction function
,
804 wxObject
* userData
= NULL
,
805 wxEvtHandler
* eventSink
= NULL
);
808 Disconnects the given function dynamically from the event handler, using the
809 specified parameters as search criteria and returning @true if a matching
810 function has been found and removed.
812 This method can only disconnect functions which have been added using the
813 Connect() method. There is no way to disconnect functions connected using
814 the (static) event tables.
817 The event type associated with this event handler.
819 The event handler function.
821 Data associated with the event table entry.
823 Object whose member function should be called.
826 Not supported by wxPerl.
829 bool Disconnect(wxEventType eventType
,
830 wxObjectEventFunction function
,
831 wxObject
* userData
= NULL
,
832 wxEvtHandler
* eventSink
= NULL
);
835 See the Disconnect(wxEventType, wxObjectEventFunction, wxObject*, wxEvtHandler*)
836 overload for more info.
838 This overload takes the additional @a id parameter.
841 Not supported by wxPerl.
844 bool Disconnect(int id
= wxID_ANY
,
845 wxEventType eventType
= wxEVT_NULL
,
846 wxObjectEventFunction function
= NULL
,
847 wxObject
* userData
= NULL
,
848 wxEvtHandler
* eventSink
= NULL
);
851 See the Disconnect(wxEventType, wxObjectEventFunction, wxObject*, wxEvtHandler*)
852 overload for more info.
854 This overload takes an additional range of source IDs.
857 In wxPerl this function takes 3 arguments: @a id,
861 bool Disconnect(int id
, int lastId
,
862 wxEventType eventType
,
863 wxObjectEventFunction function
= NULL
,
864 wxObject
* userData
= NULL
,
865 wxEvtHandler
* eventSink
= NULL
);
870 @name Binding and Unbinding
875 Binds the given function, functor or method dynamically with the event.
877 This offers basically the same functionality as Connect(), but it is
878 more flexible as it also allows you to use ordinary functions and
879 arbitrary functors as event handlers. It is also less restrictive then
880 Connect() because you can use an arbitrary method as an event handler,
881 whereas Connect() requires a wxEvtHandler derived handler.
883 See @ref overview_events_bind for more detailed explanation
884 of this function and the @ref page_samples_event sample for usage
888 The event type to be associated with this event handler.
890 The event handler functor. This can be an ordinary function but also
891 an arbitrary functor like boost::function<>.
893 The first ID of the identifier range to be associated with the event
896 The last ID of the identifier range to be associated with the event
899 Optional data to be associated with the event table entry.
900 wxWidgets will take ownership of this pointer, i.e. it will be
901 destroyed when the event handler is disconnected or at the program
902 termination. This pointer can be retrieved using
903 wxEvent::GetEventUserData() later.
905 @see @ref overview_cpp_rtti_disabled
909 template <typename EventTag
, typename Functor
>
910 void Bind(const EventTag
& eventType
,
913 int lastId
= wxID_ANY
,
914 wxObject
*userData
= NULL
);
917 See the Bind<>(const EventTag&, Functor, int, int, wxObject*) overload for
920 This overload will bind the given method as the event handler.
923 The event type to be associated with this event handler.
925 The event handler method. This can be an arbitrary method (doesn't need
926 to be from a wxEvtHandler derived class).
928 Object whose method should be called. It must always be specified
929 so it can be checked at compile time whether the given method is an
930 actual member of the given handler.
932 The first ID of the identifier range to be associated with the event
935 The last ID of the identifier range to be associated with the event
938 Optional data to be associated with the event table entry.
939 wxWidgets will take ownership of this pointer, i.e. it will be
940 destroyed when the event handler is disconnected or at the program
941 termination. This pointer can be retrieved using
942 wxEvent::GetEventUserData() later.
944 @see @ref overview_cpp_rtti_disabled
948 template <typename EventTag
, typename Class
, typename EventArg
, typename EventHandler
>
949 void Bind(const EventTag
&eventType
,
950 void (Class::*method
)(EventArg
&),
951 EventHandler
*handler
,
953 int lastId
= wxID_ANY
,
954 wxObject
*userData
= NULL
);
956 Unbinds the given function, functor or method dynamically from the
957 event handler, using the specified parameters as search criteria and
958 returning @true if a matching function has been found and removed.
960 This method can only unbind functions, functors or methods which have
961 been added using the Bind<>() method. There is no way to unbind
962 functions bound using the (static) event tables.
965 The event type associated with this event handler.
967 The event handler functor. This can be an ordinary function but also
968 an arbitrary functor like boost::function<>.
970 The first ID of the identifier range associated with the event
973 The last ID of the identifier range associated with the event
976 Data associated with the event table entry.
978 @see @ref overview_cpp_rtti_disabled
982 template <typename EventTag
, typename Functor
>
983 bool Unbind(const EventTag
& eventType
,
986 int lastId
= wxID_ANY
,
987 wxObject
*userData
= NULL
);
990 See the Unbind<>(const EventTag&, Functor, int, int, wxObject*)
991 overload for more info.
993 This overload unbinds the given method from the event..
996 The event type associated with this event handler.
998 The event handler method associated with this event.
1000 Object whose method was called.
1002 The first ID of the identifier range associated with the event
1005 The last ID of the identifier range associated with the event
1008 Data associated with the event table entry.
1010 @see @ref overview_cpp_rtti_disabled
1014 template <typename EventTag
, typename Class
, typename EventArg
, typename EventHandler
>
1015 bool Unbind(const EventTag
&eventType
,
1016 void (Class::*method
)(EventArg
&),
1017 EventHandler
*handler
,
1019 int lastId
= wxID_ANY
,
1020 wxObject
*userData
= NULL
);
1023 @name User-supplied data
1028 Returns user-supplied client data.
1030 @remarks Normally, any extra data the programmer wishes to associate with
1031 the object should be made available by deriving a new class with
1034 @see SetClientData()
1036 void* GetClientData() const;
1039 Returns a pointer to the user-supplied client data object.
1041 @see SetClientObject(), wxClientData
1043 wxClientData
* GetClientObject() const;
1046 Sets user-supplied client data.
1049 Data to be associated with the event handler.
1051 @remarks Normally, any extra data the programmer wishes to associate
1052 with the object should be made available by deriving a new
1053 class with new data members. You must not call this method
1054 and SetClientObject on the same class - only one of them.
1056 @see GetClientData()
1058 void SetClientData(void* data
);
1061 Set the client data object. Any previous object will be deleted.
1063 @see GetClientObject(), wxClientData
1065 void SetClientObject(wxClientData
* data
);
1071 @name Event handler chaining
1073 wxEvtHandler can be arranged in a double-linked list of handlers
1074 which is automatically iterated by ProcessEvent() if needed.
1079 Returns @true if the event handler is enabled, @false otherwise.
1081 @see SetEvtHandlerEnabled()
1083 bool GetEvtHandlerEnabled() const;
1086 Returns the pointer to the next handler in the chain.
1088 @see SetNextHandler(), GetPreviousHandler(), SetPreviousHandler(),
1089 wxWindow::PushEventHandler, wxWindow::PopEventHandler
1091 wxEvtHandler
* GetNextHandler() const;
1094 Returns the pointer to the previous handler in the chain.
1096 @see SetPreviousHandler(), GetNextHandler(), SetNextHandler(),
1097 wxWindow::PushEventHandler, wxWindow::PopEventHandler
1099 wxEvtHandler
* GetPreviousHandler() const;
1102 Enables or disables the event handler.
1105 @true if the event handler is to be enabled, @false if it is to be disabled.
1107 @remarks You can use this function to avoid having to remove the event
1108 handler from the chain, for example when implementing a
1109 dialog editor and changing from edit to test mode.
1111 @see GetEvtHandlerEnabled()
1113 void SetEvtHandlerEnabled(bool enabled
);
1116 Sets the pointer to the next handler.
1119 See ProcessEvent() for more info about how the chains of event handlers
1120 are internally used.
1121 Also remember that wxEvtHandler uses double-linked lists and thus if you
1122 use this function, you should also call SetPreviousHandler() on the
1123 argument passed to this function:
1125 handlerA->SetNextHandler(handlerB);
1126 handlerB->SetPreviousHandler(handlerA);
1130 The event handler to be set as the next handler.
1133 @see @ref overview_events_processing
1135 virtual void SetNextHandler(wxEvtHandler
* handler
);
1138 Sets the pointer to the previous handler.
1139 All remarks about SetNextHandler() apply to this function as well.
1142 The event handler to be set as the previous handler.
1145 @see @ref overview_events_processing
1147 virtual void SetPreviousHandler(wxEvtHandler
* handler
);
1150 Unlinks this event handler from the chain it's part of (if any);
1151 then links the "previous" event handler to the "next" one
1152 (so that the chain won't be interrupted).
1154 E.g. if before calling Unlink() you have the following chain:
1155 @image html evthandler_unlink_before.png
1156 then after calling @c B->Unlink() you'll have:
1157 @image html evthandler_unlink_after.png
1164 Returns @true if the next and the previous handler pointers of this
1165 event handler instance are @NULL.
1169 @see SetPreviousHandler(), SetNextHandler()
1171 bool IsUnlinked() const;
1176 @name Global event filters.
1178 Methods for working with the global list of event filters.
1180 Event filters can be defined to pre-process all the events that happen
1181 in an application, see wxEventFilter documentation for more information.
1186 Add an event filter whose FilterEvent() method will be called for each
1187 and every event processed by wxWidgets.
1189 The filters are called in LIFO order and wxApp is registered as an
1190 event filter by default. The pointer must remain valid until it's
1191 removed with RemoveFilter() and is not deleted by wxEvtHandler.
1195 static void AddFilter(wxEventFilter
* filter
);
1198 Remove a filter previously installed with AddFilter().
1200 It's an error to remove a filter that hadn't been previously added or
1201 was already removed.
1205 static void RemoveFilter(wxEventFilter
* filter
);
1211 Method called by ProcessEvent() before examining this object event
1214 This method can be overridden to hook into the event processing logic
1215 as early as possible. You should usually call the base class version
1216 when overriding this method, even if wxEvtHandler itself does nothing
1217 here, some derived classes do use this method, e.g. wxWindow implements
1218 support for wxValidator in it.
1222 class MyClass : public BaseClass // inheriting from wxEvtHandler
1226 virtual bool TryBefore(wxEvent& event)
1228 if ( MyPreProcess(event) )
1231 return BaseClass::TryBefore(event);
1238 virtual bool TryBefore(wxEvent
& event
);
1241 Method called by ProcessEvent() as last resort.
1243 This method can be overridden to implement post-processing for the
1244 events which were not processed anywhere else.
1246 The base class version handles forwarding the unprocessed events to
1247 wxApp at wxEvtHandler level and propagating them upwards the window
1248 child-parent chain at wxWindow level and so should usually be called
1249 when overriding this method:
1251 class MyClass : public BaseClass // inheriting from wxEvtHandler
1255 virtual bool TryAfter(wxEvent& event)
1257 if ( BaseClass::TryAfter(event) )
1260 return MyPostProcess(event);
1267 virtual bool TryAfter(wxEvent
& event
);
1270 #endif // wxUSE_BASE
1275 Flags for categories of keys.
1277 These values are used by wxKeyEvent::IsKeyInCategory(). They may be
1278 combined via the bitwise operators |, &, and ~.
1282 enum wxKeyCategoryFlags
1284 /// arrow keys, on and off numeric keypads
1287 /// page up and page down keys, on and off numeric keypads
1288 WXK_CATEGORY_PAGING
,
1290 /// home and end keys, on and off numeric keypads
1293 /// tab key, on and off numeric keypads
1296 /// backspace and delete keys, on and off numeric keypads
1299 /// union of WXK_CATEGORY_ARROW, WXK_CATEGORY_PAGING, and WXK_CATEGORY_JUMP categories
1300 WXK_CATEGORY_NAVIGATION
1307 This event class contains information about key press and release events.
1309 The main information carried by this event is the key being pressed or
1310 released. It can be accessed using either GetKeyCode() function or
1311 GetUnicodeKey(). For the printable characters, the latter should be used as
1312 it works for any keys, including non-Latin-1 characters that can be entered
1313 when using national keyboard layouts. GetKeyCode() should be used to handle
1314 special characters (such as cursor arrows keys or @c HOME or @c INS and so
1315 on) which correspond to ::wxKeyCode enum elements above the @c WXK_START
1316 constant. While GetKeyCode() also returns the character code for Latin-1
1317 keys for compatibility, it doesn't work for Unicode characters in general
1318 and will return @c WXK_NONE for any non-Latin-1 ones. For this reason, it's
1319 recommended to always use GetUnicodeKey() and only fall back to GetKeyCode()
1320 if GetUnicodeKey() returned @c WXK_NONE meaning that the event corresponds
1321 to a non-printable special keys.
1323 While both of these functions can be used with the events of @c
1324 wxEVT_KEY_DOWN, @c wxEVT_KEY_UP and @c wxEVT_CHAR types, the values
1325 returned by them are different for the first two events and the last one.
1326 For the latter, the key returned corresponds to the character that would
1327 appear in e.g. a text zone if the user pressed the key in it. As such, its
1328 value depends on the current state of the Shift key and, for the letters,
1329 on the state of Caps Lock modifier. For example, if @c A key is pressed
1330 without Shift being held down, wxKeyEvent of type @c wxEVT_CHAR generated
1331 for this key press will return (from either GetKeyCode() or GetUnicodeKey()
1332 as their meanings coincide for ASCII characters) key code of 97
1333 corresponding the ASCII value of @c a. And if the same key is pressed but
1334 with Shift being held (or Caps Lock being active), then the key could would
1335 be 65, i.e. ASCII value of capital @c A.
1337 However for the key down and up events the returned key code will instead
1338 be @c A independently of the state of the modifier keys i.e. it depends
1339 only on physical key being pressed and is not translated to its logical
1340 representation using the current keyboard state. Such untranslated key
1341 codes are defined as follows:
1342 - For the letters they correspond to the @e upper case value of the
1344 - For the other alphanumeric keys (e.g. @c 7 or @c +), the untranslated
1345 key code corresponds to the character produced by the key when it is
1346 pressed without Shift. E.g. in standard US keyboard layout the
1347 untranslated key code for the key @c =/+ in the upper right corner of
1348 the keyboard is 61 which is the ASCII value of @c =.
1349 - For the rest of the keys (i.e. special non-printable keys) it is the
1350 same as the normal key code as no translation is used anyhow.
1352 Notice that the first rule applies to all Unicode letters, not just the
1353 usual Latin-1 ones. However for non-Latin-1 letters only GetUnicodeKey()
1354 can be used to retrieve the key code as GetKeyCode() just returns @c
1355 WXK_NONE in this case.
1357 To summarize: you should handle @c wxEVT_CHAR if you need the translated
1358 key and @c wxEVT_KEY_DOWN if you only need the value of the key itself,
1359 independent of the current keyboard state.
1361 @note Not all key down events may be generated by the user. As an example,
1362 @c wxEVT_KEY_DOWN with @c = key code can be generated using the
1363 standard US keyboard layout but not using the German one because the @c
1364 = key corresponds to Shift-0 key combination in this layout and the key
1365 code for it is @c 0, not @c =. Because of this you should avoid
1366 requiring your users to type key events that might be impossible to
1367 enter on their keyboard.
1370 Another difference between key and char events is that another kind of
1371 translation is done for the latter ones when the Control key is pressed:
1372 char events for ASCII letters in this case carry codes corresponding to the
1373 ASCII value of Ctrl-Latter, i.e. 1 for Ctrl-A, 2 for Ctrl-B and so on until
1374 26 for Ctrl-Z. This is convenient for terminal-like applications and can be
1375 completely ignored by all the other ones (if you need to handle Ctrl-A it
1376 is probably a better idea to use the key event rather than the char one).
1377 Notice that currently no translation is done for the presses of @c [, @c
1378 \\, @c ], @c ^ and @c _ keys which might be mapped to ASCII values from 27
1380 Since version 2.9.2, the enum values @c WXK_CONTROL_A - @c WXK_CONTROL_Z
1381 can be used instead of the non-descriptive constant values 1-26.
1383 Finally, modifier keys only generate key events but no char events at all.
1384 The modifiers keys are @c WXK_SHIFT, @c WXK_CONTROL, @c WXK_ALT and various
1385 @c WXK_WINDOWS_XXX from ::wxKeyCode enum.
1387 Modifier keys events are special in one additional aspect: usually the
1388 keyboard state associated with a key press is well defined, e.g.
1389 wxKeyboardState::ShiftDown() returns @c true only if the Shift key was held
1390 pressed when the key that generated this event itself was pressed. There is
1391 an ambiguity for the key press events for Shift key itself however. By
1392 convention, it is considered to be already pressed when it is pressed and
1393 already released when it is released. In other words, @c wxEVT_KEY_DOWN
1394 event for the Shift key itself will have @c wxMOD_SHIFT in GetModifiers()
1395 and ShiftDown() will return true while the @c wxEVT_KEY_UP event for Shift
1396 itself will not have @c wxMOD_SHIFT in its modifiers and ShiftDown() will
1400 @b Tip: You may discover the key codes and modifiers generated by all the
1401 keys on your system interactively by running the @ref
1402 page_samples_keyboard wxWidgets sample and pressing some keys in it.
1404 @note If a key down (@c EVT_KEY_DOWN) event is caught and the event handler
1405 does not call @c event.Skip() then the corresponding char event
1406 (@c EVT_CHAR) will not happen. This is by design and enables the
1407 programs that handle both types of events to avoid processing the
1408 same key twice. As a consequence, if you do not want to suppress the
1409 @c wxEVT_CHAR events for the keys you handle, always call @c
1410 event.Skip() in your @c wxEVT_KEY_DOWN handler. Not doing may also
1411 prevent accelerators defined using this key from working.
1413 @note If a key is maintained in a pressed state, you will typically get a
1414 lot of (automatically generated) key down events but only one key up
1415 one at the end when the key is released so it is wrong to assume that
1416 there is one up event corresponding to each down one.
1418 @note For Windows programmers: The key and char events in wxWidgets are
1419 similar to but slightly different from Windows @c WM_KEYDOWN and
1420 @c WM_CHAR events. In particular, Alt-x combination will generate a
1421 char event in wxWidgets (unless it is used as an accelerator) and
1422 almost all keys, including ones without ASCII equivalents, generate
1426 @beginEventTable{wxKeyEvent}
1427 @event{EVT_KEY_DOWN(func)}
1428 Process a @c wxEVT_KEY_DOWN event (any key has been pressed). If this
1429 event is handled and not skipped, @c wxEVT_CHAR will not be generated
1430 at all for this key press (but @c wxEVT_KEY_UP will be).
1431 @event{EVT_KEY_UP(func)}
1432 Process a @c wxEVT_KEY_UP event (any key has been released).
1433 @event{EVT_CHAR(func)}
1434 Process a @c wxEVT_CHAR event.
1435 @event{EVT_CHAR_HOOK(func)}
1436 Process a @c wxEVT_CHAR_HOOK event. Unlike all the other key events,
1437 this event is propagated upwards the window hierarchy which allows
1438 intercepting it in the parent window of the focused window to which it
1439 is sent initially (if there is no focused window, this event is sent to
1440 the wxApp global object). It is also generated before any other key
1441 events and so gives the parent window an opportunity to modify the
1442 keyboard handling of its children, e.g. it is used internally by
1443 wxWidgets in some ports to intercept pressing Esc key in any child of a
1444 dialog to close the dialog itself when it's pressed. By default, if
1445 this event is handled, i.e. the handler doesn't call wxEvent::Skip(),
1446 neither @c wxEVT_KEY_DOWN nor @c wxEVT_CHAR events will be generated
1447 (although @c wxEVT_KEY_UP still will be), i.e. it replaces the normal
1448 key events. However by calling the special DoAllowNextEvent() method
1449 you can handle @c wxEVT_CHAR_HOOK and still allow normal events
1450 generation. This is something that is rarely useful but can be required
1451 if you need to prevent a parent @c wxEVT_CHAR_HOOK handler from running
1452 without suppressing the normal key events. Finally notice that this
1453 event is not generated when the mouse is captured as it is considered
1454 that the window which has the capture should receive all the keyboard
1455 events too without allowing its parent wxTopLevelWindow to interfere
1456 with their processing.
1459 @see wxKeyboardState
1464 class wxKeyEvent
: public wxEvent
,
1465 public wxKeyboardState
1470 Currently, the only valid event types are @c wxEVT_CHAR and @c wxEVT_CHAR_HOOK.
1472 wxKeyEvent(wxEventType keyEventType
= wxEVT_NULL
);
1475 Returns the key code of the key that generated this event.
1477 ASCII symbols return normal ASCII values, while events from special
1478 keys such as "left cursor arrow" (@c WXK_LEFT) return values outside of
1479 the ASCII range. See ::wxKeyCode for a full list of the virtual key
1482 Note that this method returns a meaningful value only for special
1483 non-alphanumeric keys or if the user entered a Latin-1 character (this
1484 includes ASCII and the accented letters found in Western European
1485 languages but not letters of other alphabets such as e.g. Cyrillic).
1486 Otherwise it simply method returns @c WXK_NONE and GetUnicodeKey()
1487 should be used to obtain the corresponding Unicode character.
1489 Using GetUnicodeKey() is in general the right thing to do if you are
1490 interested in the characters typed by the user, GetKeyCode() should be
1491 only used for special keys (for which GetUnicodeKey() returns @c
1492 WXK_NONE). To handle both kinds of keys you might write:
1494 void MyHandler::OnChar(wxKeyEvent& event)
1496 wxChar uc = event.GetUnicodeKey();
1497 if ( uc != WXK_NONE )
1499 // It's a "normal" character. Notice that this includes
1500 // control characters in 1..31 range, e.g. WXK_RETURN or
1501 // WXK_BACK, so check for them explicitly.
1504 wxLogMessage("You pressed '%c'", uc);
1508 // It's a control character
1512 else // No Unicode equivalent.
1514 // It's a special key, deal with all the known ones:
1515 switch ( event.GetKeyCode() )
1530 int GetKeyCode() const;
1533 Returns true if the key is in the given key category.
1536 A bitwise combination of named ::wxKeyCategoryFlags constants.
1540 bool IsKeyInCategory(int category
) const;
1544 Obtains the position (in client coordinates) at which the key was pressed.
1546 Notice that under most platforms this position is simply the current
1547 mouse pointer position and has no special relationship to the key event
1550 @a x and @a y may be @NULL if the corresponding coordinate is not
1553 wxPoint
GetPosition() const;
1554 void GetPosition(wxCoord
* x
, wxCoord
* y
) const;
1558 Returns the raw key code for this event.
1560 The flags are platform-dependent and should only be used if the
1561 functionality provided by other wxKeyEvent methods is insufficient.
1563 Under MSW, the raw key code is the value of @c wParam parameter of the
1564 corresponding message.
1566 Under GTK, the raw key code is the @c keyval field of the corresponding
1569 Under OS X, the raw key code is the @c keyCode field of the
1570 corresponding NSEvent.
1572 @note Currently the raw key codes are not supported by all ports, use
1573 @ifdef_ wxHAS_RAW_KEY_CODES to determine if this feature is available.
1575 wxUint32
GetRawKeyCode() const;
1578 Returns the low level key flags for this event.
1580 The flags are platform-dependent and should only be used if the
1581 functionality provided by other wxKeyEvent methods is insufficient.
1583 Under MSW, the raw flags are just the value of @c lParam parameter of
1584 the corresponding message.
1586 Under GTK, the raw flags contain the @c hardware_keycode field of the
1587 corresponding GDK event.
1589 Under OS X, the raw flags contain the modifiers state.
1591 @note Currently the raw key flags are not supported by all ports, use
1592 @ifdef_ wxHAS_RAW_KEY_CODES to determine if this feature is available.
1594 wxUint32
GetRawKeyFlags() const;
1597 Returns the Unicode character corresponding to this key event.
1599 If the key pressed doesn't have any character value (e.g. a cursor key)
1600 this method will return @c WXK_NONE. In this case you should use
1601 GetKeyCode() to retrieve the value of the key.
1603 This function is only available in Unicode build, i.e. when
1604 @c wxUSE_UNICODE is 1.
1606 wxChar
GetUnicodeKey() const;
1609 Returns the X position (in client coordinates) of the event.
1613 wxCoord
GetX() const;
1616 Returns the Y position (in client coordinates) of the event.
1620 wxCoord
GetY() const;
1623 Allow normal key events generation.
1625 Can be called from @c wxEVT_CHAR_HOOK handler to indicate that the
1626 generation of normal events should @em not be suppressed, as it happens
1627 by default when this event is handled.
1629 The intended use of this method is to allow some window object to
1630 prevent @c wxEVT_CHAR_HOOK handler in its parent window from running by
1631 defining its own handler for this event. Without calling this method,
1632 this would result in not generating @c wxEVT_KEY_DOWN nor @c wxEVT_CHAR
1633 events at all but by calling it you can ensure that these events would
1634 still be generated, even if @c wxEVT_CHAR_HOOK event was handled.
1638 void DoAllowNextEvent();
1641 Returns @true if DoAllowNextEvent() had been called, @false by default.
1643 This method is used by wxWidgets itself to determine whether the normal
1644 key events should be generated after @c wxEVT_CHAR_HOOK processing.
1648 bool IsNextEventAllowed() const;
1659 // Which button is down?
1662 wxJOY_BUTTON_ANY
= -1,
1671 @class wxJoystickEvent
1673 This event class contains information about joystick events, particularly
1674 events received by windows.
1676 @beginEventTable{wxJoystickEvent}
1677 @event{EVT_JOY_BUTTON_DOWN(func)}
1678 Process a @c wxEVT_JOY_BUTTON_DOWN event.
1679 @event{EVT_JOY_BUTTON_UP(func)}
1680 Process a @c wxEVT_JOY_BUTTON_UP event.
1681 @event{EVT_JOY_MOVE(func)}
1682 Process a @c wxEVT_JOY_MOVE event.
1683 @event{EVT_JOY_ZMOVE(func)}
1684 Process a @c wxEVT_JOY_ZMOVE event.
1685 @event{EVT_JOYSTICK_EVENTS(func)}
1686 Processes all joystick events.
1694 class wxJoystickEvent
: public wxEvent
1700 wxJoystickEvent(wxEventType eventType
= wxEVT_NULL
, int state
= 0,
1701 int joystick
= wxJOYSTICK1
,
1705 Returns @true if the event was a down event from the specified button
1709 Can be @c wxJOY_BUTTONn where @c n is 1, 2, 3 or 4; or @c wxJOY_BUTTON_ANY to
1710 indicate any button down event.
1712 bool ButtonDown(int button
= wxJOY_BUTTON_ANY
) const;
1715 Returns @true if the specified button (or any button) was in a down state.
1718 Can be @c wxJOY_BUTTONn where @c n is 1, 2, 3 or 4; or @c wxJOY_BUTTON_ANY to
1719 indicate any button down event.
1721 bool ButtonIsDown(int button
= wxJOY_BUTTON_ANY
) const;
1724 Returns @true if the event was an up event from the specified button
1728 Can be @c wxJOY_BUTTONn where @c n is 1, 2, 3 or 4; or @c wxJOY_BUTTON_ANY to
1729 indicate any button down event.
1731 bool ButtonUp(int button
= wxJOY_BUTTON_ANY
) const;
1734 Returns the identifier of the button changing state.
1736 This is a @c wxJOY_BUTTONn identifier, where @c n is one of 1, 2, 3, 4.
1738 int GetButtonChange() const;
1741 Returns the down state of the buttons.
1743 This is a @c wxJOY_BUTTONn identifier, where @c n is one of 1, 2, 3, 4.
1745 int GetButtonState() const;
1748 Returns the identifier of the joystick generating the event - one of
1749 wxJOYSTICK1 and wxJOYSTICK2.
1751 int GetJoystick() const;
1754 Returns the x, y position of the joystick event.
1756 These coordinates are valid for all the events except wxEVT_JOY_ZMOVE.
1758 wxPoint
GetPosition() const;
1761 Returns the z position of the joystick event.
1763 This method can only be used for wxEVT_JOY_ZMOVE events.
1765 int GetZPosition() const;
1768 Returns @true if this was a button up or down event
1769 (@e not 'is any button down?').
1771 bool IsButton() const;
1774 Returns @true if this was an x, y move event.
1776 bool IsMove() const;
1779 Returns @true if this was a z move event.
1781 bool IsZMove() const;
1787 @class wxScrollWinEvent
1789 A scroll event holds information about events sent from scrolling windows.
1791 Note that you can use the EVT_SCROLLWIN* macros for intercepting scroll window events
1792 from the receiving window.
1794 @beginEventTable{wxScrollWinEvent}
1795 @event{EVT_SCROLLWIN(func)}
1796 Process all scroll events.
1797 @event{EVT_SCROLLWIN_TOP(func)}
1798 Process @c wxEVT_SCROLLWIN_TOP scroll-to-top events.
1799 @event{EVT_SCROLLWIN_BOTTOM(func)}
1800 Process @c wxEVT_SCROLLWIN_BOTTOM scroll-to-bottom events.
1801 @event{EVT_SCROLLWIN_LINEUP(func)}
1802 Process @c wxEVT_SCROLLWIN_LINEUP line up events.
1803 @event{EVT_SCROLLWIN_LINEDOWN(func)}
1804 Process @c wxEVT_SCROLLWIN_LINEDOWN line down events.
1805 @event{EVT_SCROLLWIN_PAGEUP(func)}
1806 Process @c wxEVT_SCROLLWIN_PAGEUP page up events.
1807 @event{EVT_SCROLLWIN_PAGEDOWN(func)}
1808 Process @c wxEVT_SCROLLWIN_PAGEDOWN page down events.
1809 @event{EVT_SCROLLWIN_THUMBTRACK(func)}
1810 Process @c wxEVT_SCROLLWIN_THUMBTRACK thumbtrack events
1811 (frequent events sent as the user drags the thumbtrack).
1812 @event{EVT_SCROLLWIN_THUMBRELEASE(func)}
1813 Process @c wxEVT_SCROLLWIN_THUMBRELEASE thumb release events.
1820 @see wxScrollEvent, @ref overview_events
1822 class wxScrollWinEvent
: public wxEvent
1828 wxScrollWinEvent(wxEventType commandType
= wxEVT_NULL
, int pos
= 0,
1829 int orientation
= 0);
1832 Returns wxHORIZONTAL or wxVERTICAL, depending on the orientation of the
1835 @todo wxHORIZONTAL and wxVERTICAL should go in their own enum
1837 int GetOrientation() const;
1840 Returns the position of the scrollbar for the thumb track and release events.
1842 Note that this field can't be used for the other events, you need to query
1843 the window itself for the current position in that case.
1845 int GetPosition() const;
1847 void SetOrientation(int orient
);
1848 void SetPosition(int pos
);
1854 @class wxSysColourChangedEvent
1856 This class is used for system colour change events, which are generated
1857 when the user changes the colour settings using the control panel.
1858 This is only appropriate under Windows.
1861 The default event handler for this event propagates the event to child windows,
1862 since Windows only sends the events to top-level windows.
1863 If intercepting this event for a top-level window, remember to call the base
1864 class handler, or to pass the event on to the window's children explicitly.
1866 @beginEventTable{wxSysColourChangedEvent}
1867 @event{EVT_SYS_COLOUR_CHANGED(func)}
1868 Process a @c wxEVT_SYS_COLOUR_CHANGED event.
1874 @see @ref overview_events
1876 class wxSysColourChangedEvent
: public wxEvent
1882 wxSysColourChangedEvent();
1888 @class wxCommandEvent
1890 This event class contains information about command events, which originate
1891 from a variety of simple controls.
1893 Note that wxCommandEvents and wxCommandEvent-derived event classes by default
1894 and unlike other wxEvent-derived classes propagate upward from the source
1895 window (the window which emits the event) up to the first parent which processes
1896 the event. Be sure to read @ref overview_events_propagation.
1898 More complex controls, such as wxTreeCtrl, have separate command event classes.
1900 @beginEventTable{wxCommandEvent}
1901 @event{EVT_COMMAND(id, event, func)}
1902 Process a command, supplying the window identifier, command event identifier,
1903 and member function.
1904 @event{EVT_COMMAND_RANGE(id1, id2, event, func)}
1905 Process a command for a range of window identifiers, supplying the minimum and
1906 maximum window identifiers, command event identifier, and member function.
1907 @event{EVT_BUTTON(id, func)}
1908 Process a @c wxEVT_COMMAND_BUTTON_CLICKED command, which is generated by a wxButton control.
1909 @event{EVT_CHECKBOX(id, func)}
1910 Process a @c wxEVT_COMMAND_CHECKBOX_CLICKED command, which is generated by a wxCheckBox control.
1911 @event{EVT_CHOICE(id, func)}
1912 Process a @c wxEVT_COMMAND_CHOICE_SELECTED command, which is generated by a wxChoice control.
1913 @event{EVT_COMBOBOX(id, func)}
1914 Process a @c wxEVT_COMMAND_COMBOBOX_SELECTED command, which is generated by a wxComboBox control.
1915 @event{EVT_LISTBOX(id, func)}
1916 Process a @c wxEVT_COMMAND_LISTBOX_SELECTED command, which is generated by a wxListBox control.
1917 @event{EVT_LISTBOX_DCLICK(id, func)}
1918 Process a @c wxEVT_COMMAND_LISTBOX_DOUBLECLICKED command, which is generated by a wxListBox control.
1919 @event{EVT_CHECKLISTBOX(id, func)}
1920 Process a @c wxEVT_COMMAND_CHECKLISTBOX_TOGGLED command, which is generated by a wxCheckListBox control.
1921 @event{EVT_MENU(id, func)}
1922 Process a @c wxEVT_COMMAND_MENU_SELECTED command, which is generated by a menu item.
1923 @event{EVT_MENU_RANGE(id1, id2, func)}
1924 Process a @c wxEVT_COMMAND_MENU_RANGE command, which is generated by a range of menu items.
1925 @event{EVT_CONTEXT_MENU(func)}
1926 Process the event generated when the user has requested a popup menu to appear by
1927 pressing a special keyboard key (under Windows) or by right clicking the mouse.
1928 @event{EVT_RADIOBOX(id, func)}
1929 Process a @c wxEVT_COMMAND_RADIOBOX_SELECTED command, which is generated by a wxRadioBox control.
1930 @event{EVT_RADIOBUTTON(id, func)}
1931 Process a @c wxEVT_COMMAND_RADIOBUTTON_SELECTED command, which is generated by a wxRadioButton control.
1932 @event{EVT_SCROLLBAR(id, func)}
1933 Process a @c wxEVT_COMMAND_SCROLLBAR_UPDATED command, which is generated by a wxScrollBar
1934 control. This is provided for compatibility only; more specific scrollbar event macros
1935 should be used instead (see wxScrollEvent).
1936 @event{EVT_SLIDER(id, func)}
1937 Process a @c wxEVT_COMMAND_SLIDER_UPDATED command, which is generated by a wxSlider control.
1938 @event{EVT_TEXT(id, func)}
1939 Process a @c wxEVT_COMMAND_TEXT_UPDATED command, which is generated by a wxTextCtrl control.
1940 @event{EVT_TEXT_ENTER(id, func)}
1941 Process a @c wxEVT_COMMAND_TEXT_ENTER command, which is generated by a wxTextCtrl control.
1942 Note that you must use wxTE_PROCESS_ENTER flag when creating the control if you want it
1943 to generate such events.
1944 @event{EVT_TEXT_MAXLEN(id, func)}
1945 Process a @c wxEVT_COMMAND_TEXT_MAXLEN command, which is generated by a wxTextCtrl control
1946 when the user tries to enter more characters into it than the limit previously set
1947 with SetMaxLength().
1948 @event{EVT_TOGGLEBUTTON(id, func)}
1949 Process a @c wxEVT_COMMAND_TOGGLEBUTTON_CLICKED event.
1950 @event{EVT_TOOL(id, func)}
1951 Process a @c wxEVT_COMMAND_TOOL_CLICKED event (a synonym for @c wxEVT_COMMAND_MENU_SELECTED).
1952 Pass the id of the tool.
1953 @event{EVT_TOOL_RANGE(id1, id2, func)}
1954 Process a @c wxEVT_COMMAND_TOOL_CLICKED event for a range of identifiers. Pass the ids of the tools.
1955 @event{EVT_TOOL_RCLICKED(id, func)}
1956 Process a @c wxEVT_COMMAND_TOOL_RCLICKED event. Pass the id of the tool. (Not available on wxOSX.)
1957 @event{EVT_TOOL_RCLICKED_RANGE(id1, id2, func)}
1958 Process a @c wxEVT_COMMAND_TOOL_RCLICKED event for a range of ids. Pass the ids of the tools. (Not available on wxOSX.)
1959 @event{EVT_TOOL_ENTER(id, func)}
1960 Process a @c wxEVT_COMMAND_TOOL_ENTER event. Pass the id of the toolbar itself.
1961 The value of wxCommandEvent::GetSelection() is the tool id, or -1 if the mouse cursor
1962 has moved off a tool. (Not available on wxOSX.)
1963 @event{EVT_COMMAND_LEFT_CLICK(id, func)}
1964 Process a @c wxEVT_COMMAND_LEFT_CLICK command, which is generated by a control (wxMSW only).
1965 @event{EVT_COMMAND_LEFT_DCLICK(id, func)}
1966 Process a @c wxEVT_COMMAND_LEFT_DCLICK command, which is generated by a control (wxMSW only).
1967 @event{EVT_COMMAND_RIGHT_CLICK(id, func)}
1968 Process a @c wxEVT_COMMAND_RIGHT_CLICK command, which is generated by a control (wxMSW only).
1969 @event{EVT_COMMAND_SET_FOCUS(id, func)}
1970 Process a @c wxEVT_COMMAND_SET_FOCUS command, which is generated by a control (wxMSW only).
1971 @event{EVT_COMMAND_KILL_FOCUS(id, func)}
1972 Process a @c wxEVT_COMMAND_KILL_FOCUS command, which is generated by a control (wxMSW only).
1973 @event{EVT_COMMAND_ENTER(id, func)}
1974 Process a @c wxEVT_COMMAND_ENTER command, which is generated by a control.
1980 class wxCommandEvent
: public wxEvent
1986 wxCommandEvent(wxEventType commandEventType
= wxEVT_NULL
, int id
= 0);
1989 Returns client data pointer for a listbox or choice selection event
1990 (not valid for a deselection).
1992 void* GetClientData() const;
1995 Returns client object pointer for a listbox or choice selection event
1996 (not valid for a deselection).
1998 wxClientData
* GetClientObject() const;
2001 Returns extra information dependent on the event objects type.
2003 If the event comes from a listbox selection, it is a boolean
2004 determining whether the event was a selection (@true) or a
2005 deselection (@false). A listbox deselection only occurs for
2006 multiple-selection boxes, and in this case the index and string values
2007 are indeterminate and the listbox must be examined by the application.
2009 long GetExtraLong() const;
2012 Returns the integer identifier corresponding to a listbox, choice or
2013 radiobox selection (only if the event was a selection, not a deselection),
2014 or a boolean value representing the value of a checkbox.
2016 For a menu item, this method returns -1 if the item is not checkable or
2017 a boolean value (true or false) for checkable items indicating the new
2023 Returns item index for a listbox or choice selection event (not valid for
2026 int GetSelection() const;
2029 Returns item string for a listbox or choice selection event. If one
2030 or several items have been deselected, returns the index of the first
2031 deselected item. If some items have been selected and others deselected
2032 at the same time, it will return the index of the first selected item.
2034 wxString
GetString() const;
2037 This method can be used with checkbox and menu events: for the checkboxes, the
2038 method returns @true for a selection event and @false for a deselection one.
2039 For the menu events, this method indicates if the menu item just has become
2040 checked or unchecked (and thus only makes sense for checkable menu items).
2042 Notice that this method cannot be used with wxCheckListBox currently.
2044 bool IsChecked() const;
2047 For a listbox or similar event, returns @true if it is a selection, @false
2048 if it is a deselection. If some items have been selected and others deselected
2049 at the same time, it will return @true.
2051 bool IsSelection() const;
2054 Sets the client data for this event.
2056 void SetClientData(void* clientData
);
2059 Sets the client object for this event. The client object is not owned by the
2060 event object and the event object will not delete the client object in its destructor.
2062 The client object must be owned and deleted by another object (e.g. a control)
2063 that has longer life time than the event object.
2065 void SetClientObject(wxClientData
* clientObject
);
2068 Sets the @b m_extraLong member.
2070 void SetExtraLong(long extraLong
);
2073 Sets the @b m_commandInt member.
2075 void SetInt(int intCommand
);
2078 Sets the @b m_commandString member.
2080 void SetString(const wxString
& string
);
2086 @class wxWindowCreateEvent
2088 This event is sent just after the actual window associated with a wxWindow
2089 object has been created.
2091 Since it is derived from wxCommandEvent, the event propagates up
2092 the window hierarchy.
2094 @beginEventTable{wxWindowCreateEvent}
2095 @event{EVT_WINDOW_CREATE(func)}
2096 Process a @c wxEVT_CREATE event.
2102 @see @ref overview_events, wxWindowDestroyEvent
2104 class wxWindowCreateEvent
: public wxCommandEvent
2110 wxWindowCreateEvent(wxWindow
* win
= NULL
);
2112 /// Return the window being created.
2113 wxWindow
*GetWindow() const;
2121 A paint event is sent when a window's contents needs to be repainted.
2123 The handler of this event must create a wxPaintDC object and use it for
2124 painting the window contents. For example:
2126 void MyWindow::OnPaint(wxPaintEvent& event)
2134 Notice that you must @e not create other kinds of wxDC (e.g. wxClientDC or
2135 wxWindowDC) in EVT_PAINT handlers and also don't create wxPaintDC outside
2136 of this event handlers.
2139 You can optimize painting by retrieving the rectangles that have been damaged
2140 and only repainting these. The rectangles are in terms of the client area,
2141 and are unscrolled, so you will need to do some calculations using the current
2142 view position to obtain logical, scrolled units.
2143 Here is an example of using the wxRegionIterator class:
2145 // Called when window needs to be repainted.
2146 void MyWindow::OnPaint(wxPaintEvent& event)
2150 // Find Out where the window is scrolled to
2151 int vbX,vbY; // Top left corner of client
2152 GetViewStart(&vbX,&vbY);
2154 int vX,vY,vW,vH; // Dimensions of client area in pixels
2155 wxRegionIterator upd(GetUpdateRegion()); // get the update rect list
2164 // Alternatively we can do this:
2165 // wxRect rect(upd.GetRect());
2167 // Repaint this rectangle
2176 Please notice that in general it is impossible to change the drawing of a
2177 standard control (such as wxButton) and so you shouldn't attempt to handle
2178 paint events for them as even if it might work on some platforms, this is
2179 inherently not portable and won't work everywhere.
2182 @beginEventTable{wxPaintEvent}
2183 @event{EVT_PAINT(func)}
2184 Process a @c wxEVT_PAINT event.
2190 @see @ref overview_events
2192 class wxPaintEvent
: public wxEvent
2198 wxPaintEvent(int id
= 0);
2204 @class wxMaximizeEvent
2206 An event being sent when a top level window is maximized. Notice that it is
2207 not sent when the window is restored to its original size after it had been
2208 maximized, only a normal wxSizeEvent is generated in this case.
2210 Currently this event is only generated in wxMSW, wxGTK, wxOSX/Cocoa and wxOS2
2211 ports so portable programs should only rely on receiving @c wxEVT_SIZE and
2212 not necessarily this event when the window is maximized.
2214 @beginEventTable{wxMaximizeEvent}
2215 @event{EVT_MAXIMIZE(func)}
2216 Process a @c wxEVT_MAXIMIZE event.
2222 @see @ref overview_events, wxTopLevelWindow::Maximize,
2223 wxTopLevelWindow::IsMaximized
2225 class wxMaximizeEvent
: public wxEvent
2229 Constructor. Only used by wxWidgets internally.
2231 wxMaximizeEvent(int id
= 0);
2235 The possibles modes to pass to wxUpdateUIEvent::SetMode().
2239 /** Send UI update events to all windows. */
2240 wxUPDATE_UI_PROCESS_ALL
,
2242 /** Send UI update events to windows that have
2243 the wxWS_EX_PROCESS_UI_UPDATES flag specified. */
2244 wxUPDATE_UI_PROCESS_SPECIFIED
2249 @class wxUpdateUIEvent
2251 This class is used for pseudo-events which are called by wxWidgets
2252 to give an application the chance to update various user interface elements.
2254 Without update UI events, an application has to work hard to check/uncheck,
2255 enable/disable, show/hide, and set the text for elements such as menu items
2256 and toolbar buttons. The code for doing this has to be mixed up with the code
2257 that is invoked when an action is invoked for a menu item or button.
2259 With update UI events, you define an event handler to look at the state of the
2260 application and change UI elements accordingly. wxWidgets will call your member
2261 functions in idle time, so you don't have to worry where to call this code.
2263 In addition to being a clearer and more declarative method, it also means you don't
2264 have to worry whether you're updating a toolbar or menubar identifier. The same
2265 handler can update a menu item and toolbar button, if the identifier is the same.
2266 Instead of directly manipulating the menu or button, you call functions in the event
2267 object, such as wxUpdateUIEvent::Check. wxWidgets will determine whether such a
2268 call has been made, and which UI element to update.
2270 These events will work for popup menus as well as menubars. Just before a menu is
2271 popped up, wxMenu::UpdateUI is called to process any UI events for the window that
2274 If you find that the overhead of UI update processing is affecting your application,
2275 you can do one or both of the following:
2276 @li Call wxUpdateUIEvent::SetMode with a value of wxUPDATE_UI_PROCESS_SPECIFIED,
2277 and set the extra style wxWS_EX_PROCESS_UI_UPDATES for every window that should
2278 receive update events. No other windows will receive update events.
2279 @li Call wxUpdateUIEvent::SetUpdateInterval with a millisecond value to set the delay
2280 between updates. You may need to call wxWindow::UpdateWindowUI at critical points,
2281 for example when a dialog is about to be shown, in case the user sees a slight
2282 delay before windows are updated.
2284 Note that although events are sent in idle time, defining a wxIdleEvent handler
2285 for a window does not affect this because the events are sent from wxWindow::OnInternalIdle
2286 which is always called in idle time.
2288 wxWidgets tries to optimize update events on some platforms.
2289 On Windows and GTK+, events for menubar items are only sent when the menu is about
2290 to be shown, and not in idle time.
2293 @beginEventTable{wxUpdateUIEvent}
2294 @event{EVT_UPDATE_UI(id, func)}
2295 Process a @c wxEVT_UPDATE_UI event for the command with the given id.
2296 @event{EVT_UPDATE_UI_RANGE(id1, id2, func)}
2297 Process a @c wxEVT_UPDATE_UI event for any command with id included in the given range.
2303 @see @ref overview_events
2305 class wxUpdateUIEvent
: public wxCommandEvent
2311 wxUpdateUIEvent(wxWindowID commandId
= 0);
2314 Returns @true if it is appropriate to update (send UI update events to)
2317 This function looks at the mode used (see wxUpdateUIEvent::SetMode),
2318 the wxWS_EX_PROCESS_UI_UPDATES flag in @a window, the time update events
2319 were last sent in idle time, and the update interval, to determine whether
2320 events should be sent to this window now. By default this will always
2321 return @true because the update mode is initially wxUPDATE_UI_PROCESS_ALL
2322 and the interval is set to 0; so update events will be sent as often as
2323 possible. You can reduce the frequency that events are sent by changing the
2324 mode and/or setting an update interval.
2326 @see ResetUpdateTime(), SetUpdateInterval(), SetMode()
2328 static bool CanUpdate(wxWindow
* window
);
2331 Check or uncheck the UI element.
2333 void Check(bool check
);
2336 Enable or disable the UI element.
2338 void Enable(bool enable
);
2341 Returns @true if the UI element should be checked.
2343 bool GetChecked() const;
2346 Returns @true if the UI element should be enabled.
2348 bool GetEnabled() const;
2351 Static function returning a value specifying how wxWidgets will send update
2352 events: to all windows, or only to those which specify that they will process
2357 static wxUpdateUIMode
GetMode();
2360 Returns @true if the application has called Check().
2361 For wxWidgets internal use only.
2363 bool GetSetChecked() const;
2366 Returns @true if the application has called Enable().
2367 For wxWidgets internal use only.
2369 bool GetSetEnabled() const;
2372 Returns @true if the application has called Show().
2373 For wxWidgets internal use only.
2375 bool GetSetShown() const;
2378 Returns @true if the application has called SetText().
2379 For wxWidgets internal use only.
2381 bool GetSetText() const;
2384 Returns @true if the UI element should be shown.
2386 bool GetShown() const;
2389 Returns the text that should be set for the UI element.
2391 wxString
GetText() const;
2394 Returns the current interval between updates in milliseconds.
2395 The value -1 disables updates, 0 updates as frequently as possible.
2397 @see SetUpdateInterval().
2399 static long GetUpdateInterval();
2402 Used internally to reset the last-updated time to the current time.
2404 It is assumed that update events are normally sent in idle time, so this
2405 is called at the end of idle processing.
2407 @see CanUpdate(), SetUpdateInterval(), SetMode()
2409 static void ResetUpdateTime();
2412 Specify how wxWidgets will send update events: to all windows, or only to
2413 those which specify that they will process the events.
2416 this parameter may be one of the ::wxUpdateUIMode enumeration values.
2417 The default mode is wxUPDATE_UI_PROCESS_ALL.
2419 static void SetMode(wxUpdateUIMode mode
);
2422 Sets the text for this UI element.
2424 void SetText(const wxString
& text
);
2427 Sets the interval between updates in milliseconds.
2429 Set to -1 to disable updates, or to 0 to update as frequently as possible.
2432 Use this to reduce the overhead of UI update events if your application
2433 has a lot of windows. If you set the value to -1 or greater than 0,
2434 you may also need to call wxWindow::UpdateWindowUI at appropriate points
2435 in your application, such as when a dialog is about to be shown.
2437 static void SetUpdateInterval(long updateInterval
);
2440 Show or hide the UI element.
2442 void Show(bool show
);
2448 @class wxClipboardTextEvent
2450 This class represents the events generated by a control (typically a
2451 wxTextCtrl but other windows can generate these events as well) when its
2452 content gets copied or cut to, or pasted from the clipboard.
2454 There are three types of corresponding events @c wxEVT_COMMAND_TEXT_COPY,
2455 @c wxEVT_COMMAND_TEXT_CUT and @c wxEVT_COMMAND_TEXT_PASTE.
2457 If any of these events is processed (without being skipped) by an event
2458 handler, the corresponding operation doesn't take place which allows to
2459 prevent the text from being copied from or pasted to a control. It is also
2460 possible to examine the clipboard contents in the PASTE event handler and
2461 transform it in some way before inserting in a control -- for example,
2462 changing its case or removing invalid characters.
2464 Finally notice that a CUT event is always preceded by the COPY event which
2465 makes it possible to only process the latter if it doesn't matter if the
2466 text was copied or cut.
2469 These events are currently only generated by wxTextCtrl in wxGTK and wxOSX
2470 but are also generated by wxComboBox without wxCB_READONLY style in wxMSW.
2472 @beginEventTable{wxClipboardTextEvent}
2473 @event{EVT_TEXT_COPY(id, func)}
2474 Some or all of the controls content was copied to the clipboard.
2475 @event{EVT_TEXT_CUT(id, func)}
2476 Some or all of the controls content was cut (i.e. copied and
2478 @event{EVT_TEXT_PASTE(id, func)}
2479 Clipboard content was pasted into the control.
2488 class wxClipboardTextEvent
: public wxCommandEvent
2494 wxClipboardTextEvent(wxEventType commandType
= wxEVT_NULL
, int id
= 0);
2498 Possible axis values for mouse wheel scroll events.
2502 enum wxMouseWheelAxis
2504 wxMOUSE_WHEEL_VERTICAL
, ///< Vertical scroll event.
2505 wxMOUSE_WHEEL_HORIZONTAL
///< Horizontal scroll event.
2512 This event class contains information about the events generated by the mouse:
2513 they include mouse buttons press and release events and mouse move events.
2515 All mouse events involving the buttons use @c wxMOUSE_BTN_LEFT for the
2516 left mouse button, @c wxMOUSE_BTN_MIDDLE for the middle one and
2517 @c wxMOUSE_BTN_RIGHT for the right one. And if the system supports more
2518 buttons, the @c wxMOUSE_BTN_AUX1 and @c wxMOUSE_BTN_AUX2 events
2519 can also be generated. Note that not all mice have even a middle button so a
2520 portable application should avoid relying on the events from it (but the right
2521 button click can be emulated using the left mouse button with the control key
2522 under Mac platforms with a single button mouse).
2524 For the @c wxEVT_ENTER_WINDOW and @c wxEVT_LEAVE_WINDOW events
2525 purposes, the mouse is considered to be inside the window if it is in the
2526 window client area and not inside one of its children. In other words, the
2527 parent window receives @c wxEVT_LEAVE_WINDOW event not only when the
2528 mouse leaves the window entirely but also when it enters one of its children.
2530 The position associated with a mouse event is expressed in the window
2531 coordinates of the window which generated the event, you can use
2532 wxWindow::ClientToScreen() to convert it to screen coordinates and possibly
2533 call wxWindow::ScreenToClient() next to convert it to window coordinates of
2536 @note Note that under Windows CE mouse enter and leave events are not natively
2537 supported by the system but are generated by wxWidgets itself. This has several
2538 drawbacks: the LEAVE_WINDOW event might be received some time after the mouse
2539 left the window and the state variables for it may have changed during this time.
2541 @note Note the difference between methods like wxMouseEvent::LeftDown and
2542 the inherited wxMouseState::LeftIsDown: the former returns @true when
2543 the event corresponds to the left mouse button click while the latter
2544 returns @true if the left mouse button is currently being pressed.
2545 For example, when the user is dragging the mouse you can use
2546 wxMouseEvent::LeftIsDown to test whether the left mouse button is
2547 (still) depressed. Also, by convention, if wxMouseEvent::LeftDown
2548 returns @true, wxMouseEvent::LeftIsDown will also return @true in
2549 wxWidgets whatever the underlying GUI behaviour is (which is
2550 platform-dependent). The same applies, of course, to other mouse
2554 @beginEventTable{wxMouseEvent}
2555 @event{EVT_LEFT_DOWN(func)}
2556 Process a @c wxEVT_LEFT_DOWN event. The handler of this event should normally
2557 call event.Skip() to allow the default processing to take place as otherwise
2558 the window under mouse wouldn't get the focus.
2559 @event{EVT_LEFT_UP(func)}
2560 Process a @c wxEVT_LEFT_UP event.
2561 @event{EVT_LEFT_DCLICK(func)}
2562 Process a @c wxEVT_LEFT_DCLICK event.
2563 @event{EVT_MIDDLE_DOWN(func)}
2564 Process a @c wxEVT_MIDDLE_DOWN event.
2565 @event{EVT_MIDDLE_UP(func)}
2566 Process a @c wxEVT_MIDDLE_UP event.
2567 @event{EVT_MIDDLE_DCLICK(func)}
2568 Process a @c wxEVT_MIDDLE_DCLICK event.
2569 @event{EVT_RIGHT_DOWN(func)}
2570 Process a @c wxEVT_RIGHT_DOWN event.
2571 @event{EVT_RIGHT_UP(func)}
2572 Process a @c wxEVT_RIGHT_UP event.
2573 @event{EVT_RIGHT_DCLICK(func)}
2574 Process a @c wxEVT_RIGHT_DCLICK event.
2575 @event{EVT_MOUSE_AUX1_DOWN(func)}
2576 Process a @c wxEVT_AUX1_DOWN event.
2577 @event{EVT_MOUSE_AUX1_UP(func)}
2578 Process a @c wxEVT_AUX1_UP event.
2579 @event{EVT_MOUSE_AUX1_DCLICK(func)}
2580 Process a @c wxEVT_AUX1_DCLICK event.
2581 @event{EVT_MOUSE_AUX2_DOWN(func)}
2582 Process a @c wxEVT_AUX2_DOWN event.
2583 @event{EVT_MOUSE_AUX2_UP(func)}
2584 Process a @c wxEVT_AUX2_UP event.
2585 @event{EVT_MOUSE_AUX2_DCLICK(func)}
2586 Process a @c wxEVT_AUX2_DCLICK event.
2587 @event{EVT_MOTION(func)}
2588 Process a @c wxEVT_MOTION event.
2589 @event{EVT_ENTER_WINDOW(func)}
2590 Process a @c wxEVT_ENTER_WINDOW event.
2591 @event{EVT_LEAVE_WINDOW(func)}
2592 Process a @c wxEVT_LEAVE_WINDOW event.
2593 @event{EVT_MOUSEWHEEL(func)}
2594 Process a @c wxEVT_MOUSEWHEEL event.
2595 @event{EVT_MOUSE_EVENTS(func)}
2596 Process all mouse events.
2604 class wxMouseEvent
: public wxEvent
,
2609 Constructor. Valid event types are:
2611 @li @c wxEVT_ENTER_WINDOW
2612 @li @c wxEVT_LEAVE_WINDOW
2613 @li @c wxEVT_LEFT_DOWN
2614 @li @c wxEVT_LEFT_UP
2615 @li @c wxEVT_LEFT_DCLICK
2616 @li @c wxEVT_MIDDLE_DOWN
2617 @li @c wxEVT_MIDDLE_UP
2618 @li @c wxEVT_MIDDLE_DCLICK
2619 @li @c wxEVT_RIGHT_DOWN
2620 @li @c wxEVT_RIGHT_UP
2621 @li @c wxEVT_RIGHT_DCLICK
2622 @li @c wxEVT_AUX1_DOWN
2623 @li @c wxEVT_AUX1_UP
2624 @li @c wxEVT_AUX1_DCLICK
2625 @li @c wxEVT_AUX2_DOWN
2626 @li @c wxEVT_AUX2_UP
2627 @li @c wxEVT_AUX2_DCLICK
2629 @li @c wxEVT_MOUSEWHEEL
2631 wxMouseEvent(wxEventType mouseEventType
= wxEVT_NULL
);
2634 Returns @true if the event was a first extra button double click.
2636 bool Aux1DClick() const;
2639 Returns @true if the first extra button mouse button changed to down.
2641 bool Aux1Down() const;
2644 Returns @true if the first extra button mouse button changed to up.
2646 bool Aux1Up() const;
2649 Returns @true if the event was a second extra button double click.
2651 bool Aux2DClick() const;
2654 Returns @true if the second extra button mouse button changed to down.
2656 bool Aux2Down() const;
2659 Returns @true if the second extra button mouse button changed to up.
2661 bool Aux2Up() const;
2664 Returns @true if the event was generated by the specified button.
2666 @see wxMouseState::ButtoinIsDown()
2668 bool Button(wxMouseButton but
) const;
2671 If the argument is omitted, this returns @true if the event was a mouse
2672 double click event. Otherwise the argument specifies which double click event
2673 was generated (see Button() for the possible values).
2675 bool ButtonDClick(wxMouseButton but
= wxMOUSE_BTN_ANY
) const;
2678 If the argument is omitted, this returns @true if the event was a mouse
2679 button down event. Otherwise the argument specifies which button-down event
2680 was generated (see Button() for the possible values).
2682 bool ButtonDown(wxMouseButton but
= wxMOUSE_BTN_ANY
) const;
2685 If the argument is omitted, this returns @true if the event was a mouse
2686 button up event. Otherwise the argument specifies which button-up event
2687 was generated (see Button() for the possible values).
2689 bool ButtonUp(wxMouseButton but
= wxMOUSE_BTN_ANY
) const;
2692 Returns @true if this was a dragging event (motion while a button is depressed).
2696 bool Dragging() const;
2699 Returns @true if the mouse was entering the window.
2703 bool Entering() const;
2706 Returns the mouse button which generated this event or @c wxMOUSE_BTN_NONE
2707 if no button is involved (for mouse move, enter or leave event, for example).
2708 Otherwise @c wxMOUSE_BTN_LEFT is returned for the left button down, up and
2709 double click events, @c wxMOUSE_BTN_MIDDLE and @c wxMOUSE_BTN_RIGHT
2710 for the same events for the middle and the right buttons respectively.
2712 int GetButton() const;
2715 Returns the number of mouse clicks for this event: 1 for a simple click, 2
2716 for a double-click, 3 for a triple-click and so on.
2718 Currently this function is implemented only in wxMac and returns -1 for the
2719 other platforms (you can still distinguish simple clicks from double-clicks as
2720 they generate different kinds of events however).
2724 int GetClickCount() const;
2727 Returns the configured number of lines (or whatever) to be scrolled per
2728 wheel action. Defaults to three.
2730 int GetLinesPerAction() const;
2733 Returns the logical mouse position in pixels (i.e.\ translated according to the
2734 translation set for the DC, which usually indicates that the window has been
2737 wxPoint
GetLogicalPosition(const wxDC
& dc
) const;
2740 Get wheel delta, normally 120.
2742 This is the threshold for action to be taken, and one such action
2743 (for example, scrolling one increment) should occur for each delta.
2745 int GetWheelDelta() const;
2748 Get wheel rotation, positive or negative indicates direction of rotation.
2750 Current devices all send an event when rotation is at least +/-WheelDelta, but
2751 finer resolution devices can be created in the future.
2753 Because of this you shouldn't assume that one event is equal to 1 line, but you
2754 should be able to either do partial line scrolling or wait until several
2755 events accumulate before scrolling.
2757 int GetWheelRotation() const;
2760 Gets the axis the wheel operation concerns.
2762 Usually the mouse wheel is used to scroll vertically so @c
2763 wxMOUSE_WHEEL_VERTICAL is returned but some mice (and most trackpads)
2764 also allow to use the wheel to scroll horizontally in which case
2765 @c wxMOUSE_WHEEL_HORIZONTAL is returned.
2767 Notice that before wxWidgets 2.9.4 this method returned @c int.
2769 wxMouseWheelAxis
GetWheelAxis() const;
2772 Returns @true if the event was a mouse button event (not necessarily a button
2773 down event - that may be tested using ButtonDown()).
2775 bool IsButton() const;
2778 Returns @true if the system has been setup to do page scrolling with
2779 the mouse wheel instead of line scrolling.
2781 bool IsPageScroll() const;
2784 Returns @true if the mouse was leaving the window.
2788 bool Leaving() const;
2791 Returns @true if the event was a left double click.
2793 bool LeftDClick() const;
2796 Returns @true if the left mouse button changed to down.
2798 bool LeftDown() const;
2801 Returns @true if the left mouse button changed to up.
2803 bool LeftUp() const;
2806 Returns @true if the Meta key was down at the time of the event.
2808 bool MetaDown() const;
2811 Returns @true if the event was a middle double click.
2813 bool MiddleDClick() const;
2816 Returns @true if the middle mouse button changed to down.
2818 bool MiddleDown() const;
2821 Returns @true if the middle mouse button changed to up.
2823 bool MiddleUp() const;
2826 Returns @true if this was a motion event and no mouse buttons were pressed.
2827 If any mouse button is held pressed, then this method returns @false and
2828 Dragging() returns @true.
2830 bool Moving() const;
2833 Returns @true if the event was a right double click.
2835 bool RightDClick() const;
2838 Returns @true if the right mouse button changed to down.
2840 bool RightDown() const;
2843 Returns @true if the right mouse button changed to up.
2845 bool RightUp() const;
2851 @class wxDropFilesEvent
2853 This class is used for drop files events, that is, when files have been dropped
2854 onto the window. This functionality is currently only available under Windows.
2856 The window must have previously been enabled for dropping by calling
2857 wxWindow::DragAcceptFiles().
2859 Important note: this is a separate implementation to the more general drag and drop
2860 implementation documented in the @ref overview_dnd. It uses the older, Windows
2861 message-based approach of dropping files.
2863 @beginEventTable{wxDropFilesEvent}
2864 @event{EVT_DROP_FILES(func)}
2865 Process a @c wxEVT_DROP_FILES event.
2873 @see @ref overview_events
2875 class wxDropFilesEvent
: public wxEvent
2881 wxDropFilesEvent(wxEventType id
= 0, int noFiles
= 0,
2882 wxString
* files
= NULL
);
2885 Returns an array of filenames.
2887 wxString
* GetFiles() const;
2890 Returns the number of files dropped.
2892 int GetNumberOfFiles() const;
2895 Returns the position at which the files were dropped.
2896 Returns an array of filenames.
2898 wxPoint
GetPosition() const;
2904 @class wxActivateEvent
2906 An activate event is sent when a window or application is being activated
2909 @beginEventTable{wxActivateEvent}
2910 @event{EVT_ACTIVATE(func)}
2911 Process a @c wxEVT_ACTIVATE event.
2912 @event{EVT_ACTIVATE_APP(func)}
2913 Process a @c wxEVT_ACTIVATE_APP event.
2914 This event is received by the wxApp-derived instance only.
2915 @event{EVT_HIBERNATE(func)}
2916 Process a hibernate event, supplying the member function. This event applies
2917 to wxApp only, and only on Windows SmartPhone and PocketPC.
2918 It is generated when the system is low on memory; the application should free
2919 up as much memory as possible, and restore full working state when it receives
2920 a @c wxEVT_ACTIVATE or @c wxEVT_ACTIVATE_APP event.
2926 @see @ref overview_events, wxApp::IsActive
2928 class wxActivateEvent
: public wxEvent
2934 wxActivateEvent(wxEventType eventType
= wxEVT_NULL
, bool active
= true,
2938 Returns @true if the application or window is being activated, @false otherwise.
2940 bool GetActive() const;
2946 @class wxContextMenuEvent
2948 This class is used for context menu events, sent to give
2949 the application a chance to show a context (popup) menu for a wxWindow.
2951 Note that if wxContextMenuEvent::GetPosition returns wxDefaultPosition, this
2952 means that the event originated from a keyboard context button event, and you
2953 should compute a suitable position yourself, for example by calling wxGetMousePosition().
2955 Notice that the exact sequence of mouse events is different across the
2956 platforms. For example, under MSW the context menu event is generated after
2957 @c EVT_RIGHT_UP event and only if it was not handled but under GTK the
2958 context menu event is generated after @c EVT_RIGHT_DOWN event. This is
2959 correct in the sense that it ensures that the context menu is shown
2960 according to the current platform UI conventions and also means that you
2961 must not handle (or call wxEvent::Skip() in your handler if you do have
2962 one) neither right mouse down nor right mouse up event if you plan on
2963 handling @c EVT_CONTEXT_MENU event.
2965 @beginEventTable{wxContextMenuEvent}
2966 @event{EVT_CONTEXT_MENU(func)}
2967 A right click (or other context menu command depending on platform) has been detected.
2974 @see wxCommandEvent, @ref overview_events
2976 class wxContextMenuEvent
: public wxCommandEvent
2982 wxContextMenuEvent(wxEventType type
= wxEVT_NULL
, int id
= 0,
2983 const wxPoint
& pos
= wxDefaultPosition
);
2986 Returns the position in screen coordinates at which the menu should be shown.
2987 Use wxWindow::ScreenToClient to convert to client coordinates.
2989 You can also omit a position from wxWindow::PopupMenu in order to use
2990 the current mouse pointer position.
2992 If the event originated from a keyboard event, the value returned from this
2993 function will be wxDefaultPosition.
2995 const wxPoint
& GetPosition() const;
2998 Sets the position at which the menu should be shown.
3000 void SetPosition(const wxPoint
& point
);
3008 An erase event is sent when a window's background needs to be repainted.
3010 On some platforms, such as GTK+, this event is simulated (simply generated just
3011 before the paint event) and may cause flicker. It is therefore recommended that
3012 you set the text background colour explicitly in order to prevent flicker.
3013 The default background colour under GTK+ is grey.
3015 To intercept this event, use the EVT_ERASE_BACKGROUND macro in an event table
3018 You must use the device context returned by GetDC() to draw on, don't create
3019 a wxPaintDC in the event handler.
3021 @beginEventTable{wxEraseEvent}
3022 @event{EVT_ERASE_BACKGROUND(func)}
3023 Process a @c wxEVT_ERASE_BACKGROUND event.
3029 @see @ref overview_events
3031 class wxEraseEvent
: public wxEvent
3037 wxEraseEvent(int id
= 0, wxDC
* dc
= NULL
);
3040 Returns the device context associated with the erase event to draw on.
3042 The returned pointer is never @NULL.
3044 wxDC
* GetDC() const;
3052 A focus event is sent when a window's focus changes. The window losing focus
3053 receives a "kill focus" event while the window gaining it gets a "set focus" one.
3055 Notice that the set focus event happens both when the user gives focus to the
3056 window (whether using the mouse or keyboard) and when it is done from the
3057 program itself using wxWindow::SetFocus.
3059 The focus event handlers should almost invariably call wxEvent::Skip() on
3060 their event argument to allow the default handling to take place. Failure
3061 to do this may result in incorrect behaviour of the native controls. Also
3062 note that wxEVT_KILL_FOCUS handler must not call wxWindow::SetFocus() as
3063 this, again, is not supported by all native controls. If you need to do
3064 this, consider using the @ref sec_delayed_action described in wxIdleEvent
3067 @beginEventTable{wxFocusEvent}
3068 @event{EVT_SET_FOCUS(func)}
3069 Process a @c wxEVT_SET_FOCUS event.
3070 @event{EVT_KILL_FOCUS(func)}
3071 Process a @c wxEVT_KILL_FOCUS event.
3077 @see @ref overview_events
3079 class wxFocusEvent
: public wxEvent
3085 wxFocusEvent(wxEventType eventType
= wxEVT_NULL
, int id
= 0);
3088 Returns the window associated with this event, that is the window which had the
3089 focus before for the @c wxEVT_SET_FOCUS event and the window which is
3090 going to receive focus for the @c wxEVT_KILL_FOCUS one.
3092 Warning: the window pointer may be @NULL!
3094 wxWindow
*GetWindow() const;
3096 void SetWindow(wxWindow
*win
);
3102 @class wxChildFocusEvent
3104 A child focus event is sent to a (parent-)window when one of its child windows
3105 gains focus, so that the window could restore the focus back to its corresponding
3106 child if it loses it now and regains later.
3108 Notice that child window is the direct child of the window receiving event.
3109 Use wxWindow::FindFocus() to retrieve the window which is actually getting focus.
3111 @beginEventTable{wxChildFocusEvent}
3112 @event{EVT_CHILD_FOCUS(func)}
3113 Process a @c wxEVT_CHILD_FOCUS event.
3119 @see @ref overview_events
3121 class wxChildFocusEvent
: public wxCommandEvent
3128 The direct child which is (or which contains the window which is) receiving
3131 wxChildFocusEvent(wxWindow
* win
= NULL
);
3134 Returns the direct child which receives the focus, or a (grand-)parent of the
3135 control receiving the focus.
3137 To get the actually focused control use wxWindow::FindFocus.
3139 wxWindow
*GetWindow() const;
3145 @class wxMouseCaptureLostEvent
3147 A mouse capture lost event is sent to a window that had obtained mouse capture,
3148 which was subsequently lost due to an "external" event (for example, when a dialog
3149 box is shown or if another application captures the mouse).
3151 If this happens, this event is sent to all windows that are on the capture stack
3152 (i.e. called CaptureMouse, but didn't call ReleaseMouse yet). The event is
3153 not sent if the capture changes because of a call to CaptureMouse or
3156 This event is currently emitted under Windows only.
3158 @beginEventTable{wxMouseCaptureLostEvent}
3159 @event{EVT_MOUSE_CAPTURE_LOST(func)}
3160 Process a @c wxEVT_MOUSE_CAPTURE_LOST event.
3168 @see wxMouseCaptureChangedEvent, @ref overview_events,
3169 wxWindow::CaptureMouse, wxWindow::ReleaseMouse, wxWindow::GetCapture
3171 class wxMouseCaptureLostEvent
: public wxEvent
3177 wxMouseCaptureLostEvent(wxWindowID windowId
= 0);
3182 class wxDisplayChangedEvent
: public wxEvent
3185 wxDisplayChangedEvent();
3189 class wxPaletteChangedEvent
: public wxEvent
3192 wxPaletteChangedEvent(wxWindowID winid
= 0);
3194 void SetChangedWindow(wxWindow
* win
);
3195 wxWindow
* GetChangedWindow() const;
3199 class wxQueryNewPaletteEvent
: public wxEvent
3202 wxQueryNewPaletteEvent(wxWindowID winid
= 0);
3204 void SetPaletteRealized(bool realized
);
3205 bool GetPaletteRealized();
3212 @class wxNotifyEvent
3214 This class is not used by the event handlers by itself, but is a base class
3215 for other event classes (such as wxBookCtrlEvent).
3217 It (or an object of a derived class) is sent when the controls state is being
3218 changed and allows the program to wxNotifyEvent::Veto() this change if it wants
3219 to prevent it from happening.
3224 @see wxBookCtrlEvent
3226 class wxNotifyEvent
: public wxCommandEvent
3230 Constructor (used internally by wxWidgets only).
3232 wxNotifyEvent(wxEventType eventType
= wxEVT_NULL
, int id
= 0);
3235 This is the opposite of Veto(): it explicitly allows the event to be processed.
3236 For most events it is not necessary to call this method as the events are allowed
3237 anyhow but some are forbidden by default (this will be mentioned in the corresponding
3243 Returns @true if the change is allowed (Veto() hasn't been called) or @false
3244 otherwise (if it was).
3246 bool IsAllowed() const;
3249 Prevents the change announced by this event from happening.
3251 It is in general a good idea to notify the user about the reasons for vetoing
3252 the change because otherwise the applications behaviour (which just refuses to
3253 do what the user wants) might be quite surprising.
3260 @class wxThreadEvent
3262 This class adds some simple functionality to wxEvent to facilitate
3263 inter-thread communication.
3265 This event is not natively emitted by any control/class: it is just
3266 a helper class for the user.
3267 Its most important feature is the GetEventCategory() implementation which
3268 allows thread events @b NOT to be processed by wxEventLoopBase::YieldFor calls
3269 (unless the @c wxEVT_CATEGORY_THREAD is specified - which is never in wx code).
3272 @category{events,threading}
3274 @see @ref overview_thread, wxEventLoopBase::YieldFor
3278 class wxThreadEvent
: public wxEvent
3284 wxThreadEvent(wxEventType eventType
= wxEVT_THREAD
, int id
= wxID_ANY
);
3287 Clones this event making sure that all internal members which use
3288 COW (only @c m_commandString for now; see @ref overview_refcount)
3289 are unshared (see wxObject::UnShare).
3291 virtual wxEvent
*Clone() const;
3294 Returns @c wxEVT_CATEGORY_THREAD.
3296 This is important to avoid unwanted processing of thread events
3297 when calling wxEventLoopBase::YieldFor().
3299 virtual wxEventCategory
GetEventCategory() const;
3302 Sets custom data payload.
3304 The @a payload argument may be of any type that wxAny can handle
3305 (i.e. pretty much anything). Note that T's copy constructor must be
3306 thread-safe, i.e. create a copy that doesn't share anything with
3307 the original (see Clone()).
3309 @note This method is not available with Visual C++ 6.
3313 @see GetPayload(), wxAny
3315 template<typename T
>
3316 void SetPayload(const T
& payload
);
3319 Get custom data payload.
3321 Correct type is checked in debug builds.
3323 @note This method is not available with Visual C++ 6.
3327 @see SetPayload(), wxAny
3329 template<typename T
>
3330 T
GetPayload() const;
3333 Returns extra information integer value.
3335 long GetExtraLong() const;
3338 Returns stored integer value.
3343 Returns stored string value.
3345 wxString
GetString() const;
3349 Sets the extra information value.
3351 void SetExtraLong(long extraLong
);
3354 Sets the integer value.
3356 void SetInt(int intCommand
);
3359 Sets the string value.
3361 void SetString(const wxString
& string
);
3368 A help event is sent when the user has requested context-sensitive help.
3369 This can either be caused by the application requesting context-sensitive help mode
3370 via wxContextHelp, or (on MS Windows) by the system generating a WM_HELP message when
3371 the user pressed F1 or clicked on the query button in a dialog caption.
3373 A help event is sent to the window that the user clicked on, and is propagated
3374 up the window hierarchy until the event is processed or there are no more event
3377 The application should call wxEvent::GetId to check the identity of the
3378 clicked-on window, and then either show some suitable help or call wxEvent::Skip()
3379 if the identifier is unrecognised.
3381 Calling Skip is important because it allows wxWidgets to generate further
3382 events for ancestors of the clicked-on window. Otherwise it would be impossible to
3383 show help for container windows, since processing would stop after the first window
3386 @beginEventTable{wxHelpEvent}
3387 @event{EVT_HELP(id, func)}
3388 Process a @c wxEVT_HELP event.
3389 @event{EVT_HELP_RANGE(id1, id2, func)}
3390 Process a @c wxEVT_HELP event for a range of ids.
3396 @see wxContextHelp, wxDialog, @ref overview_events
3398 class wxHelpEvent
: public wxCommandEvent
3402 Indicates how a wxHelpEvent was generated.
3406 Origin_Unknown
, /**< unrecognized event source. */
3407 Origin_Keyboard
, /**< event generated from F1 key press. */
3409 /** event generated by wxContextHelp or from the [?] button on
3410 the title bar (Windows). */
3417 wxHelpEvent(wxEventType type
= wxEVT_NULL
,
3418 wxWindowID winid
= 0,
3419 const wxPoint
& pt
= wxDefaultPosition
,
3420 wxHelpEvent::Origin origin
= Origin_Unknown
);
3423 Returns the origin of the help event which is one of the ::wxHelpEventOrigin
3426 The application may handle events generated using the keyboard or mouse
3427 differently, e.g. by using wxGetMousePosition() for the mouse events.
3431 wxHelpEvent::Origin
GetOrigin() const;
3434 Returns the left-click position of the mouse, in screen coordinates.
3435 This allows the application to position the help appropriately.
3437 const wxPoint
& GetPosition() const;
3440 Set the help event origin, only used internally by wxWidgets normally.
3444 void SetOrigin(wxHelpEvent::Origin origin
);
3447 Sets the left-click position of the mouse, in screen coordinates.
3449 void SetPosition(const wxPoint
& pt
);
3455 @class wxScrollEvent
3457 A scroll event holds information about events sent from stand-alone
3458 scrollbars (see wxScrollBar) and sliders (see wxSlider).
3460 Note that scrolled windows send the wxScrollWinEvent which does not derive from
3461 wxCommandEvent, but from wxEvent directly - don't confuse these two kinds of
3462 events and use the event table macros mentioned below only for the scrollbar-like
3465 @section scrollevent_diff The difference between EVT_SCROLL_THUMBRELEASE and EVT_SCROLL_CHANGED
3467 The EVT_SCROLL_THUMBRELEASE event is only emitted when actually dragging the thumb
3468 using the mouse and releasing it (This EVT_SCROLL_THUMBRELEASE event is also followed
3469 by an EVT_SCROLL_CHANGED event).
3471 The EVT_SCROLL_CHANGED event also occurs when using the keyboard to change the thumb
3472 position, and when clicking next to the thumb (In all these cases the EVT_SCROLL_THUMBRELEASE
3473 event does not happen).
3475 In short, the EVT_SCROLL_CHANGED event is triggered when scrolling/ moving has finished
3476 independently of the way it had started. Please see the widgets sample ("Slider" page)
3477 to see the difference between EVT_SCROLL_THUMBRELEASE and EVT_SCROLL_CHANGED in action.
3480 Note that unless specifying a scroll control identifier, you will need to test for scrollbar
3481 orientation with wxScrollEvent::GetOrientation, since horizontal and vertical scroll events
3482 are processed using the same event handler.
3484 @beginEventTable{wxScrollEvent}
3485 You can use EVT_COMMAND_SCROLL... macros with window IDs for when intercepting
3486 scroll events from controls, or EVT_SCROLL... macros without window IDs for
3487 intercepting scroll events from the receiving window -- except for this, the
3488 macros behave exactly the same.
3489 @event{EVT_SCROLL(func)}
3490 Process all scroll events.
3491 @event{EVT_SCROLL_TOP(func)}
3492 Process @c wxEVT_SCROLL_TOP scroll-to-top events (minimum position).
3493 @event{EVT_SCROLL_BOTTOM(func)}
3494 Process @c wxEVT_SCROLL_BOTTOM scroll-to-bottom events (maximum position).
3495 @event{EVT_SCROLL_LINEUP(func)}
3496 Process @c wxEVT_SCROLL_LINEUP line up events.
3497 @event{EVT_SCROLL_LINEDOWN(func)}
3498 Process @c wxEVT_SCROLL_LINEDOWN line down events.
3499 @event{EVT_SCROLL_PAGEUP(func)}
3500 Process @c wxEVT_SCROLL_PAGEUP page up events.
3501 @event{EVT_SCROLL_PAGEDOWN(func)}
3502 Process @c wxEVT_SCROLL_PAGEDOWN page down events.
3503 @event{EVT_SCROLL_THUMBTRACK(func)}
3504 Process @c wxEVT_SCROLL_THUMBTRACK thumbtrack events (frequent events sent as the
3505 user drags the thumbtrack).
3506 @event{EVT_SCROLL_THUMBRELEASE(func)}
3507 Process @c wxEVT_SCROLL_THUMBRELEASE thumb release events.
3508 @event{EVT_SCROLL_CHANGED(func)}
3509 Process @c wxEVT_SCROLL_CHANGED end of scrolling events (MSW only).
3510 @event{EVT_COMMAND_SCROLL(id, func)}
3511 Process all scroll events.
3512 @event{EVT_COMMAND_SCROLL_TOP(id, func)}
3513 Process @c wxEVT_SCROLL_TOP scroll-to-top events (minimum position).
3514 @event{EVT_COMMAND_SCROLL_BOTTOM(id, func)}
3515 Process @c wxEVT_SCROLL_BOTTOM scroll-to-bottom events (maximum position).
3516 @event{EVT_COMMAND_SCROLL_LINEUP(id, func)}
3517 Process @c wxEVT_SCROLL_LINEUP line up events.
3518 @event{EVT_COMMAND_SCROLL_LINEDOWN(id, func)}
3519 Process @c wxEVT_SCROLL_LINEDOWN line down events.
3520 @event{EVT_COMMAND_SCROLL_PAGEUP(id, func)}
3521 Process @c wxEVT_SCROLL_PAGEUP page up events.
3522 @event{EVT_COMMAND_SCROLL_PAGEDOWN(id, func)}
3523 Process @c wxEVT_SCROLL_PAGEDOWN page down events.
3524 @event{EVT_COMMAND_SCROLL_THUMBTRACK(id, func)}
3525 Process @c wxEVT_SCROLL_THUMBTRACK thumbtrack events (frequent events sent
3526 as the user drags the thumbtrack).
3527 @event{EVT_COMMAND_SCROLL_THUMBRELEASE(func)}
3528 Process @c wxEVT_SCROLL_THUMBRELEASE thumb release events.
3529 @event{EVT_COMMAND_SCROLL_CHANGED(func)}
3530 Process @c wxEVT_SCROLL_CHANGED end of scrolling events (MSW only).
3536 @see wxScrollBar, wxSlider, wxSpinButton, wxScrollWinEvent, @ref overview_events
3538 class wxScrollEvent
: public wxCommandEvent
3544 wxScrollEvent(wxEventType commandType
= wxEVT_NULL
, int id
= 0, int pos
= 0,
3545 int orientation
= 0);
3548 Returns wxHORIZONTAL or wxVERTICAL, depending on the orientation of the
3551 int GetOrientation() const;
3554 Returns the position of the scrollbar.
3556 int GetPosition() const;
3559 void SetOrientation(int orient
);
3560 void SetPosition(int pos
);
3568 See wxIdleEvent::SetMode() for more info.
3572 /** Send idle events to all windows */
3575 /** Send idle events to windows that have the wxWS_EX_PROCESS_IDLE flag specified */
3576 wxIDLE_PROCESS_SPECIFIED
3583 This class is used for idle events, which are generated when the system becomes
3584 idle. Note that, unless you do something specifically, the idle events are not
3585 sent if the system remains idle once it has become it, e.g. only a single idle
3586 event will be generated until something else resulting in more normal events
3587 happens and only then is the next idle event sent again.
3589 If you need to ensure a continuous stream of idle events, you can either use
3590 wxIdleEvent::RequestMore method in your handler or call wxWakeUpIdle() periodically
3591 (for example from a timer event handler), but note that both of these approaches
3592 (and especially the first one) increase the system load and so should be avoided
3595 By default, idle events are sent to all windows, including even the hidden
3596 ones because they may be shown if some condition is met from their @c
3597 wxEVT_IDLE (or related @c wxEVT_UPDATE_UI) handler. The children of hidden
3598 windows do not receive idle events however as they can't change their state
3599 in any way noticeable by the user. Finally, the global wxApp object also
3600 receives these events, as usual, so it can be used for any global idle time
3603 If sending idle events to all windows is causing a significant overhead in
3604 your application, you can call wxIdleEvent::SetMode with the value
3605 wxIDLE_PROCESS_SPECIFIED, and set the wxWS_EX_PROCESS_IDLE extra window
3606 style for every window which should receive idle events, all the other ones
3607 will not receive them in this case.
3609 @beginEventTable{wxIdleEvent}
3610 @event{EVT_IDLE(func)}
3611 Process a @c wxEVT_IDLE event.
3617 @section sec_delayed_action Delayed Action Mechanism
3619 wxIdleEvent can be used to perform some action "at slightly later time".
3620 This can be necessary in several circumstances when, for whatever reason,
3621 something can't be done in the current event handler. For example, if a
3622 mouse event handler is called with the mouse button pressed, the mouse can
3623 be currently captured and some operations with it -- notably capturing it
3624 again -- might be impossible or lead to undesirable results. If you still
3625 want to capture it, you can do it from @c wxEVT_IDLE handler when it is
3626 called the next time instead of doing it immediately.
3628 This can be achieved in two different ways: when using static event tables,
3629 you will need a flag indicating to the (always connected) idle event
3630 handler whether the desired action should be performed. The originally
3631 called handler would then set it to indicate that it should indeed be done
3632 and the idle handler itself would reset it to prevent it from doing the
3635 Using dynamically connected event handlers things are even simpler as the
3636 original event handler can simply wxEvtHandler::Connect() or
3637 wxEvtHandler::Bind() the idle event handler which would only be executed
3638 then and could wxEvtHandler::Disconnect() or wxEvtHandler::Unbind() itself.
3641 @see @ref overview_events, wxUpdateUIEvent, wxWindow::OnInternalIdle
3643 class wxIdleEvent
: public wxEvent
3652 Static function returning a value specifying how wxWidgets will send idle
3653 events: to all windows, or only to those which specify that they
3654 will process the events.
3658 static wxIdleMode
GetMode();
3661 Returns @true if the OnIdle function processing this event requested more
3666 bool MoreRequested() const;
3669 Tells wxWidgets that more processing is required.
3671 This function can be called by an OnIdle handler for a window or window event
3672 handler to indicate that wxApp::OnIdle should forward the OnIdle event once
3673 more to the application windows.
3675 If no window calls this function during OnIdle, then the application will
3676 remain in a passive event loop (not calling OnIdle) until a new event is
3677 posted to the application by the windowing system.
3679 @see MoreRequested()
3681 void RequestMore(bool needMore
= true);
3684 Static function for specifying how wxWidgets will send idle events: to
3685 all windows, or only to those which specify that they will process the events.
3688 Can be one of the ::wxIdleMode values.
3689 The default is wxIDLE_PROCESS_ALL.
3691 static void SetMode(wxIdleMode mode
);
3694 #endif // wxUSE_BASE
3699 @class wxInitDialogEvent
3701 A wxInitDialogEvent is sent as a dialog or panel is being initialised.
3702 Handlers for this event can transfer data to the window.
3704 The default handler calls wxWindow::TransferDataToWindow.
3706 @beginEventTable{wxInitDialogEvent}
3707 @event{EVT_INIT_DIALOG(func)}
3708 Process a @c wxEVT_INIT_DIALOG event.
3714 @see @ref overview_events
3716 class wxInitDialogEvent
: public wxEvent
3722 wxInitDialogEvent(int id
= 0);
3728 @class wxWindowDestroyEvent
3730 This event is sent as early as possible during the window destruction
3733 For the top level windows, as early as possible means that this is done by
3734 wxFrame or wxDialog destructor, i.e. after the destructor of the derived
3735 class was executed and so any methods specific to the derived class can't
3736 be called any more from this event handler. If you need to do this, you
3737 must call wxWindow::SendDestroyEvent() from your derived class destructor.
3739 For the child windows, this event is generated just before deleting the
3740 window from wxWindow::Destroy() (which is also called when the parent
3741 window is deleted) or from the window destructor if operator @c delete was
3742 used directly (which is not recommended for this very reason).
3744 It is usually pointless to handle this event in the window itself but it ca
3745 be very useful to receive notifications about the window destruction in the
3746 parent window or in any other object interested in this window.
3751 @see @ref overview_events, wxWindowCreateEvent
3753 class wxWindowDestroyEvent
: public wxCommandEvent
3759 wxWindowDestroyEvent(wxWindow
* win
= NULL
);
3761 /// Return the window being destroyed.
3762 wxWindow
*GetWindow() const;
3767 @class wxNavigationKeyEvent
3769 This event class contains information about navigation events,
3770 generated by navigation keys such as tab and page down.
3772 This event is mainly used by wxWidgets implementations.
3773 A wxNavigationKeyEvent handler is automatically provided by wxWidgets
3774 when you enable keyboard navigation inside a window by inheriting it from
3775 wxNavigationEnabled<>.
3777 @beginEventTable{wxNavigationKeyEvent}
3778 @event{EVT_NAVIGATION_KEY(func)}
3779 Process a navigation key event.
3785 @see wxWindow::Navigate, wxWindow::NavigateIn
3787 class wxNavigationKeyEvent
: public wxEvent
3791 Flags which can be used with wxNavigationKeyEvent.
3793 enum wxNavigationKeyEventFlags
3795 IsBackward
= 0x0000,
3801 wxNavigationKeyEvent();
3802 wxNavigationKeyEvent(const wxNavigationKeyEvent
& event
);
3805 Returns the child that has the focus, or @NULL.
3807 wxWindow
* GetCurrentFocus() const;
3810 Returns @true if the navigation was in the forward direction.
3812 bool GetDirection() const;
3815 Returns @true if the navigation event was from a tab key.
3816 This is required for proper navigation over radio buttons.
3818 bool IsFromTab() const;
3821 Returns @true if the navigation event represents a window change
3822 (for example, from Ctrl-Page Down in a notebook).
3824 bool IsWindowChange() const;
3827 Sets the current focus window member.
3829 void SetCurrentFocus(wxWindow
* currentFocus
);
3832 Sets the direction to forward if @a direction is @true, or backward
3835 void SetDirection(bool direction
);
3838 Sets the flags for this event.
3839 The @a flags can be a combination of the ::wxNavigationKeyEventFlags values.
3841 void SetFlags(long flags
);
3844 Marks the navigation event as from a tab key.
3846 void SetFromTab(bool fromTab
);
3849 Marks the event as a window change event.
3851 void SetWindowChange(bool windowChange
);
3857 @class wxMouseCaptureChangedEvent
3859 An mouse capture changed event is sent to a window that loses its
3860 mouse capture. This is called even if wxWindow::ReleaseMouse
3861 was called by the application code. Handling this event allows
3862 an application to cater for unexpected capture releases which
3863 might otherwise confuse mouse handling code.
3867 @beginEventTable{wxMouseCaptureChangedEvent}
3868 @event{EVT_MOUSE_CAPTURE_CHANGED(func)}
3869 Process a @c wxEVT_MOUSE_CAPTURE_CHANGED event.
3875 @see wxMouseCaptureLostEvent, @ref overview_events,
3876 wxWindow::CaptureMouse, wxWindow::ReleaseMouse, wxWindow::GetCapture
3878 class wxMouseCaptureChangedEvent
: public wxEvent
3884 wxMouseCaptureChangedEvent(wxWindowID windowId
= 0,
3885 wxWindow
* gainedCapture
= NULL
);
3888 Returns the window that gained the capture, or @NULL if it was a
3889 non-wxWidgets window.
3891 wxWindow
* GetCapturedWindow() const;
3899 This event class contains information about window and session close events.
3901 The handler function for EVT_CLOSE is called when the user has tried to close a
3902 a frame or dialog box using the window manager (X) or system menu (Windows).
3903 It can also be invoked by the application itself programmatically, for example by
3904 calling the wxWindow::Close function.
3906 You should check whether the application is forcing the deletion of the window
3907 using wxCloseEvent::CanVeto. If this is @false, you @e must destroy the window
3908 using wxWindow::Destroy.
3910 If the return value is @true, it is up to you whether you respond by destroying
3913 If you don't destroy the window, you should call wxCloseEvent::Veto to
3914 let the calling code know that you did not destroy the window.
3915 This allows the wxWindow::Close function to return @true or @false depending
3916 on whether the close instruction was honoured or not.
3918 Example of a wxCloseEvent handler:
3921 void MyFrame::OnClose(wxCloseEvent& event)
3923 if ( event.CanVeto() && m_bFileNotSaved )
3925 if ( wxMessageBox("The file has not been saved... continue closing?",
3927 wxICON_QUESTION | wxYES_NO) != wxYES )
3934 Destroy(); // you may also do: event.Skip();
3935 // since the default event handler does call Destroy(), too
3939 The EVT_END_SESSION event is slightly different as it is sent by the system
3940 when the user session is ending (e.g. because of log out or shutdown) and
3941 so all windows are being forcefully closed. At least under MSW, after the
3942 handler for this event is executed the program is simply killed by the
3943 system. Because of this, the default handler for this event provided by
3944 wxWidgets calls all the usual cleanup code (including wxApp::OnExit()) so
3945 that it could still be executed and exit()s the process itself, without
3946 waiting for being killed. If this behaviour is for some reason undesirable,
3947 make sure that you define a handler for this event in your wxApp-derived
3948 class and do not call @c event.Skip() in it (but be aware that the system
3949 will still kill your application).
3951 @beginEventTable{wxCloseEvent}
3952 @event{EVT_CLOSE(func)}
3953 Process a @c wxEVT_CLOSE_WINDOW command event, supplying the member function.
3954 This event applies to wxFrame and wxDialog classes.
3955 @event{EVT_QUERY_END_SESSION(func)}
3956 Process a @c wxEVT_QUERY_END_SESSION session event, supplying the member function.
3957 This event can be handled in wxApp-derived class only.
3958 @event{EVT_END_SESSION(func)}
3959 Process a @c wxEVT_END_SESSION session event, supplying the member function.
3960 This event can be handled in wxApp-derived class only.
3966 @see wxWindow::Close, @ref overview_windowdeletion
3968 class wxCloseEvent
: public wxEvent
3974 wxCloseEvent(wxEventType commandEventType
= wxEVT_NULL
, int id
= 0);
3977 Returns @true if you can veto a system shutdown or a window close event.
3978 Vetoing a window close event is not possible if the calling code wishes to
3979 force the application to exit, and so this function must be called to check this.
3981 bool CanVeto() const;
3984 Returns @true if the user is just logging off or @false if the system is
3985 shutting down. This method can only be called for end session and query end
3986 session events, it doesn't make sense for close window event.
3988 bool GetLoggingOff() const;
3991 Sets the 'can veto' flag.
3993 void SetCanVeto(bool canVeto
);
3996 Sets the 'logging off' flag.
3998 void SetLoggingOff(bool loggingOff
);
4001 Call this from your event handler to veto a system shutdown or to signal
4002 to the calling application that a window close did not happen.
4004 You can only veto a shutdown if CanVeto() returns @true.
4006 void Veto(bool veto
= true);
4014 This class is used for a variety of menu-related events. Note that
4015 these do not include menu command events, which are
4016 handled using wxCommandEvent objects.
4018 The default handler for @c wxEVT_MENU_HIGHLIGHT displays help
4019 text in the first field of the status bar.
4021 @beginEventTable{wxMenuEvent}
4022 @event{EVT_MENU_OPEN(func)}
4023 A menu is about to be opened. On Windows, this is only sent once for each
4024 navigation of the menubar (up until all menus have closed).
4025 @event{EVT_MENU_CLOSE(func)}
4026 A menu has been just closed.
4027 @event{EVT_MENU_HIGHLIGHT(id, func)}
4028 The menu item with the specified id has been highlighted: used to show
4029 help prompts in the status bar by wxFrame
4030 @event{EVT_MENU_HIGHLIGHT_ALL(func)}
4031 A menu item has been highlighted, i.e. the currently selected menu item has changed.
4037 @see wxCommandEvent, @ref overview_events
4039 class wxMenuEvent
: public wxEvent
4045 wxMenuEvent(wxEventType type
= wxEVT_NULL
, int id
= 0, wxMenu
* menu
= NULL
);
4048 Returns the menu which is being opened or closed.
4050 This method can only be used with the @c OPEN and @c CLOSE events.
4052 The returned value is never @NULL in the ports implementing this
4053 function, which currently includes all the major ones.
4055 wxMenu
* GetMenu() const;
4058 Returns the menu identifier associated with the event.
4059 This method should be only used with the @c HIGHLIGHT events.
4061 int GetMenuId() const;
4064 Returns @true if the menu which is being opened or closed is a popup menu,
4065 @false if it is a normal one.
4067 This method should only be used with the @c OPEN and @c CLOSE events.
4069 bool IsPopup() const;
4075 An event being sent when the window is shown or hidden.
4076 The event is triggered by calls to wxWindow::Show(), and any user
4077 action showing a previously hidden window or vice versa (if allowed by
4078 the current platform and/or window manager).
4079 Notice that the event is not triggered when the application is iconized
4080 (minimized) or restored under wxMSW.
4082 @onlyfor{wxmsw,wxgtk,wxos2}
4084 @beginEventTable{wxShowEvent}
4085 @event{EVT_SHOW(func)}
4086 Process a @c wxEVT_SHOW event.
4092 @see @ref overview_events, wxWindow::Show,
4096 class wxShowEvent
: public wxEvent
4102 wxShowEvent(int winid
= 0, bool show
= false);
4105 Set whether the windows was shown or hidden.
4107 void SetShow(bool show
);
4110 Return @true if the window has been shown, @false if it has been
4113 bool IsShown() const;
4116 @deprecated This function is deprecated in favour of IsShown().
4118 bool GetShow() const;
4124 @class wxIconizeEvent
4126 An event being sent when the frame is iconized (minimized) or restored.
4128 Currently only wxMSW and wxGTK generate such events.
4130 @onlyfor{wxmsw,wxgtk}
4132 @beginEventTable{wxIconizeEvent}
4133 @event{EVT_ICONIZE(func)}
4134 Process a @c wxEVT_ICONIZE event.
4140 @see @ref overview_events, wxTopLevelWindow::Iconize,
4141 wxTopLevelWindow::IsIconized
4143 class wxIconizeEvent
: public wxEvent
4149 wxIconizeEvent(int id
= 0, bool iconized
= true);
4152 Returns @true if the frame has been iconized, @false if it has been
4155 bool IsIconized() const;
4158 @deprecated This function is deprecated in favour of IsIconized().
4160 bool Iconized() const;
4168 A move event holds information about wxTopLevelWindow move change events.
4170 These events are currently only generated by wxMSW port.
4172 @beginEventTable{wxMoveEvent}
4173 @event{EVT_MOVE(func)}
4174 Process a @c wxEVT_MOVE event, which is generated when a window is moved.
4175 @event{EVT_MOVE_START(func)}
4176 Process a @c wxEVT_MOVE_START event, which is generated when the user starts
4177 to move or size a window. wxMSW only.
4178 @event{EVT_MOVING(func)}
4179 Process a @c wxEVT_MOVING event, which is generated while the user is
4180 moving the window. wxMSW only.
4181 @event{EVT_MOVE_END(func)}
4182 Process a @c wxEVT_MOVE_END event, which is generated when the user stops
4183 moving or sizing a window. wxMSW only.
4189 @see wxPoint, @ref overview_events
4191 class wxMoveEvent
: public wxEvent
4197 wxMoveEvent(const wxPoint
& pt
, int id
= 0);
4200 Returns the position of the window generating the move change event.
4202 wxPoint
GetPosition() const;
4204 wxRect
GetRect() const;
4205 void SetRect(const wxRect
& rect
);
4206 void SetPosition(const wxPoint
& pos
);
4213 A size event holds information about size change events of wxWindow.
4215 The EVT_SIZE handler function will be called when the window has been resized.
4217 You may wish to use this for frames to resize their child windows as appropriate.
4219 Note that the size passed is of the whole window: call wxWindow::GetClientSize()
4220 for the area which may be used by the application.
4222 When a window is resized, usually only a small part of the window is damaged
4223 and you may only need to repaint that area. However, if your drawing depends on the
4224 size of the window, you may need to clear the DC explicitly and repaint the whole window.
4225 In which case, you may need to call wxWindow::Refresh to invalidate the entire window.
4227 @b Important : Sizers ( see @ref overview_sizer ) rely on size events to function
4228 correctly. Therefore, in a sizer-based layout, do not forget to call Skip on all
4229 size events you catch (and don't catch size events at all when you don't need to).
4231 @beginEventTable{wxSizeEvent}
4232 @event{EVT_SIZE(func)}
4233 Process a @c wxEVT_SIZE event.
4239 @see wxSize, @ref overview_events
4241 class wxSizeEvent
: public wxEvent
4247 wxSizeEvent(const wxSize
& sz
, int id
= 0);
4250 Returns the entire size of the window generating the size change event.
4252 This is the new total size of the window, i.e. the same size as would
4253 be returned by wxWindow::GetSize() if it were called now. Use
4254 wxWindow::GetClientSize() if you catch this event in a top level window
4255 such as wxFrame to find the size available for the window contents.
4257 wxSize
GetSize() const;
4258 void SetSize(wxSize size
);
4260 wxRect
GetRect() const;
4261 void SetRect(wxRect rect
);
4267 @class wxSetCursorEvent
4269 A wxSetCursorEvent is generated from wxWindow when the mouse cursor is about
4270 to be set as a result of mouse motion.
4272 This event gives the application the chance to perform specific mouse cursor
4273 processing based on the current position of the mouse within the window.
4274 Use wxSetCursorEvent::SetCursor to specify the cursor you want to be displayed.
4276 @beginEventTable{wxSetCursorEvent}
4277 @event{EVT_SET_CURSOR(func)}
4278 Process a @c wxEVT_SET_CURSOR event.
4284 @see ::wxSetCursor, wxWindow::SetCursor
4286 class wxSetCursorEvent
: public wxEvent
4290 Constructor, used by the library itself internally to initialize the event
4293 wxSetCursorEvent(wxCoord x
= 0, wxCoord y
= 0);
4296 Returns a reference to the cursor specified by this event.
4298 const wxCursor
& GetCursor() const;
4301 Returns the X coordinate of the mouse in client coordinates.
4303 wxCoord
GetX() const;
4306 Returns the Y coordinate of the mouse in client coordinates.
4308 wxCoord
GetY() const;
4311 Returns @true if the cursor specified by this event is a valid cursor.
4313 @remarks You cannot specify wxNullCursor with this event, as it is not
4314 considered a valid cursor.
4316 bool HasCursor() const;
4319 Sets the cursor associated with this event.
4321 void SetCursor(const wxCursor
& cursor
);
4326 // ============================================================================
4327 // Global functions/macros
4328 // ============================================================================
4330 /** @addtogroup group_funcmacro_events */
4336 A value uniquely identifying the type of the event.
4338 The values of this type should only be created using wxNewEventType().
4340 See the macro DEFINE_EVENT_TYPE() for more info.
4342 @see @ref overview_events
4344 typedef int wxEventType
;
4347 A special event type usually used to indicate that some wxEvent has yet
4350 wxEventType wxEVT_NULL
;
4352 wxEventType wxEVT_ANY
;
4355 Generates a new unique event type.
4357 Usually this function is only used by wxDEFINE_EVENT() and not called
4360 wxEventType
wxNewEventType();
4363 Define a new event type associated with the specified event class.
4365 This macro defines a new unique event type @a name associated with the
4370 wxDEFINE_EVENT(MY_COMMAND_EVENT, wxCommandEvent);
4372 class MyCustomEvent : public wxEvent { ... };
4373 wxDEFINE_EVENT(MY_CUSTOM_EVENT, MyCustomEvent);
4376 @see wxDECLARE_EVENT(), @ref overview_events_custom
4378 #define wxDEFINE_EVENT(name, cls) \
4379 const wxEventTypeTag< cls > name(wxNewEventType())
4382 Declares a custom event type.
4384 This macro declares a variable called @a name which must be defined
4385 elsewhere using wxDEFINE_EVENT().
4387 The class @a cls must be the wxEvent-derived class associated with the
4388 events of this type and its full declaration must be visible from the point
4389 of use of this macro.
4393 wxDECLARE_EVENT(MY_COMMAND_EVENT, wxCommandEvent);
4395 class MyCustomEvent : public wxEvent { ... };
4396 wxDECLARE_EVENT(MY_CUSTOM_EVENT, MyCustomEvent);
4399 #define wxDECLARE_EVENT(name, cls) \
4400 wxDECLARE_EXPORTED_EVENT(wxEMPTY_PARAMETER_VALUE, name, cls)
4403 Variant of wxDECLARE_EVENT() used for event types defined inside a shared
4406 This is mostly used by wxWidgets internally, e.g.
4408 wxDECLARE_EXPORTED_EVENT(WXDLLIMPEXP_CORE, wxEVT_COMMAND_BUTTON_CLICKED, wxCommandEvent)
4411 #define wxDECLARE_EXPORTED_EVENT( expdecl, name, cls ) \
4412 extern const expdecl wxEventTypeTag< cls > name;
4415 Helper macro for definition of custom event table macros.
4417 This macro must only be used if wxEVENTS_COMPATIBILITY_2_8 is 1, otherwise
4418 it is better and more clear to just use the address of the function
4419 directly as this is all this macro does in this case. However it needs to
4420 explicitly cast @a func to @a functype, which is the type of wxEvtHandler
4421 member function taking the custom event argument when
4422 wxEVENTS_COMPATIBILITY_2_8 is 0.
4424 See wx__DECLARE_EVT0 for an example of use.
4426 @see @ref overview_events_custom_ownclass
4428 #define wxEVENT_HANDLER_CAST(functype, func) (&func)
4431 This macro is used to define event table macros for handling custom
4436 class MyEvent : public wxEvent { ... };
4438 // note that this is not necessary unless using old compilers: for the
4439 // reasonably new ones just use &func instead of MyEventHandler(func)
4440 typedef void (wxEvtHandler::*MyEventFunction)(MyEvent&);
4441 #define MyEventHandler(func) wxEVENT_HANDLER_CAST(MyEventFunction, func)
4443 wxDEFINE_EVENT(MY_EVENT_TYPE, MyEvent);
4445 #define EVT_MY(id, func) \
4446 wx__DECLARE_EVT1(MY_EVENT_TYPE, id, MyEventHandler(func))
4450 wxBEGIN_EVENT_TABLE(MyFrame, wxFrame)
4451 EVT_MY(wxID_ANY, MyFrame::OnMyEvent)
4456 The event type to handle.
4458 The identifier of events to handle.
4460 The event handler method.
4462 #define wx__DECLARE_EVT1(evt, id, fn) \
4463 wx__DECLARE_EVT2(evt, id, wxID_ANY, fn)
4466 Generalized version of the wx__DECLARE_EVT1() macro taking a range of
4467 IDs instead of a single one.
4468 Argument @a id1 is the first identifier of the range, @a id2 is the
4469 second identifier of the range.
4471 #define wx__DECLARE_EVT2(evt, id1, id2, fn) \
4472 DECLARE_EVENT_TABLE_ENTRY(evt, id1, id2, fn, NULL),
4475 Simplified version of the wx__DECLARE_EVT1() macro, to be used when the
4476 event type must be handled regardless of the ID associated with the
4477 specific event instances.
4479 #define wx__DECLARE_EVT0(evt, fn) \
4480 wx__DECLARE_EVT1(evt, wxID_ANY, fn)
4483 Use this macro inside a class declaration to declare a @e static event table
4486 In the implementation file you'll need to use the wxBEGIN_EVENT_TABLE()
4487 and the wxEND_EVENT_TABLE() macros, plus some additional @c EVT_xxx macro
4490 Note that this macro requires a final semicolon.
4492 @see @ref overview_events_eventtables
4494 #define wxDECLARE_EVENT_TABLE()
4497 Use this macro in a source file to start listing @e static event handlers
4498 for a specific class.
4500 Use wxEND_EVENT_TABLE() to terminate the event-declaration block.
4502 @see @ref overview_events_eventtables
4504 #define wxBEGIN_EVENT_TABLE(theClass, baseClass)
4507 Use this macro in a source file to end listing @e static event handlers
4508 for a specific class.
4510 Use wxBEGIN_EVENT_TABLE() to start the event-declaration block.
4512 @see @ref overview_events_eventtables
4514 #define wxEND_EVENT_TABLE()
4517 In a GUI application, this function posts @a event to the specified @e dest
4518 object using wxEvtHandler::AddPendingEvent().
4520 Otherwise, it dispatches @a event immediately using
4521 wxEvtHandler::ProcessEvent(). See the respective documentation for details
4522 (and caveats). Because of limitation of wxEvtHandler::AddPendingEvent()
4523 this function is not thread-safe for event objects having wxString fields,
4524 use wxQueueEvent() instead.
4528 void wxPostEvent(wxEvtHandler
* dest
, const wxEvent
& event
);
4531 Queue an event for processing on the given object.
4533 This is a wrapper around wxEvtHandler::QueueEvent(), see its documentation
4539 The object to queue the event on, can't be @c NULL.
4541 The heap-allocated and non-@c NULL event to queue, the function takes
4544 void wxQueueEvent(wxEvtHandler
* dest
, wxEvent
*event
);
4546 #endif // wxUSE_BASE
4550 wxEventType wxEVT_COMMAND_BUTTON_CLICKED
;
4551 wxEventType wxEVT_COMMAND_CHECKBOX_CLICKED
;
4552 wxEventType wxEVT_COMMAND_CHOICE_SELECTED
;
4553 wxEventType wxEVT_COMMAND_LISTBOX_SELECTED
;
4554 wxEventType wxEVT_COMMAND_LISTBOX_DOUBLECLICKED
;
4555 wxEventType wxEVT_COMMAND_CHECKLISTBOX_TOGGLED
;
4556 wxEventType wxEVT_COMMAND_MENU_SELECTED
;
4557 wxEventType wxEVT_COMMAND_SLIDER_UPDATED
;
4558 wxEventType wxEVT_COMMAND_RADIOBOX_SELECTED
;
4559 wxEventType wxEVT_COMMAND_RADIOBUTTON_SELECTED
;
4560 wxEventType wxEVT_COMMAND_SCROLLBAR_UPDATED
;
4561 wxEventType wxEVT_COMMAND_VLBOX_SELECTED
;
4562 wxEventType wxEVT_COMMAND_COMBOBOX_SELECTED
;
4563 wxEventType wxEVT_COMMAND_TOOL_RCLICKED
;
4564 wxEventType wxEVT_COMMAND_TOOL_DROPDOWN_CLICKED
;
4565 wxEventType wxEVT_COMMAND_TOOL_ENTER
;
4566 wxEventType wxEVT_COMMAND_COMBOBOX_DROPDOWN
;
4567 wxEventType wxEVT_COMMAND_COMBOBOX_CLOSEUP
;
4568 wxEventType wxEVT_THREAD
;
4569 wxEventType wxEVT_LEFT_DOWN
;
4570 wxEventType wxEVT_LEFT_UP
;
4571 wxEventType wxEVT_MIDDLE_DOWN
;
4572 wxEventType wxEVT_MIDDLE_UP
;
4573 wxEventType wxEVT_RIGHT_DOWN
;
4574 wxEventType wxEVT_RIGHT_UP
;
4575 wxEventType wxEVT_MOTION
;
4576 wxEventType wxEVT_ENTER_WINDOW
;
4577 wxEventType wxEVT_LEAVE_WINDOW
;
4578 wxEventType wxEVT_LEFT_DCLICK
;
4579 wxEventType wxEVT_MIDDLE_DCLICK
;
4580 wxEventType wxEVT_RIGHT_DCLICK
;
4581 wxEventType wxEVT_SET_FOCUS
;
4582 wxEventType wxEVT_KILL_FOCUS
;
4583 wxEventType wxEVT_CHILD_FOCUS
;
4584 wxEventType wxEVT_MOUSEWHEEL
;
4585 wxEventType wxEVT_AUX1_DOWN
;
4586 wxEventType wxEVT_AUX1_UP
;
4587 wxEventType wxEVT_AUX1_DCLICK
;
4588 wxEventType wxEVT_AUX2_DOWN
;
4589 wxEventType wxEVT_AUX2_UP
;
4590 wxEventType wxEVT_AUX2_DCLICK
;
4591 wxEventType wxEVT_CHAR
;
4592 wxEventType wxEVT_CHAR_HOOK
;
4593 wxEventType wxEVT_NAVIGATION_KEY
;
4594 wxEventType wxEVT_KEY_DOWN
;
4595 wxEventType wxEVT_KEY_UP
;
4596 wxEventType wxEVT_HOTKEY
;
4597 wxEventType wxEVT_SET_CURSOR
;
4598 wxEventType wxEVT_SCROLL_TOP
;
4599 wxEventType wxEVT_SCROLL_BOTTOM
;
4600 wxEventType wxEVT_SCROLL_LINEUP
;
4601 wxEventType wxEVT_SCROLL_LINEDOWN
;
4602 wxEventType wxEVT_SCROLL_PAGEUP
;
4603 wxEventType wxEVT_SCROLL_PAGEDOWN
;
4604 wxEventType wxEVT_SCROLL_THUMBTRACK
;
4605 wxEventType wxEVT_SCROLL_THUMBRELEASE
;
4606 wxEventType wxEVT_SCROLL_CHANGED
;
4607 wxEventType wxEVT_SPIN_UP
;
4608 wxEventType wxEVT_SPIN_DOWN
;
4609 wxEventType wxEVT_SPIN
;
4610 wxEventType wxEVT_SCROLLWIN_TOP
;
4611 wxEventType wxEVT_SCROLLWIN_BOTTOM
;
4612 wxEventType wxEVT_SCROLLWIN_LINEUP
;
4613 wxEventType wxEVT_SCROLLWIN_LINEDOWN
;
4614 wxEventType wxEVT_SCROLLWIN_PAGEUP
;
4615 wxEventType wxEVT_SCROLLWIN_PAGEDOWN
;
4616 wxEventType wxEVT_SCROLLWIN_THUMBTRACK
;
4617 wxEventType wxEVT_SCROLLWIN_THUMBRELEASE
;
4618 wxEventType wxEVT_SIZE
;
4619 wxEventType wxEVT_MOVE
;
4620 wxEventType wxEVT_CLOSE_WINDOW
;
4621 wxEventType wxEVT_END_SESSION
;
4622 wxEventType wxEVT_QUERY_END_SESSION
;
4623 wxEventType wxEVT_ACTIVATE_APP
;
4624 wxEventType wxEVT_ACTIVATE
;
4625 wxEventType wxEVT_CREATE
;
4626 wxEventType wxEVT_DESTROY
;
4627 wxEventType wxEVT_SHOW
;
4628 wxEventType wxEVT_ICONIZE
;
4629 wxEventType wxEVT_MAXIMIZE
;
4630 wxEventType wxEVT_MOUSE_CAPTURE_CHANGED
;
4631 wxEventType wxEVT_MOUSE_CAPTURE_LOST
;
4632 wxEventType wxEVT_PAINT
;
4633 wxEventType wxEVT_ERASE_BACKGROUND
;
4634 wxEventType wxEVT_NC_PAINT
;
4635 wxEventType wxEVT_MENU_OPEN
;
4636 wxEventType wxEVT_MENU_CLOSE
;
4637 wxEventType wxEVT_MENU_HIGHLIGHT
;
4638 wxEventType wxEVT_CONTEXT_MENU
;
4639 wxEventType wxEVT_SYS_COLOUR_CHANGED
;
4640 wxEventType wxEVT_DISPLAY_CHANGED
;
4641 wxEventType wxEVT_QUERY_NEW_PALETTE
;
4642 wxEventType wxEVT_PALETTE_CHANGED
;
4643 wxEventType wxEVT_JOY_BUTTON_DOWN
;
4644 wxEventType wxEVT_JOY_BUTTON_UP
;
4645 wxEventType wxEVT_JOY_MOVE
;
4646 wxEventType wxEVT_JOY_ZMOVE
;
4647 wxEventType wxEVT_DROP_FILES
;
4648 wxEventType wxEVT_INIT_DIALOG
;
4649 wxEventType wxEVT_IDLE
;
4650 wxEventType wxEVT_UPDATE_UI
;
4651 wxEventType wxEVT_SIZING
;
4652 wxEventType wxEVT_MOVING
;
4653 wxEventType wxEVT_MOVE_START
;
4654 wxEventType wxEVT_MOVE_END
;
4655 wxEventType wxEVT_HIBERNATE
;
4656 wxEventType wxEVT_COMMAND_TEXT_COPY
;
4657 wxEventType wxEVT_COMMAND_TEXT_CUT
;
4658 wxEventType wxEVT_COMMAND_TEXT_PASTE
;
4659 wxEventType wxEVT_COMMAND_LEFT_CLICK
;
4660 wxEventType wxEVT_COMMAND_LEFT_DCLICK
;
4661 wxEventType wxEVT_COMMAND_RIGHT_CLICK
;
4662 wxEventType wxEVT_COMMAND_RIGHT_DCLICK
;
4663 wxEventType wxEVT_COMMAND_SET_FOCUS
;
4664 wxEventType wxEVT_COMMAND_KILL_FOCUS
;
4665 wxEventType wxEVT_COMMAND_ENTER
;
4666 wxEventType wxEVT_HELP
;
4667 wxEventType wxEVT_DETAILED_HELP
;
4668 wxEventType wxEVT_COMMAND_TEXT_UPDATED
;
4669 wxEventType wxEVT_COMMAND_TEXT_ENTER
;
4670 wxEventType wxEVT_COMMAND_TOOL_CLICKED
;
4671 wxEventType wxEVT_WINDOW_MODAL_DIALOG_CLOSED
;