1 /////////////////////////////////////////////////////////////////////////////
3 // Purpose: interface of wxEvtHandler, wxEventBlocker and many
4 // wxEvent-derived classes
5 // Author: wxWidgets team
6 // Licence: wxWindows licence
7 /////////////////////////////////////////////////////////////////////////////
12 The predefined constants for the number of times we propagate event
13 upwards window child-parent chain.
15 enum wxEventPropagation
17 /// don't propagate it at all
18 wxEVENT_PROPAGATE_NONE
= 0,
20 /// propagate it until it is processed
21 wxEVENT_PROPAGATE_MAX
= INT_MAX
25 The different categories for a wxEvent; see wxEvent::GetEventCategory.
27 @note They are used as OR-combinable flags by wxEventLoopBase::YieldFor.
32 This is the category for those events which are generated to update
33 the appearance of the GUI but which (usually) do not comport data
34 processing, i.e. which do not provide input or output data
35 (e.g. size events, scroll events, etc).
36 They are events NOT directly generated by the user's input devices.
38 wxEVT_CATEGORY_UI
= 1,
41 This category groups those events which are generated directly from the
42 user through input devices like mouse and keyboard and usually result in
43 data to be processed from the application
44 (e.g. mouse clicks, key presses, etc).
46 wxEVT_CATEGORY_USER_INPUT
= 2,
48 /// This category is for wxSocketEvent
49 wxEVT_CATEGORY_SOCKET
= 4,
51 /// This category is for wxTimerEvent
52 wxEVT_CATEGORY_TIMER
= 8,
55 This category is for any event used to send notifications from the
56 secondary threads to the main one or in general for notifications among
57 different threads (which may or may not be user-generated).
58 See e.g. wxThreadEvent.
60 wxEVT_CATEGORY_THREAD
= 16,
63 This mask is used in wxEventLoopBase::YieldFor to specify that all event
64 categories should be processed.
67 wxEVT_CATEGORY_UI
|wxEVT_CATEGORY_USER_INPUT
|wxEVT_CATEGORY_SOCKET
| \
68 wxEVT_CATEGORY_TIMER
|wxEVT_CATEGORY_THREAD
74 An event is a structure holding information about an event passed to a
75 callback or member function.
77 wxEvent used to be a multipurpose event object, and is an abstract base class
78 for other event classes (see below).
80 For more information about events, see the @ref overview_events overview.
83 In wxPerl custom event classes should be derived from
84 @c Wx::PlEvent and @c Wx::PlCommandEvent.
90 @see wxCommandEvent, wxMouseEvent
92 class wxEvent
: public wxObject
98 Notice that events are usually created by wxWidgets itself and creating
99 e.g. a wxPaintEvent in your code and sending it to e.g. a wxTextCtrl
100 will not usually affect it at all as native controls have no specific
101 knowledge about wxWidgets events. However you may construct objects of
102 specific types and pass them to wxEvtHandler::ProcessEvent() if you
103 want to create your own custom control and want to process its events
104 in the same manner as the standard ones.
106 Also please notice that the order of parameters in this constructor is
107 different from almost all the derived classes which specify the event
108 type as the first argument.
111 The identifier of the object (window, timer, ...) which generated
114 The unique type of event, e.g. @c wxEVT_PAINT, @c wxEVT_SIZE or
117 wxEvent(int id
= 0, wxEventType eventType
= wxEVT_NULL
);
120 Returns a copy of the event.
122 Any event that is posted to the wxWidgets event system for later action
123 (via wxEvtHandler::AddPendingEvent, wxEvtHandler::QueueEvent or wxPostEvent())
124 must implement this method.
126 All wxWidgets events fully implement this method, but any derived events
127 implemented by the user should also implement this method just in case they
128 (or some event derived from them) are ever posted.
130 All wxWidgets events implement a copy constructor, so the easiest way of
131 implementing the Clone function is to implement a copy constructor for
132 a new event (call it MyEvent) and then define the Clone function like this:
135 wxEvent *Clone() const { return new MyEvent(*this); }
138 virtual wxEvent
* Clone() const = 0;
141 Returns the object (usually a window) associated with the event, if any.
143 wxObject
* GetEventObject() const;
146 Returns the identifier of the given event type, such as @c wxEVT_BUTTON.
148 wxEventType
GetEventType() const;
151 Returns a generic category for this event.
152 wxEvent implementation returns @c wxEVT_CATEGORY_UI by default.
154 This function is used to selectively process events in wxEventLoopBase::YieldFor.
156 virtual wxEventCategory
GetEventCategory() const;
159 Returns the identifier associated with this event, such as a button command id.
164 Return the user data associated with a dynamically connected event handler.
166 wxEvtHandler::Connect() and wxEvtHandler::Bind() allow associating
167 optional @c userData pointer with the handler and this method returns
168 the value of this pointer.
170 The returned pointer is owned by wxWidgets and must not be deleted.
174 wxObject
*GetEventUserData() const;
177 Returns @true if the event handler should be skipped, @false otherwise.
179 bool GetSkipped() const;
182 Gets the timestamp for the event. The timestamp is the time in milliseconds
183 since some fixed moment (not necessarily the standard Unix Epoch, so only
184 differences between the timestamps and not their absolute values usually make sense).
187 wxWidgets returns a non-NULL timestamp only for mouse and key events
188 (see wxMouseEvent and wxKeyEvent).
190 long GetTimestamp() const;
193 Returns @true if the event is or is derived from wxCommandEvent else it returns @false.
195 @note exists only for optimization purposes.
197 bool IsCommandEvent() const;
200 Sets the propagation level to the given value (for example returned from an
201 earlier call to wxEvent::StopPropagation).
203 void ResumePropagation(int propagationLevel
);
206 Sets the originating object.
208 void SetEventObject(wxObject
* object
);
213 void SetEventType(wxEventType type
);
216 Sets the identifier associated with this event, such as a button command id.
221 Sets the timestamp for the event.
223 void SetTimestamp(long timeStamp
= 0);
226 Test if this event should be propagated or not, i.e.\ if the propagation level
227 is currently greater than 0.
229 bool ShouldPropagate() const;
232 This method can be used inside an event handler to control whether further
233 event handlers bound to this event will be called after the current one returns.
235 Without Skip() (or equivalently if Skip(@false) is used), the event will not
236 be processed any more. If Skip(@true) is called, the event processing system
237 continues searching for a further handler function for this event, even though
238 it has been processed already in the current handler.
240 In general, it is recommended to skip all non-command events to allow the
241 default handling to take place. The command events are, however, normally not
242 skipped as usually a single command such as a button click or menu item
243 selection must only be processed by one handler.
245 void Skip(bool skip
= true);
248 Stop the event from propagating to its parent window.
250 Returns the old propagation level value which may be later passed to
251 ResumePropagation() to allow propagating the event again.
253 int StopPropagation();
257 Indicates how many levels the event can propagate.
259 This member is protected and should typically only be set in the constructors
260 of the derived classes. It may be temporarily changed by StopPropagation()
261 and ResumePropagation() and tested with ShouldPropagate().
263 The initial value is set to either @c wxEVENT_PROPAGATE_NONE (by default)
264 meaning that the event shouldn't be propagated at all or to
265 @c wxEVENT_PROPAGATE_MAX (for command events) meaning that it should be
266 propagated as much as necessary.
268 Any positive number means that the event should be propagated but no more than
269 the given number of times. E.g. the propagation level may be set to 1 to
270 propagate the event to its parent only, but not to its grandparent.
272 int m_propagationLevel
;
280 @class wxEventBlocker
282 This class is a special event handler which allows to discard
283 any event (or a set of event types) directed to a specific window.
288 void MyWindow::DoSomething()
291 // block all events directed to this window while
292 // we do the 1000 FunctionWhichSendsEvents() calls
293 wxEventBlocker blocker(this);
295 for ( int i = 0; i 1000; i++ )
296 FunctionWhichSendsEvents(i);
298 } // ~wxEventBlocker called, old event handler is restored
300 // the event generated by this call will be processed:
301 FunctionWhichSendsEvents(0)
308 @see @ref overview_events_processing, wxEvtHandler
310 class wxEventBlocker
: public wxEvtHandler
314 Constructs the blocker for the given window and for the given event type.
316 If @a type is @c wxEVT_ANY, then all events for that window are blocked.
317 You can call Block() after creation to add other event types to the list
320 Note that the @a win window @b must remain alive until the
321 wxEventBlocker object destruction.
323 wxEventBlocker(wxWindow
* win
, wxEventType type
= -1);
326 Destructor. The blocker will remove itself from the chain of event handlers for
327 the window provided in the constructor, thus restoring normal processing of events.
329 virtual ~wxEventBlocker();
332 Adds to the list of event types which should be blocked the given @a eventType.
334 void Block(wxEventType eventType
);
340 Helper class to temporarily change an event to not propagate.
342 class wxPropagationDisabler
345 wxPropagationDisabler(wxEvent
& event
);
346 ~wxPropagationDisabler();
351 Helper class to temporarily lower propagation level.
353 class wxPropagateOnce
356 wxPropagateOnce(wxEvent
& event
);
367 A class that can handle events from the windowing system.
368 wxWindow is (and therefore all window classes are) derived from this class.
370 When events are received, wxEvtHandler invokes the method listed in the
371 event table using itself as the object. When using multiple inheritance
372 <b>it is imperative that the wxEvtHandler(-derived) class is the first
373 class inherited</b> such that the @c this pointer for the overall object
374 will be identical to the @c this pointer of the wxEvtHandler portion.
379 @see @ref overview_events_processing, wxEventBlocker, wxEventLoopBase
381 class wxEvtHandler
: public wxObject
, public wxTrackable
392 If the handler is part of a chain, the destructor will unlink itself
395 virtual ~wxEvtHandler();
399 @name Event queuing and processing
404 Queue event for a later processing.
406 This method is similar to ProcessEvent() but while the latter is
407 synchronous, i.e. the event is processed immediately, before the
408 function returns, this one is asynchronous and returns immediately
409 while the event will be processed at some later time (usually during
410 the next event loop iteration).
412 Another important difference is that this method takes ownership of the
413 @a event parameter, i.e. it will delete it itself. This implies that
414 the event should be allocated on the heap and that the pointer can't be
415 used any more after the function returns (as it can be deleted at any
418 QueueEvent() can be used for inter-thread communication from the worker
419 threads to the main thread, it is safe in the sense that it uses
420 locking internally and avoids the problem mentioned in AddPendingEvent()
421 documentation by ensuring that the @a event object is not used by the
422 calling thread any more. Care should still be taken to avoid that some
423 fields of this object are used by it, notably any wxString members of
424 the event object must not be shallow copies of another wxString object
425 as this would result in them still using the same string buffer behind
426 the scenes. For example:
428 void FunctionInAWorkerThread(const wxString& str)
430 wxCommandEvent* evt = new wxCommandEvent;
432 // NOT evt->SetString(str) as this would be a shallow copy
433 evt->SetString(str.c_str()); // make a deep copy
435 wxTheApp->QueueEvent( evt );
439 Note that you can use wxThreadEvent instead of wxCommandEvent
440 to avoid this problem:
442 void FunctionInAWorkerThread(const wxString& str)
447 // wxThreadEvent::Clone() makes sure that the internal wxString
448 // member is not shared by other wxString instances:
449 wxTheApp->QueueEvent( evt.Clone() );
453 Finally notice that this method automatically wakes up the event loop
454 if it is currently idle by calling ::wxWakeUpIdle() so there is no need
455 to do it manually when using it.
460 A heap-allocated event to be queued, QueueEvent() takes ownership
461 of it. This parameter shouldn't be @c NULL.
463 virtual void QueueEvent(wxEvent
*event
);
466 Post an event to be processed later.
468 This function is similar to QueueEvent() but can't be used to post
469 events from worker threads for the event objects with wxString fields
470 (i.e. in practice most of them) because of an unsafe use of the same
471 wxString object which happens because the wxString field in the
472 original @a event object and its copy made internally by this function
473 share the same string buffer internally. Use QueueEvent() to avoid
476 A copy of @a event is made by the function, so the original can be deleted
477 as soon as function returns (it is common that the original is created
478 on the stack). This requires that the wxEvent::Clone() method be
479 implemented by event so that it can be duplicated and stored until it
483 Event to add to the pending events queue.
485 virtual void AddPendingEvent(const wxEvent
& event
);
488 Asynchronously call the given method.
490 Calling this function on an object schedules an asynchronous call to
491 the method specified as CallAfter() argument at a (slightly) later
492 time. This is useful when processing some events as certain actions
493 typically can't be performed inside their handlers, e.g. you shouldn't
494 show a modal dialog from a mouse click event handler as this would
495 break the mouse capture state -- but you can call a method showing
496 this message dialog after the current event handler completes.
498 The method being called must be the method of the object on which
499 CallAfter() itself is called.
501 Notice that it is safe to use CallAfter() from other, non-GUI,
502 threads, but that the method will be always called in the main, GUI,
507 class MyFrame : public wxFrame {
508 void OnClick(wxMouseEvent& event) {
509 CallAfter(&MyFrame::ShowPosition, event.GetPosition());
512 void ShowPosition(const wxPoint& pos) {
514 wxString::Format("Perform click at (%d, %d)?",
515 pos.x, pos.y), "", wxYES_NO) == wxYES )
517 ... do take this click into account ...
523 @param method The method to call.
524 @param x1 The (optional) first parameter to pass to the method.
525 Currently, 0, 1 or 2 parameters can be passed. If you need to pass
526 more than 2 arguments, you can use the CallAfter<T>(const T& fn)
527 overload that can call any functor.
529 @note This method is not available with Visual C++ before version 8
530 (Visual Studio 2005) as earlier versions of the compiler don't
531 have the required support for C++ templates to implement it.
535 template<typename T
, typename T1
, ...>
536 void CallAfter(void (T::*method
)(T1
, ...), T1 x1
, ...);
539 Asynchronously call the given functor.
541 Calling this function on an object schedules an asynchronous call to
542 the functor specified as CallAfter() argument at a (slightly) later
543 time. This is useful when processing some events as certain actions
544 typically can't be performed inside their handlers, e.g. you shouldn't
545 show a modal dialog from a mouse click event handler as this would
546 break the mouse capture state -- but you can call a function showing
547 this message dialog after the current event handler completes.
549 Notice that it is safe to use CallAfter() from other, non-GUI,
550 threads, but that the method will be always called in the main, GUI,
553 This overload is particularly useful in combination with C++11 lambdas:
555 wxGetApp().CallAfter([]{
560 @param functor The functor to call.
562 @note This method is not available with Visual C++ before version 8
563 (Visual Studio 2005) as earlier versions of the compiler don't
564 have the required support for C++ templates to implement it.
569 void CallAfter(const T
& functor
);
572 Processes an event, searching event tables and calling zero or more suitable
573 event handler function(s).
575 Normally, your application would not call this function: it is called in the
576 wxWidgets implementation to dispatch incoming user interface events to the
577 framework (and application).
579 However, you might need to call it if implementing new functionality
580 (such as a new control) where you define new event types, as opposed to
581 allowing the user to override virtual functions.
583 Notice that you don't usually need to override ProcessEvent() to
584 customize the event handling, overriding the specially provided
585 TryBefore() and TryAfter() functions is usually enough. For example,
586 wxMDIParentFrame may override TryBefore() to ensure that the menu
587 events are processed in the active child frame before being processed
588 in the parent frame itself.
590 The normal order of event table searching is as follows:
591 -# wxApp::FilterEvent() is called. If it returns anything but @c -1
592 (default) the processing stops here.
593 -# TryBefore() is called (this is where wxValidator are taken into
594 account for wxWindow objects). If this returns @true, the function exits.
595 -# If the object is disabled (via a call to wxEvtHandler::SetEvtHandlerEnabled)
596 the function skips to step (7).
597 -# Dynamic event table of the handlers bound using Bind<>() is
598 searched. If a handler is found, it is executed and the function
599 returns @true unless the handler used wxEvent::Skip() to indicate
600 that it didn't handle the event in which case the search continues.
601 -# Static events table of the handlers bound using event table
602 macros is searched for this event handler. If this fails, the base
603 class event table is tried, and so on until no more tables
604 exist or an appropriate function was found. If a handler is found,
605 the same logic as in the previous step applies.
606 -# The search is applied down the entire chain of event handlers (usually the
607 chain has a length of one). This chain can be formed using wxEvtHandler::SetNextHandler():
608 @image html overview_events_chain.png
609 (referring to the image, if @c A->ProcessEvent is called and it doesn't handle
610 the event, @c B->ProcessEvent will be called and so on...).
611 Note that in the case of wxWindow you can build a stack of event handlers
612 (see wxWindow::PushEventHandler() for more info).
613 If any of the handlers of the chain return @true, the function exits.
614 -# TryAfter() is called: for the wxWindow object this may propagate the
615 event to the window parent (recursively). If the event is still not
616 processed, ProcessEvent() on wxTheApp object is called as the last
619 Notice that steps (2)-(6) are performed in ProcessEventLocally()
620 which is called by this function.
625 @true if a suitable event handler function was found and executed,
626 and the function did not call wxEvent::Skip.
628 @see SearchEventTable()
630 virtual bool ProcessEvent(wxEvent
& event
);
633 Try to process the event in this handler and all those chained to it.
635 As explained in ProcessEvent() documentation, the event handlers may be
636 chained in a doubly-linked list. This function tries to process the
637 event in this handler (including performing any pre-processing done in
638 TryBefore(), e.g. applying validators) and all those following it in
639 the chain until the event is processed or the chain is exhausted.
641 This function is called from ProcessEvent() and, in turn, calls
642 TryBefore() and TryAfter(). It is not virtual and so cannot be
643 overridden but can, and should, be called to forward an event to
644 another handler instead of ProcessEvent() which would result in a
645 duplicate call to TryAfter(), e.g. resulting in all unprocessed events
646 being sent to the application object multiple times.
653 @true if this handler of one of those chained to it processed the
656 bool ProcessEventLocally(wxEvent
& event
);
659 Processes an event by calling ProcessEvent() and handles any exceptions
660 that occur in the process.
661 If an exception is thrown in event handler, wxApp::OnExceptionInMainLoop is called.
666 @return @true if the event was processed, @false if no handler was found
667 or an exception was thrown.
669 @see wxWindow::HandleWindowEvent
671 bool SafelyProcessEvent(wxEvent
& event
);
674 Processes the pending events previously queued using QueueEvent() or
675 AddPendingEvent(); you must call this function only if you are sure
676 there are pending events for this handler, otherwise a @c wxCHECK
679 The real processing still happens in ProcessEvent() which is called by this
682 Note that this function needs a valid application object (see
683 wxAppConsole::GetInstance()) because wxApp holds the list of the event
684 handlers with pending events and this function manipulates that list.
686 void ProcessPendingEvents();
689 Deletes all events queued on this event handler using QueueEvent() or
692 Use with care because the events which are deleted are (obviously) not
693 processed and this may have unwanted consequences (e.g. user actions events
696 void DeletePendingEvents();
699 Searches the event table, executing an event handler function if an appropriate
703 Event table to be searched.
705 Event to be matched against an event table entry.
707 @return @true if a suitable event handler function was found and
708 executed, and the function did not call wxEvent::Skip.
710 @remarks This function looks through the object's event table and tries
711 to find an entry that will match the event.
712 An entry will match if:
713 @li The event type matches, and
714 @li the identifier or identifier range matches, or the event table
715 entry's identifier is zero.
717 If a suitable function is called but calls wxEvent::Skip, this
718 function will fail, and searching will continue.
720 @todo this function in the header is listed as an "implementation only" function;
721 are we sure we want to document it?
725 virtual bool SearchEventTable(wxEventTable
& table
,
732 @name Connecting and disconnecting
737 Connects the given function dynamically with the event handler, id and
740 Notice that Bind() provides a more flexible and safer way to do the
741 same thing as Connect(), please use it in any new code -- while
742 Connect() is not formally deprecated due to its existing widespread
743 usage, it has no advantages compared to Bind().
745 This is an alternative to the use of static event tables. It is more
746 flexible as it allows to connect events generated by some object to an
747 event handler defined in a different object of a different class (which
748 is impossible to do directly with the event tables -- the events can be
749 only handled in another object if they are propagated upwards to it).
750 Do make sure to specify the correct @a eventSink when connecting to an
751 event of a different object.
753 See @ref overview_events_bind for more detailed explanation
754 of this function and the @ref page_samples_event sample for usage
757 This specific overload allows you to connect an event handler to a @e range
759 Do not confuse @e source IDs with event @e types: source IDs identify the
760 event generator objects (typically wxMenuItem or wxWindow objects) while the
761 event @e type identify which type of events should be handled by the
762 given @e function (an event generator object may generate many different
766 The first ID of the identifier range to be associated with the event
769 The last ID of the identifier range to be associated with the event
772 The event type to be associated with this event handler.
774 The event handler function. Note that this function should
775 be explicitly converted to the correct type which can be done using a macro
776 called @c wxFooEventHandler for the handler for any @c wxFooEvent.
778 Optional data to be associated with the event table entry.
779 wxWidgets will take ownership of this pointer, i.e. it will be
780 destroyed when the event handler is disconnected or at the program
781 termination. This pointer can be retrieved using
782 wxEvent::GetEventUserData() later.
784 Object whose member function should be called. It must be specified
785 when connecting an event generated by one object to a member
786 function of a different object. If it is omitted, @c this is used.
789 In wxPerl this function takes 4 arguments: @a id, @a lastid,
790 @a type, @a method; if @a method is undef, the handler is
796 void Connect(int id
, int lastId
, wxEventType eventType
,
797 wxObjectEventFunction function
,
798 wxObject
* userData
= NULL
,
799 wxEvtHandler
* eventSink
= NULL
);
802 See the Connect(int, int, wxEventType, wxObjectEventFunction, wxObject*, wxEvtHandler*)
803 overload for more info.
805 This overload can be used to attach an event handler to a single source ID:
809 frame->Connect( wxID_EXIT,
811 wxCommandEventHandler(MyFrame::OnQuit) );
815 Not supported by wxPerl.
818 void Connect(int id
, wxEventType eventType
,
819 wxObjectEventFunction function
,
820 wxObject
* userData
= NULL
,
821 wxEvtHandler
* eventSink
= NULL
);
824 See the Connect(int, int, wxEventType, wxObjectEventFunction, wxObject*, wxEvtHandler*)
825 overload for more info.
827 This overload will connect the given event handler so that regardless of the
828 ID of the event source, the handler will be called.
831 Not supported by wxPerl.
834 void Connect(wxEventType eventType
,
835 wxObjectEventFunction function
,
836 wxObject
* userData
= NULL
,
837 wxEvtHandler
* eventSink
= NULL
);
840 Disconnects the given function dynamically from the event handler, using the
841 specified parameters as search criteria and returning @true if a matching
842 function has been found and removed.
844 This method can only disconnect functions which have been added using the
845 Connect() method. There is no way to disconnect functions connected using
846 the (static) event tables.
849 The event type associated with this event handler.
851 The event handler function.
853 Data associated with the event table entry.
855 Object whose member function should be called.
858 Not supported by wxPerl.
861 bool Disconnect(wxEventType eventType
,
862 wxObjectEventFunction function
,
863 wxObject
* userData
= NULL
,
864 wxEvtHandler
* eventSink
= NULL
);
867 See the Disconnect(wxEventType, wxObjectEventFunction, wxObject*, wxEvtHandler*)
868 overload for more info.
870 This overload takes the additional @a id parameter.
873 Not supported by wxPerl.
876 bool Disconnect(int id
= wxID_ANY
,
877 wxEventType eventType
= wxEVT_NULL
,
878 wxObjectEventFunction function
= NULL
,
879 wxObject
* userData
= NULL
,
880 wxEvtHandler
* eventSink
= NULL
);
883 See the Disconnect(wxEventType, wxObjectEventFunction, wxObject*, wxEvtHandler*)
884 overload for more info.
886 This overload takes an additional range of source IDs.
889 In wxPerl this function takes 3 arguments: @a id,
893 bool Disconnect(int id
, int lastId
,
894 wxEventType eventType
,
895 wxObjectEventFunction function
= NULL
,
896 wxObject
* userData
= NULL
,
897 wxEvtHandler
* eventSink
= NULL
);
902 @name Binding and Unbinding
907 Binds the given function, functor or method dynamically with the event.
909 This offers basically the same functionality as Connect(), but it is
910 more flexible as it also allows you to use ordinary functions and
911 arbitrary functors as event handlers. It is also less restrictive then
912 Connect() because you can use an arbitrary method as an event handler,
913 whereas Connect() requires a wxEvtHandler derived handler.
915 See @ref overview_events_bind for more detailed explanation
916 of this function and the @ref page_samples_event sample for usage
920 The event type to be associated with this event handler.
922 The event handler functor. This can be an ordinary function but also
923 an arbitrary functor like boost::function<>.
925 The first ID of the identifier range to be associated with the event
928 The last ID of the identifier range to be associated with the event
931 Optional data to be associated with the event table entry.
932 wxWidgets will take ownership of this pointer, i.e. it will be
933 destroyed when the event handler is disconnected or at the program
934 termination. This pointer can be retrieved using
935 wxEvent::GetEventUserData() later.
937 @see @ref overview_cpp_rtti_disabled
941 template <typename EventTag
, typename Functor
>
942 void Bind(const EventTag
& eventType
,
945 int lastId
= wxID_ANY
,
946 wxObject
*userData
= NULL
);
949 See the Bind<>(const EventTag&, Functor, int, int, wxObject*) overload for
952 This overload will bind the given method as the event handler.
955 The event type to be associated with this event handler.
957 The event handler method. This can be an arbitrary method (doesn't need
958 to be from a wxEvtHandler derived class).
960 Object whose method should be called. It must always be specified
961 so it can be checked at compile time whether the given method is an
962 actual member of the given handler.
964 The first ID of the identifier range to be associated with the event
967 The last ID of the identifier range to be associated with the event
970 Optional data to be associated with the event table entry.
971 wxWidgets will take ownership of this pointer, i.e. it will be
972 destroyed when the event handler is disconnected or at the program
973 termination. This pointer can be retrieved using
974 wxEvent::GetEventUserData() later.
976 @see @ref overview_cpp_rtti_disabled
980 template <typename EventTag
, typename Class
, typename EventArg
, typename EventHandler
>
981 void Bind(const EventTag
&eventType
,
982 void (Class::*method
)(EventArg
&),
983 EventHandler
*handler
,
985 int lastId
= wxID_ANY
,
986 wxObject
*userData
= NULL
);
988 Unbinds the given function, functor or method dynamically from the
989 event handler, using the specified parameters as search criteria and
990 returning @true if a matching function has been found and removed.
992 This method can only unbind functions, functors or methods which have
993 been added using the Bind<>() method. There is no way to unbind
994 functions bound using the (static) event tables.
997 The event type associated with this event handler.
999 The event handler functor. This can be an ordinary function but also
1000 an arbitrary functor like boost::function<>.
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 Functor
>
1015 bool Unbind(const EventTag
& eventType
,
1018 int lastId
= wxID_ANY
,
1019 wxObject
*userData
= NULL
);
1022 See the Unbind<>(const EventTag&, Functor, int, int, wxObject*)
1023 overload for more info.
1025 This overload unbinds the given method from the event..
1028 The event type associated with this event handler.
1030 The event handler method associated with this event.
1032 Object whose method was called.
1034 The first ID of the identifier range associated with the event
1037 The last ID of the identifier range associated with the event
1040 Data associated with the event table entry.
1042 @see @ref overview_cpp_rtti_disabled
1046 template <typename EventTag
, typename Class
, typename EventArg
, typename EventHandler
>
1047 bool Unbind(const EventTag
&eventType
,
1048 void (Class::*method
)(EventArg
&),
1049 EventHandler
*handler
,
1051 int lastId
= wxID_ANY
,
1052 wxObject
*userData
= NULL
);
1055 @name User-supplied data
1060 Returns user-supplied client data.
1062 @remarks Normally, any extra data the programmer wishes to associate with
1063 the object should be made available by deriving a new class with
1066 @see SetClientData()
1068 void* GetClientData() const;
1071 Returns a pointer to the user-supplied client data object.
1073 @see SetClientObject(), wxClientData
1075 wxClientData
* GetClientObject() const;
1078 Sets user-supplied client data.
1081 Data to be associated with the event handler.
1083 @remarks Normally, any extra data the programmer wishes to associate
1084 with the object should be made available by deriving a new
1085 class with new data members. You must not call this method
1086 and SetClientObject on the same class - only one of them.
1088 @see GetClientData()
1090 void SetClientData(void* data
);
1093 Set the client data object. Any previous object will be deleted.
1095 @see GetClientObject(), wxClientData
1097 void SetClientObject(wxClientData
* data
);
1103 @name Event handler chaining
1105 wxEvtHandler can be arranged in a double-linked list of handlers
1106 which is automatically iterated by ProcessEvent() if needed.
1111 Returns @true if the event handler is enabled, @false otherwise.
1113 @see SetEvtHandlerEnabled()
1115 bool GetEvtHandlerEnabled() const;
1118 Returns the pointer to the next handler in the chain.
1120 @see SetNextHandler(), GetPreviousHandler(), SetPreviousHandler(),
1121 wxWindow::PushEventHandler, wxWindow::PopEventHandler
1123 wxEvtHandler
* GetNextHandler() const;
1126 Returns the pointer to the previous handler in the chain.
1128 @see SetPreviousHandler(), GetNextHandler(), SetNextHandler(),
1129 wxWindow::PushEventHandler, wxWindow::PopEventHandler
1131 wxEvtHandler
* GetPreviousHandler() const;
1134 Enables or disables the event handler.
1137 @true if the event handler is to be enabled, @false if it is to be disabled.
1139 @remarks You can use this function to avoid having to remove the event
1140 handler from the chain, for example when implementing a
1141 dialog editor and changing from edit to test mode.
1143 @see GetEvtHandlerEnabled()
1145 void SetEvtHandlerEnabled(bool enabled
);
1148 Sets the pointer to the next handler.
1151 See ProcessEvent() for more info about how the chains of event handlers
1152 are internally used.
1153 Also remember that wxEvtHandler uses double-linked lists and thus if you
1154 use this function, you should also call SetPreviousHandler() on the
1155 argument passed to this function:
1157 handlerA->SetNextHandler(handlerB);
1158 handlerB->SetPreviousHandler(handlerA);
1162 The event handler to be set as the next handler.
1165 @see @ref overview_events_processing
1167 virtual void SetNextHandler(wxEvtHandler
* handler
);
1170 Sets the pointer to the previous handler.
1171 All remarks about SetNextHandler() apply to this function as well.
1174 The event handler to be set as the previous handler.
1177 @see @ref overview_events_processing
1179 virtual void SetPreviousHandler(wxEvtHandler
* handler
);
1182 Unlinks this event handler from the chain it's part of (if any);
1183 then links the "previous" event handler to the "next" one
1184 (so that the chain won't be interrupted).
1186 E.g. if before calling Unlink() you have the following chain:
1187 @image html evthandler_unlink_before.png
1188 then after calling @c B->Unlink() you'll have:
1189 @image html evthandler_unlink_after.png
1196 Returns @true if the next and the previous handler pointers of this
1197 event handler instance are @NULL.
1201 @see SetPreviousHandler(), SetNextHandler()
1203 bool IsUnlinked() const;
1208 @name Global event filters.
1210 Methods for working with the global list of event filters.
1212 Event filters can be defined to pre-process all the events that happen
1213 in an application, see wxEventFilter documentation for more information.
1218 Add an event filter whose FilterEvent() method will be called for each
1219 and every event processed by wxWidgets.
1221 The filters are called in LIFO order and wxApp is registered as an
1222 event filter by default. The pointer must remain valid until it's
1223 removed with RemoveFilter() and is not deleted by wxEvtHandler.
1227 static void AddFilter(wxEventFilter
* filter
);
1230 Remove a filter previously installed with AddFilter().
1232 It's an error to remove a filter that hadn't been previously added or
1233 was already removed.
1237 static void RemoveFilter(wxEventFilter
* filter
);
1243 Method called by ProcessEvent() before examining this object event
1246 This method can be overridden to hook into the event processing logic
1247 as early as possible. You should usually call the base class version
1248 when overriding this method, even if wxEvtHandler itself does nothing
1249 here, some derived classes do use this method, e.g. wxWindow implements
1250 support for wxValidator in it.
1254 class MyClass : public BaseClass // inheriting from wxEvtHandler
1258 virtual bool TryBefore(wxEvent& event)
1260 if ( MyPreProcess(event) )
1263 return BaseClass::TryBefore(event);
1270 virtual bool TryBefore(wxEvent
& event
);
1273 Method called by ProcessEvent() as last resort.
1275 This method can be overridden to implement post-processing for the
1276 events which were not processed anywhere else.
1278 The base class version handles forwarding the unprocessed events to
1279 wxApp at wxEvtHandler level and propagating them upwards the window
1280 child-parent chain at wxWindow level and so should usually be called
1281 when overriding this method:
1283 class MyClass : public BaseClass // inheriting from wxEvtHandler
1287 virtual bool TryAfter(wxEvent& event)
1289 if ( BaseClass::TryAfter(event) )
1292 return MyPostProcess(event);
1299 virtual bool TryAfter(wxEvent
& event
);
1302 #endif // wxUSE_BASE
1307 Flags for categories of keys.
1309 These values are used by wxKeyEvent::IsKeyInCategory(). They may be
1310 combined via the bitwise operators |, &, and ~.
1314 enum wxKeyCategoryFlags
1316 /// arrow keys, on and off numeric keypads
1319 /// page up and page down keys, on and off numeric keypads
1320 WXK_CATEGORY_PAGING
,
1322 /// home and end keys, on and off numeric keypads
1325 /// tab key, on and off numeric keypads
1328 /// backspace and delete keys, on and off numeric keypads
1331 /// union of WXK_CATEGORY_ARROW, WXK_CATEGORY_PAGING, and WXK_CATEGORY_JUMP categories
1332 WXK_CATEGORY_NAVIGATION
1339 This event class contains information about key press and release events.
1341 The main information carried by this event is the key being pressed or
1342 released. It can be accessed using either GetKeyCode() function or
1343 GetUnicodeKey(). For the printable characters, the latter should be used as
1344 it works for any keys, including non-Latin-1 characters that can be entered
1345 when using national keyboard layouts. GetKeyCode() should be used to handle
1346 special characters (such as cursor arrows keys or @c HOME or @c INS and so
1347 on) which correspond to ::wxKeyCode enum elements above the @c WXK_START
1348 constant. While GetKeyCode() also returns the character code for Latin-1
1349 keys for compatibility, it doesn't work for Unicode characters in general
1350 and will return @c WXK_NONE for any non-Latin-1 ones. For this reason, it's
1351 recommended to always use GetUnicodeKey() and only fall back to GetKeyCode()
1352 if GetUnicodeKey() returned @c WXK_NONE meaning that the event corresponds
1353 to a non-printable special keys.
1355 While both of these functions can be used with the events of @c
1356 wxEVT_KEY_DOWN, @c wxEVT_KEY_UP and @c wxEVT_CHAR types, the values
1357 returned by them are different for the first two events and the last one.
1358 For the latter, the key returned corresponds to the character that would
1359 appear in e.g. a text zone if the user pressed the key in it. As such, its
1360 value depends on the current state of the Shift key and, for the letters,
1361 on the state of Caps Lock modifier. For example, if @c A key is pressed
1362 without Shift being held down, wxKeyEvent of type @c wxEVT_CHAR generated
1363 for this key press will return (from either GetKeyCode() or GetUnicodeKey()
1364 as their meanings coincide for ASCII characters) key code of 97
1365 corresponding the ASCII value of @c a. And if the same key is pressed but
1366 with Shift being held (or Caps Lock being active), then the key could would
1367 be 65, i.e. ASCII value of capital @c A.
1369 However for the key down and up events the returned key code will instead
1370 be @c A independently of the state of the modifier keys i.e. it depends
1371 only on physical key being pressed and is not translated to its logical
1372 representation using the current keyboard state. Such untranslated key
1373 codes are defined as follows:
1374 - For the letters they correspond to the @e upper case value of the
1376 - For the other alphanumeric keys (e.g. @c 7 or @c +), the untranslated
1377 key code corresponds to the character produced by the key when it is
1378 pressed without Shift. E.g. in standard US keyboard layout the
1379 untranslated key code for the key @c =/+ in the upper right corner of
1380 the keyboard is 61 which is the ASCII value of @c =.
1381 - For the rest of the keys (i.e. special non-printable keys) it is the
1382 same as the normal key code as no translation is used anyhow.
1384 Notice that the first rule applies to all Unicode letters, not just the
1385 usual Latin-1 ones. However for non-Latin-1 letters only GetUnicodeKey()
1386 can be used to retrieve the key code as GetKeyCode() just returns @c
1387 WXK_NONE in this case.
1389 To summarize: you should handle @c wxEVT_CHAR if you need the translated
1390 key and @c wxEVT_KEY_DOWN if you only need the value of the key itself,
1391 independent of the current keyboard state.
1393 @note Not all key down events may be generated by the user. As an example,
1394 @c wxEVT_KEY_DOWN with @c = key code can be generated using the
1395 standard US keyboard layout but not using the German one because the @c
1396 = key corresponds to Shift-0 key combination in this layout and the key
1397 code for it is @c 0, not @c =. Because of this you should avoid
1398 requiring your users to type key events that might be impossible to
1399 enter on their keyboard.
1402 Another difference between key and char events is that another kind of
1403 translation is done for the latter ones when the Control key is pressed:
1404 char events for ASCII letters in this case carry codes corresponding to the
1405 ASCII value of Ctrl-Latter, i.e. 1 for Ctrl-A, 2 for Ctrl-B and so on until
1406 26 for Ctrl-Z. This is convenient for terminal-like applications and can be
1407 completely ignored by all the other ones (if you need to handle Ctrl-A it
1408 is probably a better idea to use the key event rather than the char one).
1409 Notice that currently no translation is done for the presses of @c [, @c
1410 \\, @c ], @c ^ and @c _ keys which might be mapped to ASCII values from 27
1412 Since version 2.9.2, the enum values @c WXK_CONTROL_A - @c WXK_CONTROL_Z
1413 can be used instead of the non-descriptive constant values 1-26.
1415 Finally, modifier keys only generate key events but no char events at all.
1416 The modifiers keys are @c WXK_SHIFT, @c WXK_CONTROL, @c WXK_ALT and various
1417 @c WXK_WINDOWS_XXX from ::wxKeyCode enum.
1419 Modifier keys events are special in one additional aspect: usually the
1420 keyboard state associated with a key press is well defined, e.g.
1421 wxKeyboardState::ShiftDown() returns @c true only if the Shift key was held
1422 pressed when the key that generated this event itself was pressed. There is
1423 an ambiguity for the key press events for Shift key itself however. By
1424 convention, it is considered to be already pressed when it is pressed and
1425 already released when it is released. In other words, @c wxEVT_KEY_DOWN
1426 event for the Shift key itself will have @c wxMOD_SHIFT in GetModifiers()
1427 and ShiftDown() will return true while the @c wxEVT_KEY_UP event for Shift
1428 itself will not have @c wxMOD_SHIFT in its modifiers and ShiftDown() will
1432 @b Tip: You may discover the key codes and modifiers generated by all the
1433 keys on your system interactively by running the @ref
1434 page_samples_keyboard wxWidgets sample and pressing some keys in it.
1436 @note If a key down (@c EVT_KEY_DOWN) event is caught and the event handler
1437 does not call @c event.Skip() then the corresponding char event
1438 (@c EVT_CHAR) will not happen. This is by design and enables the
1439 programs that handle both types of events to avoid processing the
1440 same key twice. As a consequence, if you do not want to suppress the
1441 @c wxEVT_CHAR events for the keys you handle, always call @c
1442 event.Skip() in your @c wxEVT_KEY_DOWN handler. Not doing may also
1443 prevent accelerators defined using this key from working.
1445 @note If a key is maintained in a pressed state, you will typically get a
1446 lot of (automatically generated) key down events but only one key up
1447 one at the end when the key is released so it is wrong to assume that
1448 there is one up event corresponding to each down one.
1450 @note For Windows programmers: The key and char events in wxWidgets are
1451 similar to but slightly different from Windows @c WM_KEYDOWN and
1452 @c WM_CHAR events. In particular, Alt-x combination will generate a
1453 char event in wxWidgets (unless it is used as an accelerator) and
1454 almost all keys, including ones without ASCII equivalents, generate
1458 @beginEventTable{wxKeyEvent}
1459 @event{EVT_KEY_DOWN(func)}
1460 Process a @c wxEVT_KEY_DOWN event (any key has been pressed). If this
1461 event is handled and not skipped, @c wxEVT_CHAR will not be generated
1462 at all for this key press (but @c wxEVT_KEY_UP will be).
1463 @event{EVT_KEY_UP(func)}
1464 Process a @c wxEVT_KEY_UP event (any key has been released).
1465 @event{EVT_CHAR(func)}
1466 Process a @c wxEVT_CHAR event.
1467 @event{EVT_CHAR_HOOK(func)}
1468 Process a @c wxEVT_CHAR_HOOK event. Unlike all the other key events,
1469 this event is propagated upwards the window hierarchy which allows
1470 intercepting it in the parent window of the focused window to which it
1471 is sent initially (if there is no focused window, this event is sent to
1472 the wxApp global object). It is also generated before any other key
1473 events and so gives the parent window an opportunity to modify the
1474 keyboard handling of its children, e.g. it is used internally by
1475 wxWidgets in some ports to intercept pressing Esc key in any child of a
1476 dialog to close the dialog itself when it's pressed. By default, if
1477 this event is handled, i.e. the handler doesn't call wxEvent::Skip(),
1478 neither @c wxEVT_KEY_DOWN nor @c wxEVT_CHAR events will be generated
1479 (although @c wxEVT_KEY_UP still will be), i.e. it replaces the normal
1480 key events. However by calling the special DoAllowNextEvent() method
1481 you can handle @c wxEVT_CHAR_HOOK and still allow normal events
1482 generation. This is something that is rarely useful but can be required
1483 if you need to prevent a parent @c wxEVT_CHAR_HOOK handler from running
1484 without suppressing the normal key events. Finally notice that this
1485 event is not generated when the mouse is captured as it is considered
1486 that the window which has the capture should receive all the keyboard
1487 events too without allowing its parent wxTopLevelWindow to interfere
1488 with their processing.
1491 @see wxKeyboardState
1496 class wxKeyEvent
: public wxEvent
,
1497 public wxKeyboardState
1502 Currently, the only valid event types are @c wxEVT_CHAR and @c wxEVT_CHAR_HOOK.
1504 wxKeyEvent(wxEventType keyEventType
= wxEVT_NULL
);
1507 Returns the key code of the key that generated this event.
1509 ASCII symbols return normal ASCII values, while events from special
1510 keys such as "left cursor arrow" (@c WXK_LEFT) return values outside of
1511 the ASCII range. See ::wxKeyCode for a full list of the virtual key
1514 Note that this method returns a meaningful value only for special
1515 non-alphanumeric keys or if the user entered a Latin-1 character (this
1516 includes ASCII and the accented letters found in Western European
1517 languages but not letters of other alphabets such as e.g. Cyrillic).
1518 Otherwise it simply method returns @c WXK_NONE and GetUnicodeKey()
1519 should be used to obtain the corresponding Unicode character.
1521 Using GetUnicodeKey() is in general the right thing to do if you are
1522 interested in the characters typed by the user, GetKeyCode() should be
1523 only used for special keys (for which GetUnicodeKey() returns @c
1524 WXK_NONE). To handle both kinds of keys you might write:
1526 void MyHandler::OnChar(wxKeyEvent& event)
1528 wxChar uc = event.GetUnicodeKey();
1529 if ( uc != WXK_NONE )
1531 // It's a "normal" character. Notice that this includes
1532 // control characters in 1..31 range, e.g. WXK_RETURN or
1533 // WXK_BACK, so check for them explicitly.
1536 wxLogMessage("You pressed '%c'", uc);
1540 // It's a control character
1544 else // No Unicode equivalent.
1546 // It's a special key, deal with all the known ones:
1547 switch ( event.GetKeyCode() )
1562 int GetKeyCode() const;
1565 Returns true if the key is in the given key category.
1568 A bitwise combination of named ::wxKeyCategoryFlags constants.
1572 bool IsKeyInCategory(int category
) const;
1576 Obtains the position (in client coordinates) at which the key was pressed.
1578 Notice that under most platforms this position is simply the current
1579 mouse pointer position and has no special relationship to the key event
1582 @a x and @a y may be @NULL if the corresponding coordinate is not
1585 wxPoint
GetPosition() const;
1586 void GetPosition(wxCoord
* x
, wxCoord
* y
) const;
1590 Returns the raw key code for this event.
1592 The flags are platform-dependent and should only be used if the
1593 functionality provided by other wxKeyEvent methods is insufficient.
1595 Under MSW, the raw key code is the value of @c wParam parameter of the
1596 corresponding message.
1598 Under GTK, the raw key code is the @c keyval field of the corresponding
1601 Under OS X, the raw key code is the @c keyCode field of the
1602 corresponding NSEvent.
1604 @note Currently the raw key codes are not supported by all ports, use
1605 @ifdef_ wxHAS_RAW_KEY_CODES to determine if this feature is available.
1607 wxUint32
GetRawKeyCode() const;
1610 Returns the low level key flags for this event.
1612 The flags are platform-dependent and should only be used if the
1613 functionality provided by other wxKeyEvent methods is insufficient.
1615 Under MSW, the raw flags are just the value of @c lParam parameter of
1616 the corresponding message.
1618 Under GTK, the raw flags contain the @c hardware_keycode field of the
1619 corresponding GDK event.
1621 Under OS X, the raw flags contain the modifiers state.
1623 @note Currently the raw key flags are not supported by all ports, use
1624 @ifdef_ wxHAS_RAW_KEY_CODES to determine if this feature is available.
1626 wxUint32
GetRawKeyFlags() const;
1629 Returns the Unicode character corresponding to this key event.
1631 If the key pressed doesn't have any character value (e.g. a cursor key)
1632 this method will return @c WXK_NONE. In this case you should use
1633 GetKeyCode() to retrieve the value of the key.
1635 This function is only available in Unicode build, i.e. when
1636 @c wxUSE_UNICODE is 1.
1638 wxChar
GetUnicodeKey() const;
1641 Returns the X position (in client coordinates) of the event.
1645 wxCoord
GetX() const;
1648 Returns the Y position (in client coordinates) of the event.
1652 wxCoord
GetY() const;
1655 Allow normal key events generation.
1657 Can be called from @c wxEVT_CHAR_HOOK handler to indicate that the
1658 generation of normal events should @em not be suppressed, as it happens
1659 by default when this event is handled.
1661 The intended use of this method is to allow some window object to
1662 prevent @c wxEVT_CHAR_HOOK handler in its parent window from running by
1663 defining its own handler for this event. Without calling this method,
1664 this would result in not generating @c wxEVT_KEY_DOWN nor @c wxEVT_CHAR
1665 events at all but by calling it you can ensure that these events would
1666 still be generated, even if @c wxEVT_CHAR_HOOK event was handled.
1670 void DoAllowNextEvent();
1673 Returns @true if DoAllowNextEvent() had been called, @false by default.
1675 This method is used by wxWidgets itself to determine whether the normal
1676 key events should be generated after @c wxEVT_CHAR_HOOK processing.
1680 bool IsNextEventAllowed() const;
1691 // Which button is down?
1694 wxJOY_BUTTON_ANY
= -1,
1703 @class wxJoystickEvent
1705 This event class contains information about joystick events, particularly
1706 events received by windows.
1708 @beginEventTable{wxJoystickEvent}
1709 @event{EVT_JOY_BUTTON_DOWN(func)}
1710 Process a @c wxEVT_JOY_BUTTON_DOWN event.
1711 @event{EVT_JOY_BUTTON_UP(func)}
1712 Process a @c wxEVT_JOY_BUTTON_UP event.
1713 @event{EVT_JOY_MOVE(func)}
1714 Process a @c wxEVT_JOY_MOVE event.
1715 @event{EVT_JOY_ZMOVE(func)}
1716 Process a @c wxEVT_JOY_ZMOVE event.
1717 @event{EVT_JOYSTICK_EVENTS(func)}
1718 Processes all joystick events.
1726 class wxJoystickEvent
: public wxEvent
1732 wxJoystickEvent(wxEventType eventType
= wxEVT_NULL
, int state
= 0,
1733 int joystick
= wxJOYSTICK1
,
1737 Returns @true if the event was a down event from the specified button
1741 Can be @c wxJOY_BUTTONn where @c n is 1, 2, 3 or 4; or @c wxJOY_BUTTON_ANY to
1742 indicate any button down event.
1744 bool ButtonDown(int button
= wxJOY_BUTTON_ANY
) const;
1747 Returns @true if the specified button (or any button) was in a down state.
1750 Can be @c wxJOY_BUTTONn where @c n is 1, 2, 3 or 4; or @c wxJOY_BUTTON_ANY to
1751 indicate any button down event.
1753 bool ButtonIsDown(int button
= wxJOY_BUTTON_ANY
) const;
1756 Returns @true if the event was an up event from the specified button
1760 Can be @c wxJOY_BUTTONn where @c n is 1, 2, 3 or 4; or @c wxJOY_BUTTON_ANY to
1761 indicate any button down event.
1763 bool ButtonUp(int button
= wxJOY_BUTTON_ANY
) const;
1766 Returns the identifier of the button changing state.
1768 This is a @c wxJOY_BUTTONn identifier, where @c n is one of 1, 2, 3, 4.
1770 int GetButtonChange() const;
1773 Returns the down state of the buttons.
1775 This is a @c wxJOY_BUTTONn identifier, where @c n is one of 1, 2, 3, 4.
1777 int GetButtonState() const;
1780 Returns the identifier of the joystick generating the event - one of
1781 wxJOYSTICK1 and wxJOYSTICK2.
1783 int GetJoystick() const;
1786 Returns the x, y position of the joystick event.
1788 These coordinates are valid for all the events except wxEVT_JOY_ZMOVE.
1790 wxPoint
GetPosition() const;
1793 Returns the z position of the joystick event.
1795 This method can only be used for wxEVT_JOY_ZMOVE events.
1797 int GetZPosition() const;
1800 Returns @true if this was a button up or down event
1801 (@e not 'is any button down?').
1803 bool IsButton() const;
1806 Returns @true if this was an x, y move event.
1808 bool IsMove() const;
1811 Returns @true if this was a z move event.
1813 bool IsZMove() const;
1819 @class wxScrollWinEvent
1821 A scroll event holds information about events sent from scrolling windows.
1823 Note that you can use the EVT_SCROLLWIN* macros for intercepting scroll window events
1824 from the receiving window.
1826 @beginEventTable{wxScrollWinEvent}
1827 @event{EVT_SCROLLWIN(func)}
1828 Process all scroll events.
1829 @event{EVT_SCROLLWIN_TOP(func)}
1830 Process @c wxEVT_SCROLLWIN_TOP scroll-to-top events.
1831 @event{EVT_SCROLLWIN_BOTTOM(func)}
1832 Process @c wxEVT_SCROLLWIN_BOTTOM scroll-to-bottom events.
1833 @event{EVT_SCROLLWIN_LINEUP(func)}
1834 Process @c wxEVT_SCROLLWIN_LINEUP line up events.
1835 @event{EVT_SCROLLWIN_LINEDOWN(func)}
1836 Process @c wxEVT_SCROLLWIN_LINEDOWN line down events.
1837 @event{EVT_SCROLLWIN_PAGEUP(func)}
1838 Process @c wxEVT_SCROLLWIN_PAGEUP page up events.
1839 @event{EVT_SCROLLWIN_PAGEDOWN(func)}
1840 Process @c wxEVT_SCROLLWIN_PAGEDOWN page down events.
1841 @event{EVT_SCROLLWIN_THUMBTRACK(func)}
1842 Process @c wxEVT_SCROLLWIN_THUMBTRACK thumbtrack events
1843 (frequent events sent as the user drags the thumbtrack).
1844 @event{EVT_SCROLLWIN_THUMBRELEASE(func)}
1845 Process @c wxEVT_SCROLLWIN_THUMBRELEASE thumb release events.
1852 @see wxScrollEvent, @ref overview_events
1854 class wxScrollWinEvent
: public wxEvent
1860 wxScrollWinEvent(wxEventType commandType
= wxEVT_NULL
, int pos
= 0,
1861 int orientation
= 0);
1864 Returns wxHORIZONTAL or wxVERTICAL, depending on the orientation of the
1867 @todo wxHORIZONTAL and wxVERTICAL should go in their own enum
1869 int GetOrientation() const;
1872 Returns the position of the scrollbar for the thumb track and release events.
1874 Note that this field can't be used for the other events, you need to query
1875 the window itself for the current position in that case.
1877 int GetPosition() const;
1879 void SetOrientation(int orient
);
1880 void SetPosition(int pos
);
1886 @class wxSysColourChangedEvent
1888 This class is used for system colour change events, which are generated
1889 when the user changes the colour settings using the control panel.
1890 This is only appropriate under Windows.
1893 The default event handler for this event propagates the event to child windows,
1894 since Windows only sends the events to top-level windows.
1895 If intercepting this event for a top-level window, remember to call the base
1896 class handler, or to pass the event on to the window's children explicitly.
1898 @beginEventTable{wxSysColourChangedEvent}
1899 @event{EVT_SYS_COLOUR_CHANGED(func)}
1900 Process a @c wxEVT_SYS_COLOUR_CHANGED event.
1906 @see @ref overview_events
1908 class wxSysColourChangedEvent
: public wxEvent
1914 wxSysColourChangedEvent();
1920 @class wxCommandEvent
1922 This event class contains information about command events, which originate
1923 from a variety of simple controls.
1925 Note that wxCommandEvents and wxCommandEvent-derived event classes by default
1926 and unlike other wxEvent-derived classes propagate upward from the source
1927 window (the window which emits the event) up to the first parent which processes
1928 the event. Be sure to read @ref overview_events_propagation.
1930 More complex controls, such as wxTreeCtrl, have separate command event classes.
1932 @beginEventTable{wxCommandEvent}
1933 @event{EVT_COMMAND(id, event, func)}
1934 Process a command, supplying the window identifier, command event identifier,
1935 and member function.
1936 @event{EVT_COMMAND_RANGE(id1, id2, event, func)}
1937 Process a command for a range of window identifiers, supplying the minimum and
1938 maximum window identifiers, command event identifier, and member function.
1939 @event{EVT_BUTTON(id, func)}
1940 Process a @c wxEVT_BUTTON command, which is generated by a wxButton control.
1941 @event{EVT_CHECKBOX(id, func)}
1942 Process a @c wxEVT_CHECKBOX command, which is generated by a wxCheckBox control.
1943 @event{EVT_CHOICE(id, func)}
1944 Process a @c wxEVT_CHOICE command, which is generated by a wxChoice control.
1945 @event{EVT_COMBOBOX(id, func)}
1946 Process a @c wxEVT_COMBOBOX command, which is generated by a wxComboBox control.
1947 @event{EVT_LISTBOX(id, func)}
1948 Process a @c wxEVT_LISTBOX command, which is generated by a wxListBox control.
1949 @event{EVT_LISTBOX_DCLICK(id, func)}
1950 Process a @c wxEVT_LISTBOX_DCLICK command, which is generated by a wxListBox control.
1951 @event{EVT_CHECKLISTBOX(id, func)}
1952 Process a @c wxEVT_CHECKLISTBOX command, which is generated by a wxCheckListBox control.
1953 @event{EVT_MENU(id, func)}
1954 Process a @c wxEVT_MENU command, which is generated by a menu item.
1955 @event{EVT_MENU_RANGE(id1, id2, func)}
1956 Process a @c wxEVT_MENU command, which is generated by a range of menu items.
1957 @event{EVT_CONTEXT_MENU(func)}
1958 Process the event generated when the user has requested a popup menu to appear by
1959 pressing a special keyboard key (under Windows) or by right clicking the mouse.
1960 @event{EVT_RADIOBOX(id, func)}
1961 Process a @c wxEVT_RADIOBOX command, which is generated by a wxRadioBox control.
1962 @event{EVT_RADIOBUTTON(id, func)}
1963 Process a @c wxEVT_RADIOBUTTON command, which is generated by a wxRadioButton control.
1964 @event{EVT_SCROLLBAR(id, func)}
1965 Process a @c wxEVT_SCROLLBAR command, which is generated by a wxScrollBar
1966 control. This is provided for compatibility only; more specific scrollbar event macros
1967 should be used instead (see wxScrollEvent).
1968 @event{EVT_SLIDER(id, func)}
1969 Process a @c wxEVT_SLIDER command, which is generated by a wxSlider control.
1970 @event{EVT_TEXT(id, func)}
1971 Process a @c wxEVT_TEXT command, which is generated by a wxTextCtrl control.
1972 @event{EVT_TEXT_ENTER(id, func)}
1973 Process a @c wxEVT_TEXT_ENTER command, which is generated by a wxTextCtrl control.
1974 Note that you must use wxTE_PROCESS_ENTER flag when creating the control if you want it
1975 to generate such events.
1976 @event{EVT_TEXT_MAXLEN(id, func)}
1977 Process a @c wxEVT_TEXT_MAXLEN command, which is generated by a wxTextCtrl control
1978 when the user tries to enter more characters into it than the limit previously set
1979 with SetMaxLength().
1980 @event{EVT_TOGGLEBUTTON(id, func)}
1981 Process a @c wxEVT_TOGGLEBUTTON event.
1982 @event{EVT_TOOL(id, func)}
1983 Process a @c wxEVT_TOOL event (a synonym for @c wxEVT_MENU).
1984 Pass the id of the tool.
1985 @event{EVT_TOOL_RANGE(id1, id2, func)}
1986 Process a @c wxEVT_TOOL event for a range of identifiers. Pass the ids of the tools.
1987 @event{EVT_TOOL_RCLICKED(id, func)}
1988 Process a @c wxEVT_TOOL_RCLICKED event. Pass the id of the tool. (Not available on wxOSX.)
1989 @event{EVT_TOOL_RCLICKED_RANGE(id1, id2, func)}
1990 Process a @c wxEVT_TOOL_RCLICKED event for a range of ids. Pass the ids of the tools. (Not available on wxOSX.)
1991 @event{EVT_TOOL_ENTER(id, func)}
1992 Process a @c wxEVT_TOOL_ENTER event. Pass the id of the toolbar itself.
1993 The value of wxCommandEvent::GetSelection() is the tool id, or -1 if the mouse cursor
1994 has moved off a tool. (Not available on wxOSX.)
1995 @event{EVT_COMMAND_LEFT_CLICK(id, func)}
1996 Process a @c wxEVT_COMMAND_LEFT_CLICK command, which is generated by a control (wxMSW only).
1997 @event{EVT_COMMAND_LEFT_DCLICK(id, func)}
1998 Process a @c wxEVT_COMMAND_LEFT_DCLICK command, which is generated by a control (wxMSW only).
1999 @event{EVT_COMMAND_RIGHT_CLICK(id, func)}
2000 Process a @c wxEVT_COMMAND_RIGHT_CLICK command, which is generated by a control (wxMSW only).
2001 @event{EVT_COMMAND_SET_FOCUS(id, func)}
2002 Process a @c wxEVT_COMMAND_SET_FOCUS command, which is generated by a control (wxMSW only).
2003 @event{EVT_COMMAND_KILL_FOCUS(id, func)}
2004 Process a @c wxEVT_COMMAND_KILL_FOCUS command, which is generated by a control (wxMSW only).
2005 @event{EVT_COMMAND_ENTER(id, func)}
2006 Process a @c wxEVT_COMMAND_ENTER command, which is generated by a control.
2012 class wxCommandEvent
: public wxEvent
2018 wxCommandEvent(wxEventType commandEventType
= wxEVT_NULL
, int id
= 0);
2021 Returns client data pointer for a listbox or choice selection event
2022 (not valid for a deselection).
2024 void* GetClientData() const;
2027 Returns client object pointer for a listbox or choice selection event
2028 (not valid for a deselection).
2030 wxClientData
* GetClientObject() const;
2033 Returns extra information dependent on the event objects type.
2035 If the event comes from a listbox selection, it is a boolean
2036 determining whether the event was a selection (@true) or a
2037 deselection (@false). A listbox deselection only occurs for
2038 multiple-selection boxes, and in this case the index and string values
2039 are indeterminate and the listbox must be examined by the application.
2041 long GetExtraLong() const;
2044 Returns the integer identifier corresponding to a listbox, choice or
2045 radiobox selection (only if the event was a selection, not a deselection),
2046 or a boolean value representing the value of a checkbox.
2048 For a menu item, this method returns -1 if the item is not checkable or
2049 a boolean value (true or false) for checkable items indicating the new
2055 Returns item index for a listbox or choice selection event (not valid for
2058 int GetSelection() const;
2061 Returns item string for a listbox or choice selection event. If one
2062 or several items have been deselected, returns the index of the first
2063 deselected item. If some items have been selected and others deselected
2064 at the same time, it will return the index of the first selected item.
2066 wxString
GetString() const;
2069 This method can be used with checkbox and menu events: for the checkboxes, the
2070 method returns @true for a selection event and @false for a deselection one.
2071 For the menu events, this method indicates if the menu item just has become
2072 checked or unchecked (and thus only makes sense for checkable menu items).
2074 Notice that this method cannot be used with wxCheckListBox currently.
2076 bool IsChecked() const;
2079 For a listbox or similar event, returns @true if it is a selection, @false
2080 if it is a deselection. If some items have been selected and others deselected
2081 at the same time, it will return @true.
2083 bool IsSelection() const;
2086 Sets the client data for this event.
2088 void SetClientData(void* clientData
);
2091 Sets the client object for this event. The client object is not owned by the
2092 event object and the event object will not delete the client object in its destructor.
2094 The client object must be owned and deleted by another object (e.g. a control)
2095 that has longer life time than the event object.
2097 void SetClientObject(wxClientData
* clientObject
);
2100 Sets the @b m_extraLong member.
2102 void SetExtraLong(long extraLong
);
2105 Sets the @b m_commandInt member.
2107 void SetInt(int intCommand
);
2110 Sets the @b m_commandString member.
2112 void SetString(const wxString
& string
);
2118 @class wxWindowCreateEvent
2120 This event is sent just after the actual window associated with a wxWindow
2121 object has been created.
2123 Since it is derived from wxCommandEvent, the event propagates up
2124 the window hierarchy.
2126 @beginEventTable{wxWindowCreateEvent}
2127 @event{EVT_WINDOW_CREATE(func)}
2128 Process a @c wxEVT_CREATE event.
2134 @see @ref overview_events, wxWindowDestroyEvent
2136 class wxWindowCreateEvent
: public wxCommandEvent
2142 wxWindowCreateEvent(wxWindow
* win
= NULL
);
2144 /// Return the window being created.
2145 wxWindow
*GetWindow() const;
2153 A paint event is sent when a window's contents needs to be repainted.
2155 The handler of this event must create a wxPaintDC object and use it for
2156 painting the window contents. For example:
2158 void MyWindow::OnPaint(wxPaintEvent& event)
2166 Notice that you must @e not create other kinds of wxDC (e.g. wxClientDC or
2167 wxWindowDC) in EVT_PAINT handlers and also don't create wxPaintDC outside
2168 of this event handlers.
2171 You can optimize painting by retrieving the rectangles that have been damaged
2172 and only repainting these. The rectangles are in terms of the client area,
2173 and are unscrolled, so you will need to do some calculations using the current
2174 view position to obtain logical, scrolled units.
2175 Here is an example of using the wxRegionIterator class:
2177 // Called when window needs to be repainted.
2178 void MyWindow::OnPaint(wxPaintEvent& event)
2182 // Find Out where the window is scrolled to
2183 int vbX,vbY; // Top left corner of client
2184 GetViewStart(&vbX,&vbY);
2186 int vX,vY,vW,vH; // Dimensions of client area in pixels
2187 wxRegionIterator upd(GetUpdateRegion()); // get the update rect list
2196 // Alternatively we can do this:
2197 // wxRect rect(upd.GetRect());
2199 // Repaint this rectangle
2208 Please notice that in general it is impossible to change the drawing of a
2209 standard control (such as wxButton) and so you shouldn't attempt to handle
2210 paint events for them as even if it might work on some platforms, this is
2211 inherently not portable and won't work everywhere.
2214 @beginEventTable{wxPaintEvent}
2215 @event{EVT_PAINT(func)}
2216 Process a @c wxEVT_PAINT event.
2222 @see @ref overview_events
2224 class wxPaintEvent
: public wxEvent
2230 wxPaintEvent(int id
= 0);
2236 @class wxMaximizeEvent
2238 An event being sent when a top level window is maximized. Notice that it is
2239 not sent when the window is restored to its original size after it had been
2240 maximized, only a normal wxSizeEvent is generated in this case.
2242 Currently this event is only generated in wxMSW, wxGTK, wxOSX/Cocoa and wxOS2
2243 ports so portable programs should only rely on receiving @c wxEVT_SIZE and
2244 not necessarily this event when the window is maximized.
2246 @beginEventTable{wxMaximizeEvent}
2247 @event{EVT_MAXIMIZE(func)}
2248 Process a @c wxEVT_MAXIMIZE event.
2254 @see @ref overview_events, wxTopLevelWindow::Maximize,
2255 wxTopLevelWindow::IsMaximized
2257 class wxMaximizeEvent
: public wxEvent
2261 Constructor. Only used by wxWidgets internally.
2263 wxMaximizeEvent(int id
= 0);
2267 The possibles modes to pass to wxUpdateUIEvent::SetMode().
2271 /** Send UI update events to all windows. */
2272 wxUPDATE_UI_PROCESS_ALL
,
2274 /** Send UI update events to windows that have
2275 the wxWS_EX_PROCESS_UI_UPDATES flag specified. */
2276 wxUPDATE_UI_PROCESS_SPECIFIED
2281 @class wxUpdateUIEvent
2283 This class is used for pseudo-events which are called by wxWidgets
2284 to give an application the chance to update various user interface elements.
2286 Without update UI events, an application has to work hard to check/uncheck,
2287 enable/disable, show/hide, and set the text for elements such as menu items
2288 and toolbar buttons. The code for doing this has to be mixed up with the code
2289 that is invoked when an action is invoked for a menu item or button.
2291 With update UI events, you define an event handler to look at the state of the
2292 application and change UI elements accordingly. wxWidgets will call your member
2293 functions in idle time, so you don't have to worry where to call this code.
2295 In addition to being a clearer and more declarative method, it also means you don't
2296 have to worry whether you're updating a toolbar or menubar identifier. The same
2297 handler can update a menu item and toolbar button, if the identifier is the same.
2298 Instead of directly manipulating the menu or button, you call functions in the event
2299 object, such as wxUpdateUIEvent::Check. wxWidgets will determine whether such a
2300 call has been made, and which UI element to update.
2302 These events will work for popup menus as well as menubars. Just before a menu is
2303 popped up, wxMenu::UpdateUI is called to process any UI events for the window that
2306 If you find that the overhead of UI update processing is affecting your application,
2307 you can do one or both of the following:
2308 @li Call wxUpdateUIEvent::SetMode with a value of wxUPDATE_UI_PROCESS_SPECIFIED,
2309 and set the extra style wxWS_EX_PROCESS_UI_UPDATES for every window that should
2310 receive update events. No other windows will receive update events.
2311 @li Call wxUpdateUIEvent::SetUpdateInterval with a millisecond value to set the delay
2312 between updates. You may need to call wxWindow::UpdateWindowUI at critical points,
2313 for example when a dialog is about to be shown, in case the user sees a slight
2314 delay before windows are updated.
2316 Note that although events are sent in idle time, defining a wxIdleEvent handler
2317 for a window does not affect this because the events are sent from wxWindow::OnInternalIdle
2318 which is always called in idle time.
2320 wxWidgets tries to optimize update events on some platforms.
2321 On Windows and GTK+, events for menubar items are only sent when the menu is about
2322 to be shown, and not in idle time.
2325 @beginEventTable{wxUpdateUIEvent}
2326 @event{EVT_UPDATE_UI(id, func)}
2327 Process a @c wxEVT_UPDATE_UI event for the command with the given id.
2328 @event{EVT_UPDATE_UI_RANGE(id1, id2, func)}
2329 Process a @c wxEVT_UPDATE_UI event for any command with id included in the given range.
2335 @see @ref overview_events
2337 class wxUpdateUIEvent
: public wxCommandEvent
2343 wxUpdateUIEvent(wxWindowID commandId
= 0);
2346 Returns @true if it is appropriate to update (send UI update events to)
2349 This function looks at the mode used (see wxUpdateUIEvent::SetMode),
2350 the wxWS_EX_PROCESS_UI_UPDATES flag in @a window, the time update events
2351 were last sent in idle time, and the update interval, to determine whether
2352 events should be sent to this window now. By default this will always
2353 return @true because the update mode is initially wxUPDATE_UI_PROCESS_ALL
2354 and the interval is set to 0; so update events will be sent as often as
2355 possible. You can reduce the frequency that events are sent by changing the
2356 mode and/or setting an update interval.
2358 @see ResetUpdateTime(), SetUpdateInterval(), SetMode()
2360 static bool CanUpdate(wxWindow
* window
);
2363 Check or uncheck the UI element.
2365 void Check(bool check
);
2368 Enable or disable the UI element.
2370 void Enable(bool enable
);
2373 Returns @true if the UI element should be checked.
2375 bool GetChecked() const;
2378 Returns @true if the UI element should be enabled.
2380 bool GetEnabled() const;
2383 Static function returning a value specifying how wxWidgets will send update
2384 events: to all windows, or only to those which specify that they will process
2389 static wxUpdateUIMode
GetMode();
2392 Returns @true if the application has called Check().
2393 For wxWidgets internal use only.
2395 bool GetSetChecked() const;
2398 Returns @true if the application has called Enable().
2399 For wxWidgets internal use only.
2401 bool GetSetEnabled() const;
2404 Returns @true if the application has called Show().
2405 For wxWidgets internal use only.
2407 bool GetSetShown() const;
2410 Returns @true if the application has called SetText().
2411 For wxWidgets internal use only.
2413 bool GetSetText() const;
2416 Returns @true if the UI element should be shown.
2418 bool GetShown() const;
2421 Returns the text that should be set for the UI element.
2423 wxString
GetText() const;
2426 Returns the current interval between updates in milliseconds.
2427 The value -1 disables updates, 0 updates as frequently as possible.
2429 @see SetUpdateInterval().
2431 static long GetUpdateInterval();
2434 Used internally to reset the last-updated time to the current time.
2436 It is assumed that update events are normally sent in idle time, so this
2437 is called at the end of idle processing.
2439 @see CanUpdate(), SetUpdateInterval(), SetMode()
2441 static void ResetUpdateTime();
2444 Specify how wxWidgets will send update events: to all windows, or only to
2445 those which specify that they will process the events.
2448 this parameter may be one of the ::wxUpdateUIMode enumeration values.
2449 The default mode is wxUPDATE_UI_PROCESS_ALL.
2451 static void SetMode(wxUpdateUIMode mode
);
2454 Sets the text for this UI element.
2456 void SetText(const wxString
& text
);
2459 Sets the interval between updates in milliseconds.
2461 Set to -1 to disable updates, or to 0 to update as frequently as possible.
2464 Use this to reduce the overhead of UI update events if your application
2465 has a lot of windows. If you set the value to -1 or greater than 0,
2466 you may also need to call wxWindow::UpdateWindowUI at appropriate points
2467 in your application, such as when a dialog is about to be shown.
2469 static void SetUpdateInterval(long updateInterval
);
2472 Show or hide the UI element.
2474 void Show(bool show
);
2480 @class wxClipboardTextEvent
2482 This class represents the events generated by a control (typically a
2483 wxTextCtrl but other windows can generate these events as well) when its
2484 content gets copied or cut to, or pasted from the clipboard.
2486 There are three types of corresponding events @c wxEVT_TEXT_COPY,
2487 @c wxEVT_TEXT_CUT and @c wxEVT_TEXT_PASTE.
2489 If any of these events is processed (without being skipped) by an event
2490 handler, the corresponding operation doesn't take place which allows to
2491 prevent the text from being copied from or pasted to a control. It is also
2492 possible to examine the clipboard contents in the PASTE event handler and
2493 transform it in some way before inserting in a control -- for example,
2494 changing its case or removing invalid characters.
2496 Finally notice that a CUT event is always preceded by the COPY event which
2497 makes it possible to only process the latter if it doesn't matter if the
2498 text was copied or cut.
2501 These events are currently only generated by wxTextCtrl in wxGTK and wxOSX
2502 but are also generated by wxComboBox without wxCB_READONLY style in wxMSW.
2504 @beginEventTable{wxClipboardTextEvent}
2505 @event{EVT_TEXT_COPY(id, func)}
2506 Some or all of the controls content was copied to the clipboard.
2507 @event{EVT_TEXT_CUT(id, func)}
2508 Some or all of the controls content was cut (i.e. copied and
2510 @event{EVT_TEXT_PASTE(id, func)}
2511 Clipboard content was pasted into the control.
2520 class wxClipboardTextEvent
: public wxCommandEvent
2526 wxClipboardTextEvent(wxEventType commandType
= wxEVT_NULL
, int id
= 0);
2530 Possible axis values for mouse wheel scroll events.
2534 enum wxMouseWheelAxis
2536 wxMOUSE_WHEEL_VERTICAL
, ///< Vertical scroll event.
2537 wxMOUSE_WHEEL_HORIZONTAL
///< Horizontal scroll event.
2544 This event class contains information about the events generated by the mouse:
2545 they include mouse buttons press and release events and mouse move events.
2547 All mouse events involving the buttons use @c wxMOUSE_BTN_LEFT for the
2548 left mouse button, @c wxMOUSE_BTN_MIDDLE for the middle one and
2549 @c wxMOUSE_BTN_RIGHT for the right one. And if the system supports more
2550 buttons, the @c wxMOUSE_BTN_AUX1 and @c wxMOUSE_BTN_AUX2 events
2551 can also be generated. Note that not all mice have even a middle button so a
2552 portable application should avoid relying on the events from it (but the right
2553 button click can be emulated using the left mouse button with the control key
2554 under Mac platforms with a single button mouse).
2556 For the @c wxEVT_ENTER_WINDOW and @c wxEVT_LEAVE_WINDOW events
2557 purposes, the mouse is considered to be inside the window if it is in the
2558 window client area and not inside one of its children. In other words, the
2559 parent window receives @c wxEVT_LEAVE_WINDOW event not only when the
2560 mouse leaves the window entirely but also when it enters one of its children.
2562 The position associated with a mouse event is expressed in the window
2563 coordinates of the window which generated the event, you can use
2564 wxWindow::ClientToScreen() to convert it to screen coordinates and possibly
2565 call wxWindow::ScreenToClient() next to convert it to window coordinates of
2568 @note Note that under Windows CE mouse enter and leave events are not natively
2569 supported by the system but are generated by wxWidgets itself. This has several
2570 drawbacks: the LEAVE_WINDOW event might be received some time after the mouse
2571 left the window and the state variables for it may have changed during this time.
2573 @note Note the difference between methods like wxMouseEvent::LeftDown and
2574 the inherited wxMouseState::LeftIsDown: the former returns @true when
2575 the event corresponds to the left mouse button click while the latter
2576 returns @true if the left mouse button is currently being pressed.
2577 For example, when the user is dragging the mouse you can use
2578 wxMouseEvent::LeftIsDown to test whether the left mouse button is
2579 (still) depressed. Also, by convention, if wxMouseEvent::LeftDown
2580 returns @true, wxMouseEvent::LeftIsDown will also return @true in
2581 wxWidgets whatever the underlying GUI behaviour is (which is
2582 platform-dependent). The same applies, of course, to other mouse
2586 @beginEventTable{wxMouseEvent}
2587 @event{EVT_LEFT_DOWN(func)}
2588 Process a @c wxEVT_LEFT_DOWN event. The handler of this event should normally
2589 call event.Skip() to allow the default processing to take place as otherwise
2590 the window under mouse wouldn't get the focus.
2591 @event{EVT_LEFT_UP(func)}
2592 Process a @c wxEVT_LEFT_UP event.
2593 @event{EVT_LEFT_DCLICK(func)}
2594 Process a @c wxEVT_LEFT_DCLICK event.
2595 @event{EVT_MIDDLE_DOWN(func)}
2596 Process a @c wxEVT_MIDDLE_DOWN event.
2597 @event{EVT_MIDDLE_UP(func)}
2598 Process a @c wxEVT_MIDDLE_UP event.
2599 @event{EVT_MIDDLE_DCLICK(func)}
2600 Process a @c wxEVT_MIDDLE_DCLICK event.
2601 @event{EVT_RIGHT_DOWN(func)}
2602 Process a @c wxEVT_RIGHT_DOWN event.
2603 @event{EVT_RIGHT_UP(func)}
2604 Process a @c wxEVT_RIGHT_UP event.
2605 @event{EVT_RIGHT_DCLICK(func)}
2606 Process a @c wxEVT_RIGHT_DCLICK event.
2607 @event{EVT_MOUSE_AUX1_DOWN(func)}
2608 Process a @c wxEVT_AUX1_DOWN event.
2609 @event{EVT_MOUSE_AUX1_UP(func)}
2610 Process a @c wxEVT_AUX1_UP event.
2611 @event{EVT_MOUSE_AUX1_DCLICK(func)}
2612 Process a @c wxEVT_AUX1_DCLICK event.
2613 @event{EVT_MOUSE_AUX2_DOWN(func)}
2614 Process a @c wxEVT_AUX2_DOWN event.
2615 @event{EVT_MOUSE_AUX2_UP(func)}
2616 Process a @c wxEVT_AUX2_UP event.
2617 @event{EVT_MOUSE_AUX2_DCLICK(func)}
2618 Process a @c wxEVT_AUX2_DCLICK event.
2619 @event{EVT_MOTION(func)}
2620 Process a @c wxEVT_MOTION event.
2621 @event{EVT_ENTER_WINDOW(func)}
2622 Process a @c wxEVT_ENTER_WINDOW event.
2623 @event{EVT_LEAVE_WINDOW(func)}
2624 Process a @c wxEVT_LEAVE_WINDOW event.
2625 @event{EVT_MOUSEWHEEL(func)}
2626 Process a @c wxEVT_MOUSEWHEEL event.
2627 @event{EVT_MOUSE_EVENTS(func)}
2628 Process all mouse events.
2636 class wxMouseEvent
: public wxEvent
,
2641 Constructor. Valid event types are:
2643 @li @c wxEVT_ENTER_WINDOW
2644 @li @c wxEVT_LEAVE_WINDOW
2645 @li @c wxEVT_LEFT_DOWN
2646 @li @c wxEVT_LEFT_UP
2647 @li @c wxEVT_LEFT_DCLICK
2648 @li @c wxEVT_MIDDLE_DOWN
2649 @li @c wxEVT_MIDDLE_UP
2650 @li @c wxEVT_MIDDLE_DCLICK
2651 @li @c wxEVT_RIGHT_DOWN
2652 @li @c wxEVT_RIGHT_UP
2653 @li @c wxEVT_RIGHT_DCLICK
2654 @li @c wxEVT_AUX1_DOWN
2655 @li @c wxEVT_AUX1_UP
2656 @li @c wxEVT_AUX1_DCLICK
2657 @li @c wxEVT_AUX2_DOWN
2658 @li @c wxEVT_AUX2_UP
2659 @li @c wxEVT_AUX2_DCLICK
2661 @li @c wxEVT_MOUSEWHEEL
2663 wxMouseEvent(wxEventType mouseEventType
= wxEVT_NULL
);
2666 Returns @true if the event was a first extra button double click.
2668 bool Aux1DClick() const;
2671 Returns @true if the first extra button mouse button changed to down.
2673 bool Aux1Down() const;
2676 Returns @true if the first extra button mouse button changed to up.
2678 bool Aux1Up() const;
2681 Returns @true if the event was a second extra button double click.
2683 bool Aux2DClick() const;
2686 Returns @true if the second extra button mouse button changed to down.
2688 bool Aux2Down() const;
2691 Returns @true if the second extra button mouse button changed to up.
2693 bool Aux2Up() const;
2696 Returns @true if the event was generated by the specified button.
2698 @see wxMouseState::ButtoinIsDown()
2700 bool Button(wxMouseButton but
) const;
2703 If the argument is omitted, this returns @true if the event was a mouse
2704 double click event. Otherwise the argument specifies which double click event
2705 was generated (see Button() for the possible values).
2707 bool ButtonDClick(wxMouseButton but
= wxMOUSE_BTN_ANY
) const;
2710 If the argument is omitted, this returns @true if the event was a mouse
2711 button down event. Otherwise the argument specifies which button-down event
2712 was generated (see Button() for the possible values).
2714 bool ButtonDown(wxMouseButton but
= wxMOUSE_BTN_ANY
) const;
2717 If the argument is omitted, this returns @true if the event was a mouse
2718 button up event. Otherwise the argument specifies which button-up event
2719 was generated (see Button() for the possible values).
2721 bool ButtonUp(wxMouseButton but
= wxMOUSE_BTN_ANY
) const;
2724 Returns @true if this was a dragging event (motion while a button is depressed).
2728 bool Dragging() const;
2731 Returns @true if the mouse was entering the window.
2735 bool Entering() const;
2738 Returns the mouse button which generated this event or @c wxMOUSE_BTN_NONE
2739 if no button is involved (for mouse move, enter or leave event, for example).
2740 Otherwise @c wxMOUSE_BTN_LEFT is returned for the left button down, up and
2741 double click events, @c wxMOUSE_BTN_MIDDLE and @c wxMOUSE_BTN_RIGHT
2742 for the same events for the middle and the right buttons respectively.
2744 int GetButton() const;
2747 Returns the number of mouse clicks for this event: 1 for a simple click, 2
2748 for a double-click, 3 for a triple-click and so on.
2750 Currently this function is implemented only in wxMac and returns -1 for the
2751 other platforms (you can still distinguish simple clicks from double-clicks as
2752 they generate different kinds of events however).
2756 int GetClickCount() const;
2759 Returns the configured number of lines (or whatever) to be scrolled per
2762 Default value under most platforms is three.
2764 @see GetColumnsPerAction()
2766 int GetLinesPerAction() const;
2769 Returns the configured number of columns (or whatever) to be scrolled per
2772 Default value under most platforms is three.
2774 @see GetLinesPerAction()
2778 int GetColumnsPerAction() const;
2781 Returns the logical mouse position in pixels (i.e.\ translated according to the
2782 translation set for the DC, which usually indicates that the window has been
2785 wxPoint
GetLogicalPosition(const wxDC
& dc
) const;
2788 Get wheel delta, normally 120.
2790 This is the threshold for action to be taken, and one such action
2791 (for example, scrolling one increment) should occur for each delta.
2793 int GetWheelDelta() const;
2796 Get wheel rotation, positive or negative indicates direction of rotation.
2798 Current devices all send an event when rotation is at least +/-WheelDelta, but
2799 finer resolution devices can be created in the future.
2801 Because of this you shouldn't assume that one event is equal to 1 line, but you
2802 should be able to either do partial line scrolling or wait until several
2803 events accumulate before scrolling.
2805 int GetWheelRotation() const;
2808 Gets the axis the wheel operation concerns.
2810 Usually the mouse wheel is used to scroll vertically so @c
2811 wxMOUSE_WHEEL_VERTICAL is returned but some mice (and most trackpads)
2812 also allow to use the wheel to scroll horizontally in which case
2813 @c wxMOUSE_WHEEL_HORIZONTAL is returned.
2815 Notice that before wxWidgets 2.9.4 this method returned @c int.
2817 wxMouseWheelAxis
GetWheelAxis() const;
2820 Returns @true if the event was a mouse button event (not necessarily a button
2821 down event - that may be tested using ButtonDown()).
2823 bool IsButton() const;
2826 Returns @true if the system has been setup to do page scrolling with
2827 the mouse wheel instead of line scrolling.
2829 bool IsPageScroll() const;
2832 Returns @true if the mouse was leaving the window.
2836 bool Leaving() const;
2839 Returns @true if the event was a left double click.
2841 bool LeftDClick() const;
2844 Returns @true if the left mouse button changed to down.
2846 bool LeftDown() const;
2849 Returns @true if the left mouse button changed to up.
2851 bool LeftUp() const;
2854 Returns @true if the Meta key was down at the time of the event.
2856 bool MetaDown() const;
2859 Returns @true if the event was a middle double click.
2861 bool MiddleDClick() const;
2864 Returns @true if the middle mouse button changed to down.
2866 bool MiddleDown() const;
2869 Returns @true if the middle mouse button changed to up.
2871 bool MiddleUp() const;
2874 Returns @true if this was a motion event and no mouse buttons were pressed.
2875 If any mouse button is held pressed, then this method returns @false and
2876 Dragging() returns @true.
2878 bool Moving() const;
2881 Returns @true if the event was a right double click.
2883 bool RightDClick() const;
2886 Returns @true if the right mouse button changed to down.
2888 bool RightDown() const;
2891 Returns @true if the right mouse button changed to up.
2893 bool RightUp() const;
2899 @class wxDropFilesEvent
2901 This class is used for drop files events, that is, when files have been dropped
2902 onto the window. This functionality is currently only available under Windows.
2904 The window must have previously been enabled for dropping by calling
2905 wxWindow::DragAcceptFiles().
2907 Important note: this is a separate implementation to the more general drag and drop
2908 implementation documented in the @ref overview_dnd. It uses the older, Windows
2909 message-based approach of dropping files.
2911 @beginEventTable{wxDropFilesEvent}
2912 @event{EVT_DROP_FILES(func)}
2913 Process a @c wxEVT_DROP_FILES event.
2921 @see @ref overview_events
2923 class wxDropFilesEvent
: public wxEvent
2929 wxDropFilesEvent(wxEventType id
= 0, int noFiles
= 0,
2930 wxString
* files
= NULL
);
2933 Returns an array of filenames.
2935 wxString
* GetFiles() const;
2938 Returns the number of files dropped.
2940 int GetNumberOfFiles() const;
2943 Returns the position at which the files were dropped.
2944 Returns an array of filenames.
2946 wxPoint
GetPosition() const;
2952 @class wxActivateEvent
2954 An activate event is sent when a window or application is being activated
2957 @beginEventTable{wxActivateEvent}
2958 @event{EVT_ACTIVATE(func)}
2959 Process a @c wxEVT_ACTIVATE event.
2960 @event{EVT_ACTIVATE_APP(func)}
2961 Process a @c wxEVT_ACTIVATE_APP event.
2962 This event is received by the wxApp-derived instance only.
2963 @event{EVT_HIBERNATE(func)}
2964 Process a hibernate event, supplying the member function. This event applies
2965 to wxApp only, and only on Windows SmartPhone and PocketPC.
2966 It is generated when the system is low on memory; the application should free
2967 up as much memory as possible, and restore full working state when it receives
2968 a @c wxEVT_ACTIVATE or @c wxEVT_ACTIVATE_APP event.
2974 @see @ref overview_events, wxApp::IsActive
2976 class wxActivateEvent
: public wxEvent
2982 wxActivateEvent(wxEventType eventType
= wxEVT_NULL
, bool active
= true,
2986 Returns @true if the application or window is being activated, @false otherwise.
2988 bool GetActive() const;
2994 @class wxContextMenuEvent
2996 This class is used for context menu events, sent to give
2997 the application a chance to show a context (popup) menu for a wxWindow.
2999 Note that if wxContextMenuEvent::GetPosition returns wxDefaultPosition, this
3000 means that the event originated from a keyboard context button event, and you
3001 should compute a suitable position yourself, for example by calling wxGetMousePosition().
3003 Notice that the exact sequence of mouse events is different across the
3004 platforms. For example, under MSW the context menu event is generated after
3005 @c EVT_RIGHT_UP event and only if it was not handled but under GTK the
3006 context menu event is generated after @c EVT_RIGHT_DOWN event. This is
3007 correct in the sense that it ensures that the context menu is shown
3008 according to the current platform UI conventions and also means that you
3009 must not handle (or call wxEvent::Skip() in your handler if you do have
3010 one) neither right mouse down nor right mouse up event if you plan on
3011 handling @c EVT_CONTEXT_MENU event.
3013 @beginEventTable{wxContextMenuEvent}
3014 @event{EVT_CONTEXT_MENU(func)}
3015 A right click (or other context menu command depending on platform) has been detected.
3022 @see wxCommandEvent, @ref overview_events
3024 class wxContextMenuEvent
: public wxCommandEvent
3030 wxContextMenuEvent(wxEventType type
= wxEVT_NULL
, int id
= 0,
3031 const wxPoint
& pos
= wxDefaultPosition
);
3034 Returns the position in screen coordinates at which the menu should be shown.
3035 Use wxWindow::ScreenToClient to convert to client coordinates.
3037 You can also omit a position from wxWindow::PopupMenu in order to use
3038 the current mouse pointer position.
3040 If the event originated from a keyboard event, the value returned from this
3041 function will be wxDefaultPosition.
3043 const wxPoint
& GetPosition() const;
3046 Sets the position at which the menu should be shown.
3048 void SetPosition(const wxPoint
& point
);
3056 An erase event is sent when a window's background needs to be repainted.
3058 On some platforms, such as GTK+, this event is simulated (simply generated just
3059 before the paint event) and may cause flicker. It is therefore recommended that
3060 you set the text background colour explicitly in order to prevent flicker.
3061 The default background colour under GTK+ is grey.
3063 To intercept this event, use the EVT_ERASE_BACKGROUND macro in an event table
3066 You must use the device context returned by GetDC() to draw on, don't create
3067 a wxPaintDC in the event handler.
3069 @beginEventTable{wxEraseEvent}
3070 @event{EVT_ERASE_BACKGROUND(func)}
3071 Process a @c wxEVT_ERASE_BACKGROUND event.
3077 @see @ref overview_events
3079 class wxEraseEvent
: public wxEvent
3085 wxEraseEvent(int id
= 0, wxDC
* dc
= NULL
);
3088 Returns the device context associated with the erase event to draw on.
3090 The returned pointer is never @NULL.
3092 wxDC
* GetDC() const;
3100 A focus event is sent when a window's focus changes. The window losing focus
3101 receives a "kill focus" event while the window gaining it gets a "set focus" one.
3103 Notice that the set focus event happens both when the user gives focus to the
3104 window (whether using the mouse or keyboard) and when it is done from the
3105 program itself using wxWindow::SetFocus.
3107 The focus event handlers should almost invariably call wxEvent::Skip() on
3108 their event argument to allow the default handling to take place. Failure
3109 to do this may result in incorrect behaviour of the native controls. Also
3110 note that wxEVT_KILL_FOCUS handler must not call wxWindow::SetFocus() as
3111 this, again, is not supported by all native controls. If you need to do
3112 this, consider using the @ref sec_delayed_action described in wxIdleEvent
3115 @beginEventTable{wxFocusEvent}
3116 @event{EVT_SET_FOCUS(func)}
3117 Process a @c wxEVT_SET_FOCUS event.
3118 @event{EVT_KILL_FOCUS(func)}
3119 Process a @c wxEVT_KILL_FOCUS event.
3125 @see @ref overview_events
3127 class wxFocusEvent
: public wxEvent
3133 wxFocusEvent(wxEventType eventType
= wxEVT_NULL
, int id
= 0);
3136 Returns the window associated with this event, that is the window which had the
3137 focus before for the @c wxEVT_SET_FOCUS event and the window which is
3138 going to receive focus for the @c wxEVT_KILL_FOCUS one.
3140 Warning: the window pointer may be @NULL!
3142 wxWindow
*GetWindow() const;
3144 void SetWindow(wxWindow
*win
);
3150 @class wxChildFocusEvent
3152 A child focus event is sent to a (parent-)window when one of its child windows
3153 gains focus, so that the window could restore the focus back to its corresponding
3154 child if it loses it now and regains later.
3156 Notice that child window is the direct child of the window receiving event.
3157 Use wxWindow::FindFocus() to retrieve the window which is actually getting focus.
3159 @beginEventTable{wxChildFocusEvent}
3160 @event{EVT_CHILD_FOCUS(func)}
3161 Process a @c wxEVT_CHILD_FOCUS event.
3167 @see @ref overview_events
3169 class wxChildFocusEvent
: public wxCommandEvent
3176 The direct child which is (or which contains the window which is) receiving
3179 wxChildFocusEvent(wxWindow
* win
= NULL
);
3182 Returns the direct child which receives the focus, or a (grand-)parent of the
3183 control receiving the focus.
3185 To get the actually focused control use wxWindow::FindFocus.
3187 wxWindow
*GetWindow() const;
3193 @class wxMouseCaptureLostEvent
3195 A mouse capture lost event is sent to a window that had obtained mouse capture,
3196 which was subsequently lost due to an "external" event (for example, when a dialog
3197 box is shown or if another application captures the mouse).
3199 If this happens, this event is sent to all windows that are on the capture stack
3200 (i.e. called CaptureMouse, but didn't call ReleaseMouse yet). The event is
3201 not sent if the capture changes because of a call to CaptureMouse or
3204 This event is currently emitted under Windows only.
3206 @beginEventTable{wxMouseCaptureLostEvent}
3207 @event{EVT_MOUSE_CAPTURE_LOST(func)}
3208 Process a @c wxEVT_MOUSE_CAPTURE_LOST event.
3216 @see wxMouseCaptureChangedEvent, @ref overview_events,
3217 wxWindow::CaptureMouse, wxWindow::ReleaseMouse, wxWindow::GetCapture
3219 class wxMouseCaptureLostEvent
: public wxEvent
3225 wxMouseCaptureLostEvent(wxWindowID windowId
= 0);
3230 class wxDisplayChangedEvent
: public wxEvent
3233 wxDisplayChangedEvent();
3237 class wxPaletteChangedEvent
: public wxEvent
3240 wxPaletteChangedEvent(wxWindowID winid
= 0);
3242 void SetChangedWindow(wxWindow
* win
);
3243 wxWindow
* GetChangedWindow() const;
3247 class wxQueryNewPaletteEvent
: public wxEvent
3250 wxQueryNewPaletteEvent(wxWindowID winid
= 0);
3252 void SetPaletteRealized(bool realized
);
3253 bool GetPaletteRealized();
3260 @class wxNotifyEvent
3262 This class is not used by the event handlers by itself, but is a base class
3263 for other event classes (such as wxBookCtrlEvent).
3265 It (or an object of a derived class) is sent when the controls state is being
3266 changed and allows the program to wxNotifyEvent::Veto() this change if it wants
3267 to prevent it from happening.
3272 @see wxBookCtrlEvent
3274 class wxNotifyEvent
: public wxCommandEvent
3278 Constructor (used internally by wxWidgets only).
3280 wxNotifyEvent(wxEventType eventType
= wxEVT_NULL
, int id
= 0);
3283 This is the opposite of Veto(): it explicitly allows the event to be processed.
3284 For most events it is not necessary to call this method as the events are allowed
3285 anyhow but some are forbidden by default (this will be mentioned in the corresponding
3291 Returns @true if the change is allowed (Veto() hasn't been called) or @false
3292 otherwise (if it was).
3294 bool IsAllowed() const;
3297 Prevents the change announced by this event from happening.
3299 It is in general a good idea to notify the user about the reasons for vetoing
3300 the change because otherwise the applications behaviour (which just refuses to
3301 do what the user wants) might be quite surprising.
3308 @class wxThreadEvent
3310 This class adds some simple functionality to wxEvent to facilitate
3311 inter-thread communication.
3313 This event is not natively emitted by any control/class: it is just
3314 a helper class for the user.
3315 Its most important feature is the GetEventCategory() implementation which
3316 allows thread events @b NOT to be processed by wxEventLoopBase::YieldFor calls
3317 (unless the @c wxEVT_CATEGORY_THREAD is specified - which is never in wx code).
3320 @category{events,threading}
3322 @see @ref overview_thread, wxEventLoopBase::YieldFor
3326 class wxThreadEvent
: public wxEvent
3332 wxThreadEvent(wxEventType eventType
= wxEVT_THREAD
, int id
= wxID_ANY
);
3335 Clones this event making sure that all internal members which use
3336 COW (only @c m_commandString for now; see @ref overview_refcount)
3337 are unshared (see wxObject::UnShare).
3339 virtual wxEvent
*Clone() const;
3342 Returns @c wxEVT_CATEGORY_THREAD.
3344 This is important to avoid unwanted processing of thread events
3345 when calling wxEventLoopBase::YieldFor().
3347 virtual wxEventCategory
GetEventCategory() const;
3350 Sets custom data payload.
3352 The @a payload argument may be of any type that wxAny can handle
3353 (i.e. pretty much anything). Note that T's copy constructor must be
3354 thread-safe, i.e. create a copy that doesn't share anything with
3355 the original (see Clone()).
3357 @note This method is not available with Visual C++ 6.
3361 @see GetPayload(), wxAny
3363 template<typename T
>
3364 void SetPayload(const T
& payload
);
3367 Get custom data payload.
3369 Correct type is checked in debug builds.
3371 @note This method is not available with Visual C++ 6.
3375 @see SetPayload(), wxAny
3377 template<typename T
>
3378 T
GetPayload() const;
3381 Returns extra information integer value.
3383 long GetExtraLong() const;
3386 Returns stored integer value.
3391 Returns stored string value.
3393 wxString
GetString() const;
3397 Sets the extra information value.
3399 void SetExtraLong(long extraLong
);
3402 Sets the integer value.
3404 void SetInt(int intCommand
);
3407 Sets the string value.
3409 void SetString(const wxString
& string
);
3416 A help event is sent when the user has requested context-sensitive help.
3417 This can either be caused by the application requesting context-sensitive help mode
3418 via wxContextHelp, or (on MS Windows) by the system generating a WM_HELP message when
3419 the user pressed F1 or clicked on the query button in a dialog caption.
3421 A help event is sent to the window that the user clicked on, and is propagated
3422 up the window hierarchy until the event is processed or there are no more event
3425 The application should call wxEvent::GetId to check the identity of the
3426 clicked-on window, and then either show some suitable help or call wxEvent::Skip()
3427 if the identifier is unrecognised.
3429 Calling Skip is important because it allows wxWidgets to generate further
3430 events for ancestors of the clicked-on window. Otherwise it would be impossible to
3431 show help for container windows, since processing would stop after the first window
3434 @beginEventTable{wxHelpEvent}
3435 @event{EVT_HELP(id, func)}
3436 Process a @c wxEVT_HELP event.
3437 @event{EVT_HELP_RANGE(id1, id2, func)}
3438 Process a @c wxEVT_HELP event for a range of ids.
3444 @see wxContextHelp, wxDialog, @ref overview_events
3446 class wxHelpEvent
: public wxCommandEvent
3450 Indicates how a wxHelpEvent was generated.
3454 Origin_Unknown
, /**< unrecognized event source. */
3455 Origin_Keyboard
, /**< event generated from F1 key press. */
3457 /** event generated by wxContextHelp or from the [?] button on
3458 the title bar (Windows). */
3465 wxHelpEvent(wxEventType type
= wxEVT_NULL
,
3466 wxWindowID winid
= 0,
3467 const wxPoint
& pt
= wxDefaultPosition
,
3468 wxHelpEvent::Origin origin
= Origin_Unknown
);
3471 Returns the origin of the help event which is one of the wxHelpEvent::Origin
3474 The application may handle events generated using the keyboard or mouse
3475 differently, e.g. by using wxGetMousePosition() for the mouse events.
3479 wxHelpEvent::Origin
GetOrigin() const;
3482 Returns the left-click position of the mouse, in screen coordinates.
3483 This allows the application to position the help appropriately.
3485 const wxPoint
& GetPosition() const;
3488 Set the help event origin, only used internally by wxWidgets normally.
3492 void SetOrigin(wxHelpEvent::Origin origin
);
3495 Sets the left-click position of the mouse, in screen coordinates.
3497 void SetPosition(const wxPoint
& pt
);
3503 @class wxScrollEvent
3505 A scroll event holds information about events sent from stand-alone
3506 scrollbars (see wxScrollBar) and sliders (see wxSlider).
3508 Note that scrolled windows send the wxScrollWinEvent which does not derive from
3509 wxCommandEvent, but from wxEvent directly - don't confuse these two kinds of
3510 events and use the event table macros mentioned below only for the scrollbar-like
3513 @section scrollevent_diff The difference between EVT_SCROLL_THUMBRELEASE and EVT_SCROLL_CHANGED
3515 The EVT_SCROLL_THUMBRELEASE event is only emitted when actually dragging the thumb
3516 using the mouse and releasing it (This EVT_SCROLL_THUMBRELEASE event is also followed
3517 by an EVT_SCROLL_CHANGED event).
3519 The EVT_SCROLL_CHANGED event also occurs when using the keyboard to change the thumb
3520 position, and when clicking next to the thumb (In all these cases the EVT_SCROLL_THUMBRELEASE
3521 event does not happen).
3523 In short, the EVT_SCROLL_CHANGED event is triggered when scrolling/ moving has finished
3524 independently of the way it had started. Please see the widgets sample ("Slider" page)
3525 to see the difference between EVT_SCROLL_THUMBRELEASE and EVT_SCROLL_CHANGED in action.
3528 Note that unless specifying a scroll control identifier, you will need to test for scrollbar
3529 orientation with wxScrollEvent::GetOrientation, since horizontal and vertical scroll events
3530 are processed using the same event handler.
3532 @beginEventTable{wxScrollEvent}
3533 You can use EVT_COMMAND_SCROLL... macros with window IDs for when intercepting
3534 scroll events from controls, or EVT_SCROLL... macros without window IDs for
3535 intercepting scroll events from the receiving window -- except for this, the
3536 macros behave exactly the same.
3537 @event{EVT_SCROLL(func)}
3538 Process all scroll events.
3539 @event{EVT_SCROLL_TOP(func)}
3540 Process @c wxEVT_SCROLL_TOP scroll-to-top events (minimum position).
3541 @event{EVT_SCROLL_BOTTOM(func)}
3542 Process @c wxEVT_SCROLL_BOTTOM scroll-to-bottom events (maximum position).
3543 @event{EVT_SCROLL_LINEUP(func)}
3544 Process @c wxEVT_SCROLL_LINEUP line up events.
3545 @event{EVT_SCROLL_LINEDOWN(func)}
3546 Process @c wxEVT_SCROLL_LINEDOWN line down events.
3547 @event{EVT_SCROLL_PAGEUP(func)}
3548 Process @c wxEVT_SCROLL_PAGEUP page up events.
3549 @event{EVT_SCROLL_PAGEDOWN(func)}
3550 Process @c wxEVT_SCROLL_PAGEDOWN page down events.
3551 @event{EVT_SCROLL_THUMBTRACK(func)}
3552 Process @c wxEVT_SCROLL_THUMBTRACK thumbtrack events (frequent events sent as the
3553 user drags the thumbtrack).
3554 @event{EVT_SCROLL_THUMBRELEASE(func)}
3555 Process @c wxEVT_SCROLL_THUMBRELEASE thumb release events.
3556 @event{EVT_SCROLL_CHANGED(func)}
3557 Process @c wxEVT_SCROLL_CHANGED end of scrolling events (MSW only).
3558 @event{EVT_COMMAND_SCROLL(id, func)}
3559 Process all scroll events.
3560 @event{EVT_COMMAND_SCROLL_TOP(id, func)}
3561 Process @c wxEVT_SCROLL_TOP scroll-to-top events (minimum position).
3562 @event{EVT_COMMAND_SCROLL_BOTTOM(id, func)}
3563 Process @c wxEVT_SCROLL_BOTTOM scroll-to-bottom events (maximum position).
3564 @event{EVT_COMMAND_SCROLL_LINEUP(id, func)}
3565 Process @c wxEVT_SCROLL_LINEUP line up events.
3566 @event{EVT_COMMAND_SCROLL_LINEDOWN(id, func)}
3567 Process @c wxEVT_SCROLL_LINEDOWN line down events.
3568 @event{EVT_COMMAND_SCROLL_PAGEUP(id, func)}
3569 Process @c wxEVT_SCROLL_PAGEUP page up events.
3570 @event{EVT_COMMAND_SCROLL_PAGEDOWN(id, func)}
3571 Process @c wxEVT_SCROLL_PAGEDOWN page down events.
3572 @event{EVT_COMMAND_SCROLL_THUMBTRACK(id, func)}
3573 Process @c wxEVT_SCROLL_THUMBTRACK thumbtrack events (frequent events sent
3574 as the user drags the thumbtrack).
3575 @event{EVT_COMMAND_SCROLL_THUMBRELEASE(func)}
3576 Process @c wxEVT_SCROLL_THUMBRELEASE thumb release events.
3577 @event{EVT_COMMAND_SCROLL_CHANGED(func)}
3578 Process @c wxEVT_SCROLL_CHANGED end of scrolling events (MSW only).
3584 @see wxScrollBar, wxSlider, wxSpinButton, wxScrollWinEvent, @ref overview_events
3586 class wxScrollEvent
: public wxCommandEvent
3592 wxScrollEvent(wxEventType commandType
= wxEVT_NULL
, int id
= 0, int pos
= 0,
3593 int orientation
= 0);
3596 Returns wxHORIZONTAL or wxVERTICAL, depending on the orientation of the
3599 int GetOrientation() const;
3602 Returns the position of the scrollbar.
3604 int GetPosition() const;
3607 void SetOrientation(int orient
);
3608 void SetPosition(int pos
);
3616 See wxIdleEvent::SetMode() for more info.
3620 /** Send idle events to all windows */
3623 /** Send idle events to windows that have the wxWS_EX_PROCESS_IDLE flag specified */
3624 wxIDLE_PROCESS_SPECIFIED
3631 This class is used for idle events, which are generated when the system becomes
3632 idle. Note that, unless you do something specifically, the idle events are not
3633 sent if the system remains idle once it has become it, e.g. only a single idle
3634 event will be generated until something else resulting in more normal events
3635 happens and only then is the next idle event sent again.
3637 If you need to ensure a continuous stream of idle events, you can either use
3638 wxIdleEvent::RequestMore method in your handler or call wxWakeUpIdle() periodically
3639 (for example from a timer event handler), but note that both of these approaches
3640 (and especially the first one) increase the system load and so should be avoided
3643 By default, idle events are sent to all windows, including even the hidden
3644 ones because they may be shown if some condition is met from their @c
3645 wxEVT_IDLE (or related @c wxEVT_UPDATE_UI) handler. The children of hidden
3646 windows do not receive idle events however as they can't change their state
3647 in any way noticeable by the user. Finally, the global wxApp object also
3648 receives these events, as usual, so it can be used for any global idle time
3651 If sending idle events to all windows is causing a significant overhead in
3652 your application, you can call wxIdleEvent::SetMode with the value
3653 wxIDLE_PROCESS_SPECIFIED, and set the wxWS_EX_PROCESS_IDLE extra window
3654 style for every window which should receive idle events, all the other ones
3655 will not receive them in this case.
3657 @beginEventTable{wxIdleEvent}
3658 @event{EVT_IDLE(func)}
3659 Process a @c wxEVT_IDLE event.
3665 @section sec_delayed_action Delayed Action Mechanism
3667 wxIdleEvent can be used to perform some action "at slightly later time".
3668 This can be necessary in several circumstances when, for whatever reason,
3669 something can't be done in the current event handler. For example, if a
3670 mouse event handler is called with the mouse button pressed, the mouse can
3671 be currently captured and some operations with it -- notably capturing it
3672 again -- might be impossible or lead to undesirable results. If you still
3673 want to capture it, you can do it from @c wxEVT_IDLE handler when it is
3674 called the next time instead of doing it immediately.
3676 This can be achieved in two different ways: when using static event tables,
3677 you will need a flag indicating to the (always connected) idle event
3678 handler whether the desired action should be performed. The originally
3679 called handler would then set it to indicate that it should indeed be done
3680 and the idle handler itself would reset it to prevent it from doing the
3683 Using dynamically connected event handlers things are even simpler as the
3684 original event handler can simply wxEvtHandler::Connect() or
3685 wxEvtHandler::Bind() the idle event handler which would only be executed
3686 then and could wxEvtHandler::Disconnect() or wxEvtHandler::Unbind() itself.
3689 @see @ref overview_events, wxUpdateUIEvent, wxWindow::OnInternalIdle
3691 class wxIdleEvent
: public wxEvent
3700 Static function returning a value specifying how wxWidgets will send idle
3701 events: to all windows, or only to those which specify that they
3702 will process the events.
3706 static wxIdleMode
GetMode();
3709 Returns @true if the OnIdle function processing this event requested more
3714 bool MoreRequested() const;
3717 Tells wxWidgets that more processing is required.
3719 This function can be called by an OnIdle handler for a window or window event
3720 handler to indicate that wxApp::OnIdle should forward the OnIdle event once
3721 more to the application windows.
3723 If no window calls this function during OnIdle, then the application will
3724 remain in a passive event loop (not calling OnIdle) until a new event is
3725 posted to the application by the windowing system.
3727 @see MoreRequested()
3729 void RequestMore(bool needMore
= true);
3732 Static function for specifying how wxWidgets will send idle events: to
3733 all windows, or only to those which specify that they will process the events.
3736 Can be one of the ::wxIdleMode values.
3737 The default is wxIDLE_PROCESS_ALL.
3739 static void SetMode(wxIdleMode mode
);
3742 #endif // wxUSE_BASE
3747 @class wxInitDialogEvent
3749 A wxInitDialogEvent is sent as a dialog or panel is being initialised.
3750 Handlers for this event can transfer data to the window.
3752 The default handler calls wxWindow::TransferDataToWindow.
3754 @beginEventTable{wxInitDialogEvent}
3755 @event{EVT_INIT_DIALOG(func)}
3756 Process a @c wxEVT_INIT_DIALOG event.
3762 @see @ref overview_events
3764 class wxInitDialogEvent
: public wxEvent
3770 wxInitDialogEvent(int id
= 0);
3776 @class wxWindowDestroyEvent
3778 This event is sent as early as possible during the window destruction
3781 For the top level windows, as early as possible means that this is done by
3782 wxFrame or wxDialog destructor, i.e. after the destructor of the derived
3783 class was executed and so any methods specific to the derived class can't
3784 be called any more from this event handler. If you need to do this, you
3785 must call wxWindow::SendDestroyEvent() from your derived class destructor.
3787 For the child windows, this event is generated just before deleting the
3788 window from wxWindow::Destroy() (which is also called when the parent
3789 window is deleted) or from the window destructor if operator @c delete was
3790 used directly (which is not recommended for this very reason).
3792 It is usually pointless to handle this event in the window itself but it ca
3793 be very useful to receive notifications about the window destruction in the
3794 parent window or in any other object interested in this window.
3799 @see @ref overview_events, wxWindowCreateEvent
3801 class wxWindowDestroyEvent
: public wxCommandEvent
3807 wxWindowDestroyEvent(wxWindow
* win
= NULL
);
3809 /// Return the window being destroyed.
3810 wxWindow
*GetWindow() const;
3815 @class wxNavigationKeyEvent
3817 This event class contains information about navigation events,
3818 generated by navigation keys such as tab and page down.
3820 This event is mainly used by wxWidgets implementations.
3821 A wxNavigationKeyEvent handler is automatically provided by wxWidgets
3822 when you enable keyboard navigation inside a window by inheriting it from
3823 wxNavigationEnabled<>.
3825 @beginEventTable{wxNavigationKeyEvent}
3826 @event{EVT_NAVIGATION_KEY(func)}
3827 Process a navigation key event.
3833 @see wxWindow::Navigate, wxWindow::NavigateIn
3835 class wxNavigationKeyEvent
: public wxEvent
3839 Flags which can be used with wxNavigationKeyEvent.
3841 enum wxNavigationKeyEventFlags
3843 IsBackward
= 0x0000,
3849 wxNavigationKeyEvent();
3850 wxNavigationKeyEvent(const wxNavigationKeyEvent
& event
);
3853 Returns the child that has the focus, or @NULL.
3855 wxWindow
* GetCurrentFocus() const;
3858 Returns @true if the navigation was in the forward direction.
3860 bool GetDirection() const;
3863 Returns @true if the navigation event was from a tab key.
3864 This is required for proper navigation over radio buttons.
3866 bool IsFromTab() const;
3869 Returns @true if the navigation event represents a window change
3870 (for example, from Ctrl-Page Down in a notebook).
3872 bool IsWindowChange() const;
3875 Sets the current focus window member.
3877 void SetCurrentFocus(wxWindow
* currentFocus
);
3880 Sets the direction to forward if @a direction is @true, or backward
3883 void SetDirection(bool direction
);
3886 Sets the flags for this event.
3887 The @a flags can be a combination of the
3888 wxNavigationKeyEvent::wxNavigationKeyEventFlags values.
3890 void SetFlags(long flags
);
3893 Marks the navigation event as from a tab key.
3895 void SetFromTab(bool fromTab
);
3898 Marks the event as a window change event.
3900 void SetWindowChange(bool windowChange
);
3906 @class wxMouseCaptureChangedEvent
3908 An mouse capture changed event is sent to a window that loses its
3909 mouse capture. This is called even if wxWindow::ReleaseMouse
3910 was called by the application code. Handling this event allows
3911 an application to cater for unexpected capture releases which
3912 might otherwise confuse mouse handling code.
3916 @beginEventTable{wxMouseCaptureChangedEvent}
3917 @event{EVT_MOUSE_CAPTURE_CHANGED(func)}
3918 Process a @c wxEVT_MOUSE_CAPTURE_CHANGED event.
3924 @see wxMouseCaptureLostEvent, @ref overview_events,
3925 wxWindow::CaptureMouse, wxWindow::ReleaseMouse, wxWindow::GetCapture
3927 class wxMouseCaptureChangedEvent
: public wxEvent
3933 wxMouseCaptureChangedEvent(wxWindowID windowId
= 0,
3934 wxWindow
* gainedCapture
= NULL
);
3937 Returns the window that gained the capture, or @NULL if it was a
3938 non-wxWidgets window.
3940 wxWindow
* GetCapturedWindow() const;
3948 This event class contains information about window and session close events.
3950 The handler function for EVT_CLOSE is called when the user has tried to close a
3951 a frame or dialog box using the window manager (X) or system menu (Windows).
3952 It can also be invoked by the application itself programmatically, for example by
3953 calling the wxWindow::Close function.
3955 You should check whether the application is forcing the deletion of the window
3956 using wxCloseEvent::CanVeto. If this is @false, you @e must destroy the window
3957 using wxWindow::Destroy.
3959 If the return value is @true, it is up to you whether you respond by destroying
3962 If you don't destroy the window, you should call wxCloseEvent::Veto to
3963 let the calling code know that you did not destroy the window.
3964 This allows the wxWindow::Close function to return @true or @false depending
3965 on whether the close instruction was honoured or not.
3967 Example of a wxCloseEvent handler:
3970 void MyFrame::OnClose(wxCloseEvent& event)
3972 if ( event.CanVeto() && m_bFileNotSaved )
3974 if ( wxMessageBox("The file has not been saved... continue closing?",
3976 wxICON_QUESTION | wxYES_NO) != wxYES )
3983 Destroy(); // you may also do: event.Skip();
3984 // since the default event handler does call Destroy(), too
3988 The EVT_END_SESSION event is slightly different as it is sent by the system
3989 when the user session is ending (e.g. because of log out or shutdown) and
3990 so all windows are being forcefully closed. At least under MSW, after the
3991 handler for this event is executed the program is simply killed by the
3992 system. Because of this, the default handler for this event provided by
3993 wxWidgets calls all the usual cleanup code (including wxApp::OnExit()) so
3994 that it could still be executed and exit()s the process itself, without
3995 waiting for being killed. If this behaviour is for some reason undesirable,
3996 make sure that you define a handler for this event in your wxApp-derived
3997 class and do not call @c event.Skip() in it (but be aware that the system
3998 will still kill your application).
4000 @beginEventTable{wxCloseEvent}
4001 @event{EVT_CLOSE(func)}
4002 Process a @c wxEVT_CLOSE_WINDOW command event, supplying the member function.
4003 This event applies to wxFrame and wxDialog classes.
4004 @event{EVT_QUERY_END_SESSION(func)}
4005 Process a @c wxEVT_QUERY_END_SESSION session event, supplying the member function.
4006 This event can be handled in wxApp-derived class only.
4007 @event{EVT_END_SESSION(func)}
4008 Process a @c wxEVT_END_SESSION session event, supplying the member function.
4009 This event can be handled in wxApp-derived class only.
4015 @see wxWindow::Close, @ref overview_windowdeletion
4017 class wxCloseEvent
: public wxEvent
4023 wxCloseEvent(wxEventType commandEventType
= wxEVT_NULL
, int id
= 0);
4026 Returns @true if you can veto a system shutdown or a window close event.
4027 Vetoing a window close event is not possible if the calling code wishes to
4028 force the application to exit, and so this function must be called to check this.
4030 bool CanVeto() const;
4033 Returns @true if the user is just logging off or @false if the system is
4034 shutting down. This method can only be called for end session and query end
4035 session events, it doesn't make sense for close window event.
4037 bool GetLoggingOff() const;
4040 Sets the 'can veto' flag.
4042 void SetCanVeto(bool canVeto
);
4045 Sets the 'logging off' flag.
4047 void SetLoggingOff(bool loggingOff
);
4050 Call this from your event handler to veto a system shutdown or to signal
4051 to the calling application that a window close did not happen.
4053 You can only veto a shutdown if CanVeto() returns @true.
4055 void Veto(bool veto
= true);
4063 This class is used for a variety of menu-related events. Note that
4064 these do not include menu command events, which are
4065 handled using wxCommandEvent objects.
4067 The default handler for @c wxEVT_MENU_HIGHLIGHT displays help
4068 text in the first field of the status bar.
4070 @beginEventTable{wxMenuEvent}
4071 @event{EVT_MENU_OPEN(func)}
4072 A menu is about to be opened. On Windows, this is only sent once for each
4073 navigation of the menubar (up until all menus have closed).
4074 @event{EVT_MENU_CLOSE(func)}
4075 A menu has been just closed.
4076 @event{EVT_MENU_HIGHLIGHT(id, func)}
4077 The menu item with the specified id has been highlighted: used to show
4078 help prompts in the status bar by wxFrame
4079 @event{EVT_MENU_HIGHLIGHT_ALL(func)}
4080 A menu item has been highlighted, i.e. the currently selected menu item has changed.
4086 @see wxCommandEvent, @ref overview_events
4088 class wxMenuEvent
: public wxEvent
4094 wxMenuEvent(wxEventType type
= wxEVT_NULL
, int id
= 0, wxMenu
* menu
= NULL
);
4097 Returns the menu which is being opened or closed.
4099 This method can only be used with the @c OPEN and @c CLOSE events.
4101 The returned value is never @NULL in the ports implementing this
4102 function, which currently includes all the major ones.
4104 wxMenu
* GetMenu() const;
4107 Returns the menu identifier associated with the event.
4108 This method should be only used with the @c HIGHLIGHT events.
4110 int GetMenuId() const;
4113 Returns @true if the menu which is being opened or closed is a popup menu,
4114 @false if it is a normal one.
4116 This method should only be used with the @c OPEN and @c CLOSE events.
4118 bool IsPopup() const;
4124 An event being sent when the window is shown or hidden.
4125 The event is triggered by calls to wxWindow::Show(), and any user
4126 action showing a previously hidden window or vice versa (if allowed by
4127 the current platform and/or window manager).
4128 Notice that the event is not triggered when the application is iconized
4129 (minimized) or restored under wxMSW.
4131 @onlyfor{wxmsw,wxgtk,wxos2}
4133 @beginEventTable{wxShowEvent}
4134 @event{EVT_SHOW(func)}
4135 Process a @c wxEVT_SHOW event.
4141 @see @ref overview_events, wxWindow::Show,
4145 class wxShowEvent
: public wxEvent
4151 wxShowEvent(int winid
= 0, bool show
= false);
4154 Set whether the windows was shown or hidden.
4156 void SetShow(bool show
);
4159 Return @true if the window has been shown, @false if it has been
4162 bool IsShown() const;
4165 @deprecated This function is deprecated in favour of IsShown().
4167 bool GetShow() const;
4173 @class wxIconizeEvent
4175 An event being sent when the frame is iconized (minimized) or restored.
4177 Currently only wxMSW and wxGTK generate such events.
4179 @onlyfor{wxmsw,wxgtk}
4181 @beginEventTable{wxIconizeEvent}
4182 @event{EVT_ICONIZE(func)}
4183 Process a @c wxEVT_ICONIZE event.
4189 @see @ref overview_events, wxTopLevelWindow::Iconize,
4190 wxTopLevelWindow::IsIconized
4192 class wxIconizeEvent
: public wxEvent
4198 wxIconizeEvent(int id
= 0, bool iconized
= true);
4201 Returns @true if the frame has been iconized, @false if it has been
4204 bool IsIconized() const;
4207 @deprecated This function is deprecated in favour of IsIconized().
4209 bool Iconized() const;
4217 A move event holds information about wxTopLevelWindow move change events.
4219 These events are currently only generated by wxMSW port.
4221 @beginEventTable{wxMoveEvent}
4222 @event{EVT_MOVE(func)}
4223 Process a @c wxEVT_MOVE event, which is generated when a window is moved.
4224 @event{EVT_MOVE_START(func)}
4225 Process a @c wxEVT_MOVE_START event, which is generated when the user starts
4226 to move or size a window. wxMSW only.
4227 @event{EVT_MOVING(func)}
4228 Process a @c wxEVT_MOVING event, which is generated while the user is
4229 moving the window. wxMSW only.
4230 @event{EVT_MOVE_END(func)}
4231 Process a @c wxEVT_MOVE_END event, which is generated when the user stops
4232 moving or sizing a window. wxMSW only.
4238 @see wxPoint, @ref overview_events
4240 class wxMoveEvent
: public wxEvent
4246 wxMoveEvent(const wxPoint
& pt
, int id
= 0);
4249 Returns the position of the window generating the move change event.
4251 wxPoint
GetPosition() const;
4253 wxRect
GetRect() const;
4254 void SetRect(const wxRect
& rect
);
4255 void SetPosition(const wxPoint
& pos
);
4262 A size event holds information about size change events of wxWindow.
4264 The EVT_SIZE handler function will be called when the window has been resized.
4266 You may wish to use this for frames to resize their child windows as appropriate.
4268 Note that the size passed is of the whole window: call wxWindow::GetClientSize()
4269 for the area which may be used by the application.
4271 When a window is resized, usually only a small part of the window is damaged
4272 and you may only need to repaint that area. However, if your drawing depends on the
4273 size of the window, you may need to clear the DC explicitly and repaint the whole window.
4274 In which case, you may need to call wxWindow::Refresh to invalidate the entire window.
4276 @b Important : Sizers ( see @ref overview_sizer ) rely on size events to function
4277 correctly. Therefore, in a sizer-based layout, do not forget to call Skip on all
4278 size events you catch (and don't catch size events at all when you don't need to).
4280 @beginEventTable{wxSizeEvent}
4281 @event{EVT_SIZE(func)}
4282 Process a @c wxEVT_SIZE event.
4288 @see wxSize, @ref overview_events
4290 class wxSizeEvent
: public wxEvent
4296 wxSizeEvent(const wxSize
& sz
, int id
= 0);
4299 Returns the entire size of the window generating the size change event.
4301 This is the new total size of the window, i.e. the same size as would
4302 be returned by wxWindow::GetSize() if it were called now. Use
4303 wxWindow::GetClientSize() if you catch this event in a top level window
4304 such as wxFrame to find the size available for the window contents.
4306 wxSize
GetSize() const;
4307 void SetSize(wxSize size
);
4309 wxRect
GetRect() const;
4310 void SetRect(wxRect rect
);
4316 @class wxSetCursorEvent
4318 A wxSetCursorEvent is generated from wxWindow when the mouse cursor is about
4319 to be set as a result of mouse motion.
4321 This event gives the application the chance to perform specific mouse cursor
4322 processing based on the current position of the mouse within the window.
4323 Use wxSetCursorEvent::SetCursor to specify the cursor you want to be displayed.
4325 @beginEventTable{wxSetCursorEvent}
4326 @event{EVT_SET_CURSOR(func)}
4327 Process a @c wxEVT_SET_CURSOR event.
4333 @see ::wxSetCursor, wxWindow::SetCursor
4335 class wxSetCursorEvent
: public wxEvent
4339 Constructor, used by the library itself internally to initialize the event
4342 wxSetCursorEvent(wxCoord x
= 0, wxCoord y
= 0);
4345 Returns a reference to the cursor specified by this event.
4347 const wxCursor
& GetCursor() const;
4350 Returns the X coordinate of the mouse in client coordinates.
4352 wxCoord
GetX() const;
4355 Returns the Y coordinate of the mouse in client coordinates.
4357 wxCoord
GetY() const;
4360 Returns @true if the cursor specified by this event is a valid cursor.
4362 @remarks You cannot specify wxNullCursor with this event, as it is not
4363 considered a valid cursor.
4365 bool HasCursor() const;
4368 Sets the cursor associated with this event.
4370 void SetCursor(const wxCursor
& cursor
);
4375 // ============================================================================
4376 // Global functions/macros
4377 // ============================================================================
4379 /** @addtogroup group_funcmacro_events */
4385 A value uniquely identifying the type of the event.
4387 The values of this type should only be created using wxNewEventType().
4389 See the macro DEFINE_EVENT_TYPE() for more info.
4391 @see @ref overview_events
4393 typedef int wxEventType
;
4396 A special event type usually used to indicate that some wxEvent has yet
4399 wxEventType wxEVT_NULL
;
4401 wxEventType wxEVT_ANY
;
4404 Generates a new unique event type.
4406 Usually this function is only used by wxDEFINE_EVENT() and not called
4409 wxEventType
wxNewEventType();
4412 Define a new event type associated with the specified event class.
4414 This macro defines a new unique event type @a name associated with the
4419 wxDEFINE_EVENT(MY_COMMAND_EVENT, wxCommandEvent);
4421 class MyCustomEvent : public wxEvent { ... };
4422 wxDEFINE_EVENT(MY_CUSTOM_EVENT, MyCustomEvent);
4425 @see wxDECLARE_EVENT(), @ref overview_events_custom
4427 #define wxDEFINE_EVENT(name, cls) \
4428 const wxEventTypeTag< cls > name(wxNewEventType())
4431 Declares a custom event type.
4433 This macro declares a variable called @a name which must be defined
4434 elsewhere using wxDEFINE_EVENT().
4436 The class @a cls must be the wxEvent-derived class associated with the
4437 events of this type and its full declaration must be visible from the point
4438 of use of this macro.
4442 wxDECLARE_EVENT(MY_COMMAND_EVENT, wxCommandEvent);
4444 class MyCustomEvent : public wxEvent { ... };
4445 wxDECLARE_EVENT(MY_CUSTOM_EVENT, MyCustomEvent);
4448 #define wxDECLARE_EVENT(name, cls) \
4449 wxDECLARE_EXPORTED_EVENT(wxEMPTY_PARAMETER_VALUE, name, cls)
4452 Variant of wxDECLARE_EVENT() used for event types defined inside a shared
4455 This is mostly used by wxWidgets internally, e.g.
4457 wxDECLARE_EXPORTED_EVENT(WXDLLIMPEXP_CORE, wxEVT_BUTTON, wxCommandEvent)
4460 #define wxDECLARE_EXPORTED_EVENT( expdecl, name, cls ) \
4461 extern const expdecl wxEventTypeTag< cls > name;
4464 Helper macro for definition of custom event table macros.
4466 This macro must only be used if wxEVENTS_COMPATIBILITY_2_8 is 1, otherwise
4467 it is better and more clear to just use the address of the function
4468 directly as this is all this macro does in this case. However it needs to
4469 explicitly cast @a func to @a functype, which is the type of wxEvtHandler
4470 member function taking the custom event argument when
4471 wxEVENTS_COMPATIBILITY_2_8 is 0.
4473 See wx__DECLARE_EVT0 for an example of use.
4475 @see @ref overview_events_custom_ownclass
4477 #define wxEVENT_HANDLER_CAST(functype, func) (&func)
4480 This macro is used to define event table macros for handling custom
4485 class MyEvent : public wxEvent { ... };
4487 // note that this is not necessary unless using old compilers: for the
4488 // reasonably new ones just use &func instead of MyEventHandler(func)
4489 typedef void (wxEvtHandler::*MyEventFunction)(MyEvent&);
4490 #define MyEventHandler(func) wxEVENT_HANDLER_CAST(MyEventFunction, func)
4492 wxDEFINE_EVENT(MY_EVENT_TYPE, MyEvent);
4494 #define EVT_MY(id, func) \
4495 wx__DECLARE_EVT1(MY_EVENT_TYPE, id, MyEventHandler(func))
4499 wxBEGIN_EVENT_TABLE(MyFrame, wxFrame)
4500 EVT_MY(wxID_ANY, MyFrame::OnMyEvent)
4505 The event type to handle.
4507 The identifier of events to handle.
4509 The event handler method.
4511 #define wx__DECLARE_EVT1(evt, id, fn) \
4512 wx__DECLARE_EVT2(evt, id, wxID_ANY, fn)
4515 Generalized version of the wx__DECLARE_EVT1() macro taking a range of
4516 IDs instead of a single one.
4517 Argument @a id1 is the first identifier of the range, @a id2 is the
4518 second identifier of the range.
4520 #define wx__DECLARE_EVT2(evt, id1, id2, fn) \
4521 DECLARE_EVENT_TABLE_ENTRY(evt, id1, id2, fn, NULL),
4524 Simplified version of the wx__DECLARE_EVT1() macro, to be used when the
4525 event type must be handled regardless of the ID associated with the
4526 specific event instances.
4528 #define wx__DECLARE_EVT0(evt, fn) \
4529 wx__DECLARE_EVT1(evt, wxID_ANY, fn)
4532 Use this macro inside a class declaration to declare a @e static event table
4535 In the implementation file you'll need to use the wxBEGIN_EVENT_TABLE()
4536 and the wxEND_EVENT_TABLE() macros, plus some additional @c EVT_xxx macro
4539 Note that this macro requires a final semicolon.
4541 @see @ref overview_events_eventtables
4543 #define wxDECLARE_EVENT_TABLE()
4546 Use this macro in a source file to start listing @e static event handlers
4547 for a specific class.
4549 Use wxEND_EVENT_TABLE() to terminate the event-declaration block.
4551 @see @ref overview_events_eventtables
4553 #define wxBEGIN_EVENT_TABLE(theClass, baseClass)
4556 Use this macro in a source file to end listing @e static event handlers
4557 for a specific class.
4559 Use wxBEGIN_EVENT_TABLE() to start the event-declaration block.
4561 @see @ref overview_events_eventtables
4563 #define wxEND_EVENT_TABLE()
4566 In a GUI application, this function posts @a event to the specified @e dest
4567 object using wxEvtHandler::AddPendingEvent().
4569 Otherwise, it dispatches @a event immediately using
4570 wxEvtHandler::ProcessEvent(). See the respective documentation for details
4571 (and caveats). Because of limitation of wxEvtHandler::AddPendingEvent()
4572 this function is not thread-safe for event objects having wxString fields,
4573 use wxQueueEvent() instead.
4577 void wxPostEvent(wxEvtHandler
* dest
, const wxEvent
& event
);
4580 Queue an event for processing on the given object.
4582 This is a wrapper around wxEvtHandler::QueueEvent(), see its documentation
4588 The object to queue the event on, can't be @c NULL.
4590 The heap-allocated and non-@c NULL event to queue, the function takes
4593 void wxQueueEvent(wxEvtHandler
* dest
, wxEvent
*event
);
4595 #endif // wxUSE_BASE
4599 wxEventType wxEVT_BUTTON
;
4600 wxEventType wxEVT_CHECKBOX
;
4601 wxEventType wxEVT_CHOICE
;
4602 wxEventType wxEVT_LISTBOX
;
4603 wxEventType wxEVT_LISTBOX_DCLICK
;
4604 wxEventType wxEVT_CHECKLISTBOX
;
4605 wxEventType wxEVT_MENU
;
4606 wxEventType wxEVT_SLIDER
;
4607 wxEventType wxEVT_RADIOBOX
;
4608 wxEventType wxEVT_RADIOBUTTON
;
4609 wxEventType wxEVT_SCROLLBAR
;
4610 wxEventType wxEVT_VLBOX
;
4611 wxEventType wxEVT_COMBOBOX
;
4612 wxEventType wxEVT_TOOL_RCLICKED
;
4613 wxEventType wxEVT_TOOL_DROPDOWN
;
4614 wxEventType wxEVT_TOOL_ENTER
;
4615 wxEventType wxEVT_COMBOBOX_DROPDOWN
;
4616 wxEventType wxEVT_COMBOBOX_CLOSEUP
;
4617 wxEventType wxEVT_THREAD
;
4618 wxEventType wxEVT_LEFT_DOWN
;
4619 wxEventType wxEVT_LEFT_UP
;
4620 wxEventType wxEVT_MIDDLE_DOWN
;
4621 wxEventType wxEVT_MIDDLE_UP
;
4622 wxEventType wxEVT_RIGHT_DOWN
;
4623 wxEventType wxEVT_RIGHT_UP
;
4624 wxEventType wxEVT_MOTION
;
4625 wxEventType wxEVT_ENTER_WINDOW
;
4626 wxEventType wxEVT_LEAVE_WINDOW
;
4627 wxEventType wxEVT_LEFT_DCLICK
;
4628 wxEventType wxEVT_MIDDLE_DCLICK
;
4629 wxEventType wxEVT_RIGHT_DCLICK
;
4630 wxEventType wxEVT_SET_FOCUS
;
4631 wxEventType wxEVT_KILL_FOCUS
;
4632 wxEventType wxEVT_CHILD_FOCUS
;
4633 wxEventType wxEVT_MOUSEWHEEL
;
4634 wxEventType wxEVT_AUX1_DOWN
;
4635 wxEventType wxEVT_AUX1_UP
;
4636 wxEventType wxEVT_AUX1_DCLICK
;
4637 wxEventType wxEVT_AUX2_DOWN
;
4638 wxEventType wxEVT_AUX2_UP
;
4639 wxEventType wxEVT_AUX2_DCLICK
;
4640 wxEventType wxEVT_CHAR
;
4641 wxEventType wxEVT_CHAR_HOOK
;
4642 wxEventType wxEVT_NAVIGATION_KEY
;
4643 wxEventType wxEVT_KEY_DOWN
;
4644 wxEventType wxEVT_KEY_UP
;
4645 wxEventType wxEVT_HOTKEY
;
4646 wxEventType wxEVT_SET_CURSOR
;
4647 wxEventType wxEVT_SCROLL_TOP
;
4648 wxEventType wxEVT_SCROLL_BOTTOM
;
4649 wxEventType wxEVT_SCROLL_LINEUP
;
4650 wxEventType wxEVT_SCROLL_LINEDOWN
;
4651 wxEventType wxEVT_SCROLL_PAGEUP
;
4652 wxEventType wxEVT_SCROLL_PAGEDOWN
;
4653 wxEventType wxEVT_SCROLL_THUMBTRACK
;
4654 wxEventType wxEVT_SCROLL_THUMBRELEASE
;
4655 wxEventType wxEVT_SCROLL_CHANGED
;
4656 wxEventType wxEVT_SPIN_UP
;
4657 wxEventType wxEVT_SPIN_DOWN
;
4658 wxEventType wxEVT_SPIN
;
4659 wxEventType wxEVT_SCROLLWIN_TOP
;
4660 wxEventType wxEVT_SCROLLWIN_BOTTOM
;
4661 wxEventType wxEVT_SCROLLWIN_LINEUP
;
4662 wxEventType wxEVT_SCROLLWIN_LINEDOWN
;
4663 wxEventType wxEVT_SCROLLWIN_PAGEUP
;
4664 wxEventType wxEVT_SCROLLWIN_PAGEDOWN
;
4665 wxEventType wxEVT_SCROLLWIN_THUMBTRACK
;
4666 wxEventType wxEVT_SCROLLWIN_THUMBRELEASE
;
4667 wxEventType wxEVT_SIZE
;
4668 wxEventType wxEVT_MOVE
;
4669 wxEventType wxEVT_CLOSE_WINDOW
;
4670 wxEventType wxEVT_END_SESSION
;
4671 wxEventType wxEVT_QUERY_END_SESSION
;
4672 wxEventType wxEVT_ACTIVATE_APP
;
4673 wxEventType wxEVT_ACTIVATE
;
4674 wxEventType wxEVT_CREATE
;
4675 wxEventType wxEVT_DESTROY
;
4676 wxEventType wxEVT_SHOW
;
4677 wxEventType wxEVT_ICONIZE
;
4678 wxEventType wxEVT_MAXIMIZE
;
4679 wxEventType wxEVT_MOUSE_CAPTURE_CHANGED
;
4680 wxEventType wxEVT_MOUSE_CAPTURE_LOST
;
4681 wxEventType wxEVT_PAINT
;
4682 wxEventType wxEVT_ERASE_BACKGROUND
;
4683 wxEventType wxEVT_NC_PAINT
;
4684 wxEventType wxEVT_MENU_OPEN
;
4685 wxEventType wxEVT_MENU_CLOSE
;
4686 wxEventType wxEVT_MENU_HIGHLIGHT
;
4687 wxEventType wxEVT_CONTEXT_MENU
;
4688 wxEventType wxEVT_SYS_COLOUR_CHANGED
;
4689 wxEventType wxEVT_DISPLAY_CHANGED
;
4690 wxEventType wxEVT_QUERY_NEW_PALETTE
;
4691 wxEventType wxEVT_PALETTE_CHANGED
;
4692 wxEventType wxEVT_JOY_BUTTON_DOWN
;
4693 wxEventType wxEVT_JOY_BUTTON_UP
;
4694 wxEventType wxEVT_JOY_MOVE
;
4695 wxEventType wxEVT_JOY_ZMOVE
;
4696 wxEventType wxEVT_DROP_FILES
;
4697 wxEventType wxEVT_INIT_DIALOG
;
4698 wxEventType wxEVT_IDLE
;
4699 wxEventType wxEVT_UPDATE_UI
;
4700 wxEventType wxEVT_SIZING
;
4701 wxEventType wxEVT_MOVING
;
4702 wxEventType wxEVT_MOVE_START
;
4703 wxEventType wxEVT_MOVE_END
;
4704 wxEventType wxEVT_HIBERNATE
;
4705 wxEventType wxEVT_TEXT_COPY
;
4706 wxEventType wxEVT_TEXT_CUT
;
4707 wxEventType wxEVT_TEXT_PASTE
;
4708 wxEventType wxEVT_COMMAND_LEFT_CLICK
;
4709 wxEventType wxEVT_COMMAND_LEFT_DCLICK
;
4710 wxEventType wxEVT_COMMAND_RIGHT_CLICK
;
4711 wxEventType wxEVT_COMMAND_RIGHT_DCLICK
;
4712 wxEventType wxEVT_COMMAND_SET_FOCUS
;
4713 wxEventType wxEVT_COMMAND_KILL_FOCUS
;
4714 wxEventType wxEVT_COMMAND_ENTER
;
4715 wxEventType wxEVT_HELP
;
4716 wxEventType wxEVT_DETAILED_HELP
;
4717 wxEventType wxEVT_TOOL
;
4718 wxEventType wxEVT_WINDOW_MODAL_DIALOG_CLOSED
;