1 /////////////////////////////////////////////////////////////////////////////
3 // Purpose: interface of wxEvtHandler, wxEventBlocker and many
4 // wxEvent-derived classes
5 // Author: wxWidgets team
7 // Licence: wxWindows licence
8 /////////////////////////////////////////////////////////////////////////////
11 The predefined constants for the number of times we propagate event
12 upwards window child-parent chain.
14 enum wxEventPropagation
16 /// don't propagate it at all
17 wxEVENT_PROPAGATE_NONE
= 0,
19 /// propagate it until it is processed
20 wxEVENT_PROPAGATE_MAX
= INT_MAX
24 The different categories for a wxEvent; see wxEvent::GetEventCategory.
26 @note They are used as OR-combinable flags by wxEventLoopBase::YieldFor.
31 This is the category for those events which are generated to update
32 the appearance of the GUI but which (usually) do not comport data
33 processing, i.e. which do not provide input or output data
34 (e.g. size events, scroll events, etc).
35 They are events NOT directly generated by the user's input devices.
37 wxEVT_CATEGORY_UI
= 1,
40 This category groups those events which are generated directly from the
41 user through input devices like mouse and keyboard and usually result in
42 data to be processed from the application
43 (e.g. mouse clicks, key presses, etc).
45 wxEVT_CATEGORY_USER_INPUT
= 2,
47 /// This category is for wxSocketEvent
48 wxEVT_CATEGORY_SOCKET
= 4,
50 /// This category is for wxTimerEvent
51 wxEVT_CATEGORY_TIMER
= 8,
54 This category is for any event used to send notifications from the
55 secondary threads to the main one or in general for notifications among
56 different threads (which may or may not be user-generated).
57 See e.g. wxThreadEvent.
59 wxEVT_CATEGORY_THREAD
= 16,
62 This mask is used in wxEventLoopBase::YieldFor to specify that all event
63 categories should be processed.
66 wxEVT_CATEGORY_UI
|wxEVT_CATEGORY_USER_INPUT
|wxEVT_CATEGORY_SOCKET
| \
67 wxEVT_CATEGORY_TIMER
|wxEVT_CATEGORY_THREAD
73 An event is a structure holding information about an event passed to a
74 callback or member function.
76 wxEvent used to be a multipurpose event object, and is an abstract base class
77 for other event classes (see below).
79 For more information about events, see the @ref overview_events overview.
82 In wxPerl custom event classes should be derived from
83 @c Wx::PlEvent and @c Wx::PlCommandEvent.
89 @see wxCommandEvent, wxMouseEvent
91 class wxEvent
: public wxObject
97 Notice that events are usually created by wxWidgets itself and creating
98 e.g. a wxPaintEvent in your code and sending it to e.g. a wxTextCtrl
99 will not usually affect it at all as native controls have no specific
100 knowledge about wxWidgets events. However you may construct objects of
101 specific types and pass them to wxEvtHandler::ProcessEvent() if you
102 want to create your own custom control and want to process its events
103 in the same manner as the standard ones.
105 Also please notice that the order of parameters in this constructor is
106 different from almost all the derived classes which specify the event
107 type as the first argument.
110 The identifier of the object (window, timer, ...) which generated
113 The unique type of event, e.g. wxEVT_PAINT, wxEVT_SIZE or
114 wxEVT_COMMAND_BUTTON_CLICKED.
116 wxEvent(int id
= 0, wxEventType eventType
= wxEVT_NULL
);
119 Returns a copy of the event.
121 Any event that is posted to the wxWidgets event system for later action
122 (via wxEvtHandler::AddPendingEvent, wxEvtHandler::QueueEvent or wxPostEvent())
123 must implement this method.
125 All wxWidgets events fully implement this method, but any derived events
126 implemented by the user should also implement this method just in case they
127 (or some event derived from them) are ever posted.
129 All wxWidgets events implement a copy constructor, so the easiest way of
130 implementing the Clone function is to implement a copy constructor for
131 a new event (call it MyEvent) and then define the Clone function like this:
134 wxEvent *Clone() const { return new MyEvent(*this); }
137 virtual wxEvent
* Clone() const = 0;
140 Returns the object (usually a window) associated with the event, if any.
142 wxObject
* GetEventObject() const;
145 Returns the identifier of the given event type, such as @c wxEVT_COMMAND_BUTTON_CLICKED.
147 wxEventType
GetEventType() const;
150 Returns a generic category for this event.
151 wxEvent implementation returns @c wxEVT_CATEGORY_UI by default.
153 This function is used to selectively process events in wxEventLoopBase::YieldFor.
155 virtual wxEventCategory
GetEventCategory() const;
158 Returns the identifier associated with this event, such as a button command id.
163 Returns @true if the event handler should be skipped, @false otherwise.
165 bool GetSkipped() const;
168 Gets the timestamp for the event. The timestamp is the time in milliseconds
169 since some fixed moment (not necessarily the standard Unix Epoch, so only
170 differences between the timestamps and not their absolute values usually make sense).
173 wxWidgets returns a non-NULL timestamp only for mouse and key events
174 (see wxMouseEvent and wxKeyEvent).
176 long GetTimestamp() const;
179 Returns @true if the event is or is derived from wxCommandEvent else it returns @false.
181 @note exists only for optimization purposes.
183 bool IsCommandEvent() const;
186 Sets the propagation level to the given value (for example returned from an
187 earlier call to wxEvent::StopPropagation).
189 void ResumePropagation(int propagationLevel
);
192 Sets the originating object.
194 void SetEventObject(wxObject
* object
);
199 void SetEventType(wxEventType type
);
202 Sets the identifier associated with this event, such as a button command id.
207 Sets the timestamp for the event.
209 void SetTimestamp(long timeStamp
= 0);
212 Test if this event should be propagated or not, i.e. if the propagation level
213 is currently greater than 0.
215 bool ShouldPropagate() const;
218 This method can be used inside an event handler to control whether further
219 event handlers bound to this event will be called after the current one returns.
221 Without Skip() (or equivalently if Skip(@false) is used), the event will not
222 be processed any more. If Skip(@true) is called, the event processing system
223 continues searching for a further handler function for this event, even though
224 it has been processed already in the current handler.
226 In general, it is recommended to skip all non-command events to allow the
227 default handling to take place. The command events are, however, normally not
228 skipped as usually a single command such as a button click or menu item
229 selection must only be processed by one handler.
231 void Skip(bool skip
= true);
234 Stop the event from propagating to its parent window.
236 Returns the old propagation level value which may be later passed to
237 ResumePropagation() to allow propagating the event again.
239 int StopPropagation();
243 Indicates how many levels the event can propagate.
245 This member is protected and should typically only be set in the constructors
246 of the derived classes. It may be temporarily changed by StopPropagation()
247 and ResumePropagation() and tested with ShouldPropagate().
249 The initial value is set to either @c wxEVENT_PROPAGATE_NONE (by default)
250 meaning that the event shouldn't be propagated at all or to
251 @c wxEVENT_PROPAGATE_MAX (for command events) meaning that it should be
252 propagated as much as necessary.
254 Any positive number means that the event should be propagated but no more than
255 the given number of times. E.g. the propagation level may be set to 1 to
256 propagate the event to its parent only, but not to its grandparent.
258 int m_propagationLevel
;
262 @class wxEventBlocker
264 This class is a special event handler which allows to discard
265 any event (or a set of event types) directed to a specific window.
270 void MyWindow::DoSomething()
273 // block all events directed to this window while
274 // we do the 1000 FunctionWhichSendsEvents() calls
275 wxEventBlocker blocker(this);
277 for ( int i = 0; i 1000; i++ )
278 FunctionWhichSendsEvents(i);
280 } // ~wxEventBlocker called, old event handler is restored
282 // the event generated by this call will be processed:
283 FunctionWhichSendsEvents(0)
290 @see @ref overview_events_processing, wxEvtHandler
292 class wxEventBlocker
: public wxEvtHandler
296 Constructs the blocker for the given window and for the given event type.
298 If @a type is @c wxEVT_ANY, then all events for that window are blocked.
299 You can call Block() after creation to add other event types to the list
302 Note that the @a win window @b must remain alive until the
303 wxEventBlocker object destruction.
305 wxEventBlocker(wxWindow
* win
, wxEventType type
= -1);
308 Destructor. The blocker will remove itself from the chain of event handlers for
309 the window provided in the constructor, thus restoring normal processing of events.
311 virtual ~wxEventBlocker();
314 Adds to the list of event types which should be blocked the given @a eventType.
316 void Block(wxEventType eventType
);
324 A class that can handle events from the windowing system.
325 wxWindow is (and therefore all window classes are) derived from this class.
327 When events are received, wxEvtHandler invokes the method listed in the
328 event table using itself as the object. When using multiple inheritance
329 <b>it is imperative that the wxEvtHandler(-derived) class is the first
330 class inherited</b> such that the @c this pointer for the overall object
331 will be identical to the @c this pointer of the wxEvtHandler portion.
336 @see @ref overview_events_processing, wxEventBlocker, wxEventLoopBase
338 class wxEvtHandler
: public wxObject
, public wxTrackable
349 If the handler is part of a chain, the destructor will unlink itself
352 virtual ~wxEvtHandler();
356 @name Event queuing and processing
361 Queue event for a later processing.
363 This method is similar to ProcessEvent() but while the latter is
364 synchronous, i.e. the event is processed immediately, before the
365 function returns, this one is asynchronous and returns immediately
366 while the event will be processed at some later time (usually during
367 the next event loop iteration).
369 Another important difference is that this method takes ownership of the
370 @a event parameter, i.e. it will delete it itself. This implies that
371 the event should be allocated on the heap and that the pointer can't be
372 used any more after the function returns (as it can be deleted at any
375 QueueEvent() can be used for inter-thread communication from the worker
376 threads to the main thread, it is safe in the sense that it uses
377 locking internally and avoids the problem mentioned in AddPendingEvent()
378 documentation by ensuring that the @a event object is not used by the
379 calling thread any more. Care should still be taken to avoid that some
380 fields of this object are used by it, notably any wxString members of
381 the event object must not be shallow copies of another wxString object
382 as this would result in them still using the same string buffer behind
383 the scenes. For example:
385 void FunctionInAWorkerThread(const wxString& str)
387 wxCommandEvent* evt = new wxCommandEvent;
389 // NOT evt->SetString(str) as this would be a shallow copy
390 evt->SetString(str.c_str()); // make a deep copy
392 wxTheApp->QueueEvent( evt );
396 Note that you can use wxThreadEvent instead of wxCommandEvent
397 to avoid this problem:
399 void FunctionInAWorkerThread(const wxString& str)
404 // wxThreadEvent::Clone() makes sure that the internal wxString
405 // member is not shared by other wxString instances:
406 wxTheApp->QueueEvent( evt.Clone() );
410 Finally notice that this method automatically wakes up the event loop
411 if it is currently idle by calling ::wxWakeUpIdle() so there is no need
412 to do it manually when using it.
417 A heap-allocated event to be queued, QueueEvent() takes ownership
418 of it. This parameter shouldn't be @c NULL.
420 virtual void QueueEvent(wxEvent
*event
);
423 Post an event to be processed later.
425 This function is similar to QueueEvent() but can't be used to post
426 events from worker threads for the event objects with wxString fields
427 (i.e. in practice most of them) because of an unsafe use of the same
428 wxString object which happens because the wxString field in the
429 original @a event object and its copy made internally by this function
430 share the same string buffer internally. Use QueueEvent() to avoid
433 A copy of @a event is made by the function, so the original can be deleted
434 as soon as function returns (it is common that the original is created
435 on the stack). This requires that the wxEvent::Clone() method be
436 implemented by event so that it can be duplicated and stored until it
440 Event to add to the pending events queue.
442 virtual void AddPendingEvent(const wxEvent
& event
);
445 Processes an event, searching event tables and calling zero or more suitable
446 event handler function(s).
448 Normally, your application would not call this function: it is called in the
449 wxWidgets implementation to dispatch incoming user interface events to the
450 framework (and application).
452 However, you might need to call it if implementing new functionality
453 (such as a new control) where you define new event types, as opposed to
454 allowing the user to override virtual functions.
456 Notice that you don't usually need to override ProcessEvent() to
457 customize the event handling, overriding the specially provided
458 TryBefore() and TryAfter() functions is usually enough. For example,
459 wxMDIParentFrame may override TryBefore() to ensure that the menu
460 events are processed in the active child frame before being processed
461 in the parent frame itself.
463 The normal order of event table searching is as follows:
464 -# wxApp::FilterEvent() is called. If it returns anything but @c -1
465 (default) the processing stops here.
466 -# TryBefore() is called (this is where wxValidator are taken into
467 account for wxWindow objects). If this returns @true, the function exits.
468 -# If the object is disabled (via a call to wxEvtHandler::SetEvtHandlerEnabled)
469 the function skips to step (7).
470 -# Dynamic event table of the handlers bound using Bind<>() is
471 searched. If a handler is found, it is executed and the function
472 returns @true unless the handler used wxEvent::Skip() to indicate
473 that it didn't handle the event in which case the search continues.
474 -# Static events table of the handlers bound using event table
475 macros is searched for this event handler. If this fails, the base
476 class event table table is tried, and so on until no more tables
477 exist or an appropriate function was found. If a handler is found,
478 the same logic as in the previous step applies.
479 -# The search is applied down the entire chain of event handlers (usually the
480 chain has a length of one). This chain can be formed using wxEvtHandler::SetNextHandler():
481 @image html overview_events_chain.png
482 (referring to the image, if @c A->ProcessEvent is called and it doesn't handle
483 the event, @c B->ProcessEvent will be called and so on...).
484 Note that in the case of wxWindow you can build a stack of event handlers
485 (see wxWindow::PushEventHandler() for more info).
486 If any of the handlers of the chain return @true, the function exits.
487 -# TryAfter() is called: for the wxWindow object this may propagate the
488 event to the window parent (recursively). If the event is still not
489 processed, ProcessEvent() on wxTheApp object is called as the last
492 Notice that steps (2)-(6) are performed in ProcessEventLocally()
493 which is called by this function.
498 @true if a suitable event handler function was found and executed,
499 and the function did not call wxEvent::Skip.
501 @see SearchEventTable()
503 virtual bool ProcessEvent(wxEvent
& event
);
506 Try to process the event in this handler and all those chained to it.
508 As explained in ProcessEvent() documentation, the event handlers may be
509 chained in a doubly-linked list. This function tries to process the
510 event in this handler (including performing any pre-processing done in
511 TryBefore(), e.g. applying validators) and all those following it in
512 the chain until the event is processed or the chain is exhausted.
514 This function is called from ProcessEvent() and, in turn, calls
515 TryThis() for each handler in turn. It is not virtual and so cannot be
516 overridden but can, and should, be called to forward an event to
517 another handler instead of ProcessEvent() which would result in a
518 duplicate call to TryAfter(), e.g. resulting in all unprocessed events
519 being sent to the application object multiple times.
526 @true if this handler of one of those chained to it processed the
529 bool ProcessEventLocally(wxEvent
& event
);
532 Processes an event by calling ProcessEvent() and handles any exceptions
533 that occur in the process.
534 If an exception is thrown in event handler, wxApp::OnExceptionInMainLoop is called.
539 @return @true if the event was processed, @false if no handler was found
540 or an exception was thrown.
542 @see wxWindow::HandleWindowEvent
544 bool SafelyProcessEvent(wxEvent
& event
);
547 Processes the pending events previously queued using QueueEvent() or
548 AddPendingEvent(); you must call this function only if you are sure
549 there are pending events for this handler, otherwise a @c wxCHECK
552 The real processing still happens in ProcessEvent() which is called by this
555 Note that this function needs a valid application object (see
556 wxAppConsole::GetInstance()) because wxApp holds the list of the event
557 handlers with pending events and this function manipulates that list.
559 void ProcessPendingEvents();
562 Deletes all events queued on this event handler using QueueEvent() or
565 Use with care because the events which are deleted are (obviously) not
566 processed and this may have unwanted consequences (e.g. user actions events
569 void DeletePendingEvents();
572 Searches the event table, executing an event handler function if an appropriate
576 Event table to be searched.
578 Event to be matched against an event table entry.
580 @return @true if a suitable event handler function was found and
581 executed, and the function did not call wxEvent::Skip.
583 @remarks This function looks through the object's event table and tries
584 to find an entry that will match the event.
585 An entry will match if:
586 @li The event type matches, and
587 @li the identifier or identifier range matches, or the event table
588 entry's identifier is zero.
590 If a suitable function is called but calls wxEvent::Skip, this
591 function will fail, and searching will continue.
593 @todo this function in the header is listed as an "implementation only" function;
594 are we sure we want to document it?
598 virtual bool SearchEventTable(wxEventTable
& table
,
605 @name Connecting and disconnecting
610 Connects the given function dynamically with the event handler, id and
613 Notice that Bind() provides a more flexible and safer way to do the
614 same thing as Connect(), please use it in any new code -- while
615 Connect() is not formally deprecated due to its existing widespread
616 usage, it has no advantages compared to Bind().
618 This is an alternative to the use of static event tables. It is more
619 flexible as it allows to connect events generated by some object to an
620 event handler defined in a different object of a different class (which
621 is impossible to do directly with the event tables -- the events can be
622 only handled in another object if they are propagated upwards to it).
623 Do make sure to specify the correct @a eventSink when connecting to an
624 event of a different object.
626 See @ref overview_events_bind for more detailed explanation
627 of this function and the @ref page_samples_event sample for usage
630 This specific overload allows you to connect an event handler to a @e range
632 Do not confuse @e source IDs with event @e types: source IDs identify the
633 event generator objects (typically wxMenuItem or wxWindow objects) while the
634 event @e type identify which type of events should be handled by the
635 given @e function (an event generator object may generate many different
639 The first ID of the identifier range to be associated with the event
642 The last ID of the identifier range to be associated with the event
645 The event type to be associated with this event handler.
647 The event handler function. Note that this function should
648 be explicitly converted to the correct type which can be done using a macro
649 called @c wxFooEventHandler for the handler for any @c wxFooEvent.
651 Data to be associated with the event table entry.
653 Object whose member function should be called. It must be specified
654 when connecting an event generated by one object to a member
655 function of a different object. If it is omitted, @c this is used.
658 In wxPerl this function takes 4 arguments: @a id, @a lastid,
659 @a type, @a method; if @a method is undef, the handler is
665 void Connect(int id
, int lastId
, wxEventType eventType
,
666 wxObjectEventFunction function
,
667 wxObject
* userData
= NULL
,
668 wxEvtHandler
* eventSink
= NULL
);
671 See the Connect(int, int, wxEventType, wxObjectEventFunction, wxObject*, wxEvtHandler*)
672 overload for more info.
674 This overload can be used to attach an event handler to a single source ID:
678 frame->Connect( wxID_EXIT,
679 wxEVT_COMMAND_MENU_SELECTED,
680 wxCommandEventHandler(MyFrame::OnQuit) );
684 Not supported by wxPerl.
687 void Connect(int id
, wxEventType eventType
,
688 wxObjectEventFunction function
,
689 wxObject
* userData
= NULL
,
690 wxEvtHandler
* eventSink
= NULL
);
693 See the Connect(int, int, wxEventType, wxObjectEventFunction, wxObject*, wxEvtHandler*)
694 overload for more info.
696 This overload will connect the given event handler so that regardless of the
697 ID of the event source, the handler will be called.
700 Not supported by wxPerl.
703 void Connect(wxEventType eventType
,
704 wxObjectEventFunction function
,
705 wxObject
* userData
= NULL
,
706 wxEvtHandler
* eventSink
= NULL
);
709 Disconnects the given function dynamically from the event handler, using the
710 specified parameters as search criteria and returning @true if a matching
711 function has been found and removed.
713 This method can only disconnect functions which have been added using the
714 Connect() method. There is no way to disconnect functions connected using
715 the (static) event tables.
718 The event type associated with this event handler.
720 The event handler function.
722 Data associated with the event table entry.
724 Object whose member function should be called.
727 Not supported by wxPerl.
730 bool Disconnect(wxEventType eventType
,
731 wxObjectEventFunction function
,
732 wxObject
* userData
= NULL
,
733 wxEvtHandler
* eventSink
= NULL
);
736 See the Disconnect(wxEventType, wxObjectEventFunction, wxObject*, wxEvtHandler*)
737 overload for more info.
739 This overload takes the additional @a id parameter.
742 Not supported by wxPerl.
745 bool Disconnect(int id
= wxID_ANY
,
746 wxEventType eventType
= wxEVT_NULL
,
747 wxObjectEventFunction function
= NULL
,
748 wxObject
* userData
= NULL
,
749 wxEvtHandler
* eventSink
= NULL
);
752 See the Disconnect(wxEventType, wxObjectEventFunction, wxObject*, wxEvtHandler*)
753 overload for more info.
755 This overload takes an additional range of source IDs.
758 In wxPerl this function takes 3 arguments: @a id,
762 bool Disconnect(int id
, int lastId
,
763 wxEventType eventType
,
764 wxObjectEventFunction function
= NULL
,
765 wxObject
* userData
= NULL
,
766 wxEvtHandler
* eventSink
= NULL
);
771 @name Binding and Unbinding
776 Binds the given function, functor or method dynamically with the event.
778 This offers basically the same functionality as Connect(), but it is
779 more flexible as it also allows you to use ordinary functions and
780 arbitrary functors as event handlers. It is also less restrictive then
781 Connect() because you can use an arbitrary method as an event handler,
782 where as Connect() requires a wxEvtHandler derived handler.
784 See @ref overview_events_bind for more detailed explanation
785 of this function and the @ref page_samples_event sample for usage
789 The event type to be associated with this event handler.
791 The event handler functor. This can be an ordinary function but also
792 an arbitrary functor like boost::function<>.
794 The first ID of the identifier range to be associated with the event
797 The last ID of the identifier range to be associated with the event
800 Data to be associated with the event table entry.
802 @see @ref overview_cpp_rtti_disabled
806 template <typename EventTag
, typename Functor
>
807 void Bind(const EventTag
& eventType
,
810 int lastId
= wxID_ANY
,
811 wxObject
*userData
= NULL
);
814 See the Bind<>(const EventTag&, Functor, int, int, wxObject*) overload for
817 This overload will bind the given method as the event handler.
820 The event type to be associated with this event handler.
822 The event handler method. This can be an arbitrary method (doesn't need
823 to be from a wxEvtHandler derived class).
825 Object whose method should be called. It must always be specified
826 so it can be checked at compile time whether the given method is an
827 actual member of the given handler.
829 The first ID of the identifier range to be associated with the event
832 The last ID of the identifier range to be associated with the event
835 Data to be associated with the event table entry.
837 @see @ref overview_cpp_rtti_disabled
841 template <typename EventTag
, typename Class
, typename EventArg
, typename EventHandler
>
842 void Bind(const EventTag
&eventType
,
843 void (Class::*method
)(EventArg
&),
844 EventHandler
*handler
,
846 int lastId
= wxID_ANY
,
847 wxObject
*userData
= NULL
);
849 Unbinds the given function, functor or method dynamically from the
850 event handler, using the specified parameters as search criteria and
851 returning @true if a matching function has been found and removed.
853 This method can only unbind functions, functors or methods which have
854 been added using the Bind<>() method. There is no way to unbind
855 functions bound using the (static) event tables.
858 The event type associated with this event handler.
860 The event handler functor. This can be an ordinary function but also
861 an arbitrary functor like boost::function<>.
863 The first ID of the identifier range associated with the event
866 The last ID of the identifier range associated with the event
869 Data associated with the event table entry.
871 @see @ref overview_cpp_rtti_disabled
875 template <typename EventTag
, typename Functor
>
876 bool Unbind(const EventTag
& eventType
,
879 int lastId
= wxID_ANY
,
880 wxObject
*userData
= NULL
);
883 See the Unbind<>(const EventTag&, Functor, int, int, wxObject*)
884 overload for more info.
886 This overload unbinds the given method from the event..
889 The event type associated with this event handler.
891 The event handler method associated with this event.
893 Object whose method was called.
895 The first ID of the identifier range associated with the event
898 The last ID of the identifier range associated with the event
901 Data associated with the event table entry.
903 @see @ref overview_cpp_rtti_disabled
907 template <typename EventTag
, typename Class
, typename EventArg
, typename EventHandler
>
908 bool Unbind(const EventTag
&eventType
,
909 void (Class::*method
)(EventArg
&),
910 EventHandler
*handler
,
912 int lastId
= wxID_ANY
,
913 wxObject
*userData
= NULL
);
916 @name User-supplied data
921 Returns user-supplied client data.
923 @remarks Normally, any extra data the programmer wishes to associate with
924 the object should be made available by deriving a new class with
929 void* GetClientData() const;
932 Returns a pointer to the user-supplied client data object.
934 @see SetClientObject(), wxClientData
936 wxClientData
* GetClientObject() const;
939 Sets user-supplied client data.
942 Data to be associated with the event handler.
944 @remarks Normally, any extra data the programmer wishes to associate
945 with the object should be made available by deriving a new
946 class with new data members. You must not call this method
947 and SetClientObject on the same class - only one of them.
951 void SetClientData(void* data
);
954 Set the client data object. Any previous object will be deleted.
956 @see GetClientObject(), wxClientData
958 void SetClientObject(wxClientData
* data
);
964 @name Event handler chaining
966 wxEvtHandler can be arranged in a double-linked list of handlers
967 which is automatically iterated by ProcessEvent() if needed.
972 Returns @true if the event handler is enabled, @false otherwise.
974 @see SetEvtHandlerEnabled()
976 bool GetEvtHandlerEnabled() const;
979 Returns the pointer to the next handler in the chain.
981 @see SetNextHandler(), GetPreviousHandler(), SetPreviousHandler(),
982 wxWindow::PushEventHandler, wxWindow::PopEventHandler
984 wxEvtHandler
* GetNextHandler() const;
987 Returns the pointer to the previous handler in the chain.
989 @see SetPreviousHandler(), GetNextHandler(), SetNextHandler(),
990 wxWindow::PushEventHandler, wxWindow::PopEventHandler
992 wxEvtHandler
* GetPreviousHandler() const;
995 Enables or disables the event handler.
998 @true if the event handler is to be enabled, @false if it is to be disabled.
1000 @remarks You can use this function to avoid having to remove the event
1001 handler from the chain, for example when implementing a
1002 dialog editor and changing from edit to test mode.
1004 @see GetEvtHandlerEnabled()
1006 void SetEvtHandlerEnabled(bool enabled
);
1009 Sets the pointer to the next handler.
1012 See ProcessEvent() for more info about how the chains of event handlers
1013 are internally used.
1014 Also remember that wxEvtHandler uses double-linked lists and thus if you
1015 use this function, you should also call SetPreviousHandler() on the
1016 argument passed to this function:
1018 handlerA->SetNextHandler(handlerB);
1019 handlerB->SetPreviousHandler(handlerA);
1023 The event handler to be set as the next handler.
1026 @see @ref overview_events_processing
1028 virtual void SetNextHandler(wxEvtHandler
* handler
);
1031 Sets the pointer to the previous handler.
1032 All remarks about SetNextHandler() apply to this function as well.
1035 The event handler to be set as the previous handler.
1038 @see @ref overview_events_processing
1040 virtual void SetPreviousHandler(wxEvtHandler
* handler
);
1043 Unlinks this event handler from the chain it's part of (if any);
1044 then links the "previous" event handler to the "next" one
1045 (so that the chain won't be interrupted).
1047 E.g. if before calling Unlink() you have the following chain:
1048 @image html evthandler_unlink_before.png
1049 then after calling @c B->Unlink() you'll have:
1050 @image html evthandler_unlink_after.png
1057 Returns @true if the next and the previous handler pointers of this
1058 event handler instance are @NULL.
1062 @see SetPreviousHandler(), SetNextHandler()
1064 bool IsUnlinked() const;
1070 Method called by ProcessEvent() before examining this object event
1073 This method can be overridden to hook into the event processing logic
1074 as early as possible. You should usually call the base class version
1075 when overriding this method, even if wxEvtHandler itself does nothing
1076 here, some derived classes do use this method, e.g. wxWindow implements
1077 support for wxValidator in it.
1081 class MyClass : public BaseClass // inheriting from wxEvtHandler
1085 virtual bool TryBefore(wxEvent& event)
1087 if ( MyPreProcess(event) )
1090 return BaseClass::TryBefore(event);
1097 virtual bool TryBefore(wxEvent
& event
);
1100 Try to process the event in this event handler.
1102 This method is called from ProcessEventLocally() and thus, indirectly,
1103 from ProcessEvent(), please see the detailed description of the event
1104 processing logic there.
1106 It is currently @em not virtual and so may not be overridden.
1113 @true if this object itself defines a handler for this event and
1114 the handler didn't skip the event.
1116 bool TryThis(wxEvent
& event
);
1119 Method called by ProcessEvent() as last resort.
1121 This method can be overridden to implement post-processing for the
1122 events which were not processed anywhere else.
1124 The base class version handles forwarding the unprocessed events to
1125 wxApp at wxEvtHandler level and propagating them upwards the window
1126 child-parent chain at wxWindow level and so should usually be called
1127 when overriding this method:
1129 class MyClass : public BaseClass // inheriting from wxEvtHandler
1133 virtual bool TryAfter(wxEvent& event)
1135 if ( BaseClass::TryAfter(event) )
1138 return MyPostProcess(event);
1145 virtual bool TryAfter(wxEvent
& event
);
1150 Flags for categories of keys.
1152 These values are used by wxKeyEvent::IsKeyInCategory(). They may be
1153 combined via the bitwise operators |, &, and ~.
1157 enum wxKeyCategoryFlags
1159 /// arrow keys, on and off numeric keypads
1162 /// page up and page down keys, on and off numeric keypads
1163 WXK_CATEGORY_PAGING
,
1165 /// home and end keys, on and off numeric keypads
1168 /// tab key, on and off numeric keypads
1171 /// backspace and delete keys, on and off numeric keypads
1174 /// union of WXK_CATEGORY_ARROW, WXK_CATEGORY_PAGING, and WXK_CATEGORY_JUMP categories
1175 WXK_CATEGORY_NAVIGATION
1182 This event class contains information about key press and release events.
1184 The main information carried by this event is the key being pressed or
1185 released. It can be accessed using either GetKeyCode() function or
1186 GetUnicodeKey(). For the printable characters, the latter should be used as
1187 it works for any keys, including non-Latin-1 characters that can be entered
1188 when using national keyboard layouts. GetKeyCode() should be used to handle
1189 special characters (such as cursor arrows keys or @c HOME or @c INS and so
1190 on) which correspond to ::wxKeyCode enum elements above the @c WXK_START
1191 constant. While GetKeyCode() also returns the character code for Latin-1
1192 keys for compatibility, it doesn't work for Unicode characters in general
1193 and will return @c WXK_NONE for any non-Latin-1 ones. For this reason, it's
1194 recommended to always use GetUnicodeKey() and only fall back to GetKeyCode()
1195 if GetUnicodeKey() returned @c WXK_NONE meaning that the event corresponds
1196 to a non-printable special keys.
1198 While both of these functions can be used with the events of @c
1199 wxEVT_KEY_DOWN, @c wxEVT_KEY_UP and @c wxEVT_CHAR types, the values
1200 returned by them are different for the first two events and the last one.
1201 For the latter, the key returned corresponds to the character that would
1202 appear in e.g. a text zone if the user pressed the key in it. As such, its
1203 value depends on the current state of the Shift key and, for the letters,
1204 on the state of Caps Lock modifier. For example, if @c A key is pressed
1205 without Shift being held down, wxKeyEvent of type @c wxEVT_CHAR generated
1206 for this key press will return (from either GetKeyCode() or GetUnicodeKey()
1207 as their meanings coincide for ASCII characters) key code of 97
1208 corresponding the ASCII value of @c a. And if the same key is pressed but
1209 with Shift being held (or Caps Lock being active), then the key could would
1210 be 65, i.e. ASCII value of capital @c A.
1212 However for the key down and up events the returned key code will instead
1213 be @c A independently of the state of the modifier keys i.e. it depends
1214 only on physical key being pressed and is not translated to its logical
1215 representation using the current keyboard state. Such untranslated key
1216 codes are defined as follows:
1217 - For the letters they correspond to the @e upper case value of the
1219 - For the other alphanumeric keys (e.g. @c 7 or @c +), the untranslated
1220 key code corresponds to the character produced by the key when it is
1221 pressed without Shift. E.g. in standard US keyboard layout the
1222 untranslated key code for the key @c =/+ in the upper right corner of
1223 the keyboard is 61 which is the ASCII value of @c =.
1224 - For the rest of the keys (i.e. special non-printable keys) it is the
1225 same as the normal key code as no translation is used anyhow.
1227 Notice that the first rule applies to all Unicode letters, not just the
1228 usual Latin-1 ones. However for non-Latin-1 letters only GetUnicodeKey()
1229 can be used to retrieve the key code as GetKeyCode() just returns @c
1230 WXK_NONE in this case.
1232 To summarize: you should handle @c wxEVT_CHAR if you need the translated
1233 key and @c wxEVT_KEY_DOWN if you only need the value of the key itself,
1234 independent of the current keyboard state.
1236 @note Not all key down events may be generated by the user. As an example,
1237 @c wxEVT_KEY_DOWN with @c = key code can be generated using the
1238 standard US keyboard layout but not using the German one because the @c
1239 = key corresponds to Shift-0 key combination in this layout and the key
1240 code for it is @c 0, not @c =. Because of this you should avoid
1241 requiring your users to type key events that might be impossible to
1242 enter on their keyboard.
1245 Another difference between key and char events is that another kind of
1246 translation is done for the latter ones when the Control key is pressed:
1247 char events for ASCII letters in this case carry codes corresponding to the
1248 ASCII value of Ctrl-Latter, i.e. 1 for Ctrl-A, 2 for Ctrl-B and so on until
1249 26 for Ctrl-Z. This is convenient for terminal-like applications and can be
1250 completely ignored by all the other ones (if you need to handle Ctrl-A it
1251 is probably a better idea to use the key event rather than the char one).
1252 Notice that currently no translation is done for the presses of @c [, @c
1253 \\, @c ], @c ^ and @c _ keys which might be mapped to ASCII values from 27
1256 Finally, modifier keys only generate key events but no char events at all.
1257 The modifiers keys are @c WXK_SHIFT, @c WXK_CONTROL, @c WXK_ALT and various
1258 @c WXK_WINDOWS_XXX from ::wxKeyCode enum.
1260 Modifier keys events are special in one additional aspect: usually the
1261 keyboard state associated with a key press is well defined, e.g.
1262 wxKeyboardState::ShiftDown() returns @c true only if the Shift key was held
1263 pressed when the key that generated this event itself was pressed. There is
1264 an ambiguity for the key press events for Shift key itself however. By
1265 convention, it is considered to be already pressed when it is pressed and
1266 already released when it is released. In other words, @c wxEVT_KEY_DOWN
1267 event for the Shift key itself will have @c wxMOD_SHIFT in GetModifiers()
1268 and ShiftDown() will return true while the @c wxEVT_KEY_UP event for Shift
1269 itself will not have @c wxMOD_SHIFT in its modifiers and ShiftDown() will
1273 @b Tip: You may discover the key codes and modifiers generated by all the
1274 keys on your system interactively by running the @ref
1275 page_samples_keyboard wxWidgets sample and pressing some keys in it.
1277 @note If a key down (@c EVT_KEY_DOWN) event is caught and the event handler
1278 does not call @c event.Skip() then the corresponding char event
1279 (@c EVT_CHAR) will not happen. This is by design and enables the
1280 programs that handle both types of events to avoid processing the
1281 same key twice. As a consequence, if you do not want to suppress the
1282 @c wxEVT_CHAR events for the keys you handle, always call @c
1283 event.Skip() in your @c wxEVT_KEY_DOWN handler. Not doing may also
1284 prevent accelerators defined using this key from working.
1286 @note If a key is maintained in a pressed state, you will typically get a
1287 lot of (automatically generated) key down events but only one key up
1288 one at the end when the key is released so it is wrong to assume that
1289 there is one up event corresponding to each down one.
1291 @note For Windows programmers: The key and char events in wxWidgets are
1292 similar to but slightly different from Windows @c WM_KEYDOWN and
1293 @c WM_CHAR events. In particular, Alt-x combination will generate a
1294 char event in wxWidgets (unless it is used as an accelerator) and
1295 almost all keys, including ones without ASCII equivalents, generate
1299 @beginEventTable{wxKeyEvent}
1300 @event{EVT_KEY_DOWN(func)}
1301 Process a @c wxEVT_KEY_DOWN event (any key has been pressed).
1302 @event{EVT_KEY_UP(func)}
1303 Process a @c wxEVT_KEY_UP event (any key has been released).
1304 @event{EVT_CHAR(func)}
1305 Process a @c wxEVT_CHAR event.
1308 @see wxKeyboardState
1313 class wxKeyEvent
: public wxEvent
,
1314 public wxKeyboardState
1319 Currently, the only valid event types are @c wxEVT_CHAR and @c wxEVT_CHAR_HOOK.
1321 wxKeyEvent(wxEventType keyEventType
= wxEVT_NULL
);
1324 Returns the key code of the key that generated this event.
1326 ASCII symbols return normal ASCII values, while events from special
1327 keys such as "left cursor arrow" (@c WXK_LEFT) return values outside of
1328 the ASCII range. See ::wxKeyCode for a full list of the virtual key
1331 Note that this method returns a meaningful value only for special
1332 non-alphanumeric keys or if the user entered a character that can be
1333 represented in current locale's default charset. Otherwise, e.g. if the
1334 user enters a Japanese character in a program not using Japanese
1335 locale, this method returns @c WXK_NONE and GetUnicodeKey() should be
1336 used to obtain the corresponding Unicode character.
1338 Using GetUnicodeKey() is in general the right thing to do if you are
1339 interested in the characters typed by the user, GetKeyCode() should be
1340 only used for special keys (for which GetUnicodeKey() returns @c
1341 WXK_NONE). To handle both kinds of keys you might write:
1343 void MyHandler::OnChar(wxKeyEvent& event)
1345 if ( event.GetUnicodeKey() != WXK_NONE )
1347 // It's a printable character
1348 wxLogMessage("You pressed '%c'", event.GetUnicodeKey());
1352 // It's a special key, deal with all the known ones:
1368 int GetKeyCode() const;
1371 Returns true if the key is in the given key category.
1374 A bitwise combination of named ::wxKeyCategoryFlags constants.
1378 bool IsKeyInCategory(int category
) const;
1382 Obtains the position (in client coordinates) at which the key was pressed.
1384 wxPoint
GetPosition() const;
1385 void GetPosition(long* x
, long* y
) const;
1389 Returns the raw key code for this event.
1391 The flags are platform-dependent and should only be used if the
1392 functionality provided by other wxKeyEvent methods is insufficient.
1394 Under MSW, the raw key code is the value of @c wParam parameter of the
1395 corresponding message.
1397 Under GTK, the raw key code is the @c keyval field of the corresponding
1400 Under OS X, the raw key code is the @c keyCode field of the
1401 corresponding NSEvent.
1403 @note Currently the raw key codes are not supported by all ports, use
1404 @ifdef_ wxHAS_RAW_KEY_CODES to determine if this feature is available.
1406 wxUint32
GetRawKeyCode() const;
1409 Returns the low level key flags for this event.
1411 The flags are platform-dependent and should only be used if the
1412 functionality provided by other wxKeyEvent methods is insufficient.
1414 Under MSW, the raw flags are just the value of @c lParam parameter of
1415 the corresponding message.
1417 Under GTK, the raw flags contain the @c hardware_keycode field of the
1418 corresponding GDK event.
1420 Under OS X, the raw flags contain the modifiers state.
1422 @note Currently the raw key flags are not supported by all ports, use
1423 @ifdef_ wxHAS_RAW_KEY_CODES to determine if this feature is available.
1425 wxUint32
GetRawKeyFlags() const;
1428 Returns the Unicode character corresponding to this key event.
1430 If the key pressed doesn't have any character value (e.g. a cursor key)
1431 this method will return @c WXK_NONE. In this case you should use
1432 GetKeyCode() to retrieve the value of the key.
1434 This function is only available in Unicode build, i.e. when
1435 @c wxUSE_UNICODE is 1.
1437 wxChar
GetUnicodeKey() const;
1440 Returns the X position (in client coordinates) of the event.
1442 wxCoord
GetX() const;
1445 Returns the Y position (in client coordinates) of the event.
1447 wxCoord
GetY() const;
1453 @class wxJoystickEvent
1455 This event class contains information about joystick events, particularly
1456 events received by windows.
1458 @beginEventTable{wxJoystickEvent}
1459 @event{EVT_JOY_BUTTON_DOWN(func)}
1460 Process a @c wxEVT_JOY_BUTTON_DOWN event.
1461 @event{EVT_JOY_BUTTON_UP(func)}
1462 Process a @c wxEVT_JOY_BUTTON_UP event.
1463 @event{EVT_JOY_MOVE(func)}
1464 Process a @c wxEVT_JOY_MOVE event.
1465 @event{EVT_JOY_ZMOVE(func)}
1466 Process a @c wxEVT_JOY_ZMOVE event.
1467 @event{EVT_JOYSTICK_EVENTS(func)}
1468 Processes all joystick events.
1476 class wxJoystickEvent
: public wxEvent
1482 wxJoystickEvent(wxEventType eventType
= wxEVT_NULL
, int state
= 0,
1483 int joystick
= wxJOYSTICK1
,
1487 Returns @true if the event was a down event from the specified button
1491 Can be @c wxJOY_BUTTONn where @c n is 1, 2, 3 or 4; or @c wxJOY_BUTTON_ANY to
1492 indicate any button down event.
1494 bool ButtonDown(int button
= wxJOY_BUTTON_ANY
) const;
1497 Returns @true if the specified button (or any button) was in a down state.
1500 Can be @c wxJOY_BUTTONn where @c n is 1, 2, 3 or 4; or @c wxJOY_BUTTON_ANY to
1501 indicate any button down event.
1503 bool ButtonIsDown(int button
= wxJOY_BUTTON_ANY
) const;
1506 Returns @true if the event was an up event from the specified button
1510 Can be @c wxJOY_BUTTONn where @c n is 1, 2, 3 or 4; or @c wxJOY_BUTTON_ANY to
1511 indicate any button down event.
1513 bool ButtonUp(int button
= wxJOY_BUTTON_ANY
) const;
1516 Returns the identifier of the button changing state.
1518 This is a @c wxJOY_BUTTONn identifier, where @c n is one of 1, 2, 3, 4.
1520 int GetButtonChange() const;
1523 Returns the down state of the buttons.
1525 This is a @c wxJOY_BUTTONn identifier, where @c n is one of 1, 2, 3, 4.
1527 int GetButtonState() const;
1530 Returns the identifier of the joystick generating the event - one of
1531 wxJOYSTICK1 and wxJOYSTICK2.
1533 int GetJoystick() const;
1536 Returns the x, y position of the joystick event.
1538 wxPoint
GetPosition() const;
1541 Returns the z position of the joystick event.
1543 int GetZPosition() const;
1546 Returns @true if this was a button up or down event
1547 (@e not 'is any button down?').
1549 bool IsButton() const;
1552 Returns @true if this was an x, y move event.
1554 bool IsMove() const;
1557 Returns @true if this was a z move event.
1559 bool IsZMove() const;
1565 @class wxScrollWinEvent
1567 A scroll event holds information about events sent from scrolling windows.
1569 Note that you can use the EVT_SCROLLWIN* macros for intercepting scroll window events
1570 from the receiving window.
1572 @beginEventTable{wxScrollWinEvent}
1573 @event{EVT_SCROLLWIN(func)}
1574 Process all scroll events.
1575 @event{EVT_SCROLLWIN_TOP(func)}
1576 Process wxEVT_SCROLLWIN_TOP scroll-to-top events.
1577 @event{EVT_SCROLLWIN_BOTTOM(func)}
1578 Process wxEVT_SCROLLWIN_BOTTOM scroll-to-bottom events.
1579 @event{EVT_SCROLLWIN_LINEUP(func)}
1580 Process wxEVT_SCROLLWIN_LINEUP line up events.
1581 @event{EVT_SCROLLWIN_LINEDOWN(func)}
1582 Process wxEVT_SCROLLWIN_LINEDOWN line down events.
1583 @event{EVT_SCROLLWIN_PAGEUP(func)}
1584 Process wxEVT_SCROLLWIN_PAGEUP page up events.
1585 @event{EVT_SCROLLWIN_PAGEDOWN(func)}
1586 Process wxEVT_SCROLLWIN_PAGEDOWN page down events.
1587 @event{EVT_SCROLLWIN_THUMBTRACK(func)}
1588 Process wxEVT_SCROLLWIN_THUMBTRACK thumbtrack events
1589 (frequent events sent as the user drags the thumbtrack).
1590 @event{EVT_SCROLLWIN_THUMBRELEASE(func)}
1591 Process wxEVT_SCROLLWIN_THUMBRELEASE thumb release events.
1598 @see wxScrollEvent, @ref overview_events
1600 class wxScrollWinEvent
: public wxEvent
1606 wxScrollWinEvent(wxEventType commandType
= wxEVT_NULL
, int pos
= 0,
1607 int orientation
= 0);
1610 Returns wxHORIZONTAL or wxVERTICAL, depending on the orientation of the
1613 @todo wxHORIZONTAL and wxVERTICAL should go in their own enum
1615 int GetOrientation() const;
1618 Returns the position of the scrollbar for the thumb track and release events.
1620 Note that this field can't be used for the other events, you need to query
1621 the window itself for the current position in that case.
1623 int GetPosition() const;
1629 @class wxSysColourChangedEvent
1631 This class is used for system colour change events, which are generated
1632 when the user changes the colour settings using the control panel.
1633 This is only appropriate under Windows.
1636 The default event handler for this event propagates the event to child windows,
1637 since Windows only sends the events to top-level windows.
1638 If intercepting this event for a top-level window, remember to call the base
1639 class handler, or to pass the event on to the window's children explicitly.
1641 @beginEventTable{wxSysColourChangedEvent}
1642 @event{EVT_SYS_COLOUR_CHANGED(func)}
1643 Process a @c wxEVT_SYS_COLOUR_CHANGED event.
1649 @see @ref overview_events
1651 class wxSysColourChangedEvent
: public wxEvent
1657 wxSysColourChangedEvent();
1663 @class wxWindowCreateEvent
1665 This event is sent just after the actual window associated with a wxWindow
1666 object has been created.
1668 Since it is derived from wxCommandEvent, the event propagates up
1669 the window hierarchy.
1671 @beginEventTable{wxWindowCreateEvent}
1672 @event{EVT_WINDOW_CREATE(func)}
1673 Process a @c wxEVT_CREATE event.
1679 @see @ref overview_events, wxWindowDestroyEvent
1681 class wxWindowCreateEvent
: public wxCommandEvent
1687 wxWindowCreateEvent(wxWindow
* win
= NULL
);
1689 /// Retutn the window being created.
1690 wxWindow
*GetWindow() const;
1698 A paint event is sent when a window's contents needs to be repainted.
1700 The handler of this event must create a wxPaintDC object and use it for
1701 painting the window contents. For example:
1703 void MyWindow::OnPaint(wxPaintEvent& event)
1711 Notice that you must @e not create other kinds of wxDC (e.g. wxClientDC or
1712 wxWindowDC) in EVT_PAINT handlers and also don't create wxPaintDC outside
1713 of this event handlers.
1716 You can optimize painting by retrieving the rectangles that have been damaged
1717 and only repainting these. The rectangles are in terms of the client area,
1718 and are unscrolled, so you will need to do some calculations using the current
1719 view position to obtain logical, scrolled units.
1720 Here is an example of using the wxRegionIterator class:
1722 // Called when window needs to be repainted.
1723 void MyWindow::OnPaint(wxPaintEvent& event)
1727 // Find Out where the window is scrolled to
1728 int vbX,vbY; // Top left corner of client
1729 GetViewStart(&vbX,&vbY);
1731 int vX,vY,vW,vH; // Dimensions of client area in pixels
1732 wxRegionIterator upd(GetUpdateRegion()); // get the update rect list
1741 // Alternatively we can do this:
1742 // wxRect rect(upd.GetRect());
1744 // Repaint this rectangle
1753 Please notice that in general it is impossible to change the drawing of a
1754 standard control (such as wxButton) and so you shouldn't attempt to handle
1755 paint events for them as even if it might work on some platforms, this is
1756 inherently not portable and won't work everywhere.
1759 @beginEventTable{wxPaintEvent}
1760 @event{EVT_PAINT(func)}
1761 Process a @c wxEVT_PAINT event.
1767 @see @ref overview_events
1769 class wxPaintEvent
: public wxEvent
1775 wxPaintEvent(int id
= 0);
1781 @class wxMaximizeEvent
1783 An event being sent when a top level window is maximized. Notice that it is
1784 not sent when the window is restored to its original size after it had been
1785 maximized, only a normal wxSizeEvent is generated in this case.
1787 @beginEventTable{wxMaximizeEvent}
1788 @event{EVT_MAXIMIZE(func)}
1789 Process a @c wxEVT_MAXIMIZE event.
1795 @see @ref overview_events, wxTopLevelWindow::Maximize,
1796 wxTopLevelWindow::IsMaximized
1798 class wxMaximizeEvent
: public wxEvent
1802 Constructor. Only used by wxWidgets internally.
1804 wxMaximizeEvent(int id
= 0);
1808 The possibles modes to pass to wxUpdateUIEvent::SetMode().
1812 /** Send UI update events to all windows. */
1813 wxUPDATE_UI_PROCESS_ALL
,
1815 /** Send UI update events to windows that have
1816 the wxWS_EX_PROCESS_UI_UPDATES flag specified. */
1817 wxUPDATE_UI_PROCESS_SPECIFIED
1822 @class wxUpdateUIEvent
1824 This class is used for pseudo-events which are called by wxWidgets
1825 to give an application the chance to update various user interface elements.
1827 Without update UI events, an application has to work hard to check/uncheck,
1828 enable/disable, show/hide, and set the text for elements such as menu items
1829 and toolbar buttons. The code for doing this has to be mixed up with the code
1830 that is invoked when an action is invoked for a menu item or button.
1832 With update UI events, you define an event handler to look at the state of the
1833 application and change UI elements accordingly. wxWidgets will call your member
1834 functions in idle time, so you don't have to worry where to call this code.
1836 In addition to being a clearer and more declarative method, it also means you don't
1837 have to worry whether you're updating a toolbar or menubar identifier. The same
1838 handler can update a menu item and toolbar button, if the identifier is the same.
1839 Instead of directly manipulating the menu or button, you call functions in the event
1840 object, such as wxUpdateUIEvent::Check. wxWidgets will determine whether such a
1841 call has been made, and which UI element to update.
1843 These events will work for popup menus as well as menubars. Just before a menu is
1844 popped up, wxMenu::UpdateUI is called to process any UI events for the window that
1847 If you find that the overhead of UI update processing is affecting your application,
1848 you can do one or both of the following:
1849 @li Call wxUpdateUIEvent::SetMode with a value of wxUPDATE_UI_PROCESS_SPECIFIED,
1850 and set the extra style wxWS_EX_PROCESS_UI_UPDATES for every window that should
1851 receive update events. No other windows will receive update events.
1852 @li Call wxUpdateUIEvent::SetUpdateInterval with a millisecond value to set the delay
1853 between updates. You may need to call wxWindow::UpdateWindowUI at critical points,
1854 for example when a dialog is about to be shown, in case the user sees a slight
1855 delay before windows are updated.
1857 Note that although events are sent in idle time, defining a wxIdleEvent handler
1858 for a window does not affect this because the events are sent from wxWindow::OnInternalIdle
1859 which is always called in idle time.
1861 wxWidgets tries to optimize update events on some platforms.
1862 On Windows and GTK+, events for menubar items are only sent when the menu is about
1863 to be shown, and not in idle time.
1866 @beginEventTable{wxUpdateUIEvent}
1867 @event{EVT_UPDATE_UI(id, func)}
1868 Process a @c wxEVT_UPDATE_UI event for the command with the given id.
1869 @event{EVT_UPDATE_UI_RANGE(id1, id2, func)}
1870 Process a @c wxEVT_UPDATE_UI event for any command with id included in the given range.
1876 @see @ref overview_events
1878 class wxUpdateUIEvent
: public wxCommandEvent
1884 wxUpdateUIEvent(wxWindowID commandId
= 0);
1887 Returns @true if it is appropriate to update (send UI update events to)
1890 This function looks at the mode used (see wxUpdateUIEvent::SetMode),
1891 the wxWS_EX_PROCESS_UI_UPDATES flag in @a window, the time update events
1892 were last sent in idle time, and the update interval, to determine whether
1893 events should be sent to this window now. By default this will always
1894 return @true because the update mode is initially wxUPDATE_UI_PROCESS_ALL
1895 and the interval is set to 0; so update events will be sent as often as
1896 possible. You can reduce the frequency that events are sent by changing the
1897 mode and/or setting an update interval.
1899 @see ResetUpdateTime(), SetUpdateInterval(), SetMode()
1901 static bool CanUpdate(wxWindow
* window
);
1904 Check or uncheck the UI element.
1906 void Check(bool check
);
1909 Enable or disable the UI element.
1911 void Enable(bool enable
);
1914 Returns @true if the UI element should be checked.
1916 bool GetChecked() const;
1919 Returns @true if the UI element should be enabled.
1921 bool GetEnabled() const;
1924 Static function returning a value specifying how wxWidgets will send update
1925 events: to all windows, or only to those which specify that they will process
1930 static wxUpdateUIMode
GetMode();
1933 Returns @true if the application has called Check().
1934 For wxWidgets internal use only.
1936 bool GetSetChecked() const;
1939 Returns @true if the application has called Enable().
1940 For wxWidgets internal use only.
1942 bool GetSetEnabled() const;
1945 Returns @true if the application has called Show().
1946 For wxWidgets internal use only.
1948 bool GetSetShown() const;
1951 Returns @true if the application has called SetText().
1952 For wxWidgets internal use only.
1954 bool GetSetText() const;
1957 Returns @true if the UI element should be shown.
1959 bool GetShown() const;
1962 Returns the text that should be set for the UI element.
1964 wxString
GetText() const;
1967 Returns the current interval between updates in milliseconds.
1968 The value -1 disables updates, 0 updates as frequently as possible.
1970 @see SetUpdateInterval().
1972 static long GetUpdateInterval();
1975 Used internally to reset the last-updated time to the current time.
1977 It is assumed that update events are normally sent in idle time, so this
1978 is called at the end of idle processing.
1980 @see CanUpdate(), SetUpdateInterval(), SetMode()
1982 static void ResetUpdateTime();
1985 Specify how wxWidgets will send update events: to all windows, or only to
1986 those which specify that they will process the events.
1989 this parameter may be one of the ::wxUpdateUIMode enumeration values.
1990 The default mode is wxUPDATE_UI_PROCESS_ALL.
1992 static void SetMode(wxUpdateUIMode mode
);
1995 Sets the text for this UI element.
1997 void SetText(const wxString
& text
);
2000 Sets the interval between updates in milliseconds.
2002 Set to -1 to disable updates, or to 0 to update as frequently as possible.
2005 Use this to reduce the overhead of UI update events if your application
2006 has a lot of windows. If you set the value to -1 or greater than 0,
2007 you may also need to call wxWindow::UpdateWindowUI at appropriate points
2008 in your application, such as when a dialog is about to be shown.
2010 static void SetUpdateInterval(long updateInterval
);
2013 Show or hide the UI element.
2015 void Show(bool show
);
2021 @class wxClipboardTextEvent
2023 This class represents the events generated by a control (typically a
2024 wxTextCtrl but other windows can generate these events as well) when its
2025 content gets copied or cut to, or pasted from the clipboard.
2027 There are three types of corresponding events wxEVT_COMMAND_TEXT_COPY,
2028 wxEVT_COMMAND_TEXT_CUT and wxEVT_COMMAND_TEXT_PASTE.
2030 If any of these events is processed (without being skipped) by an event
2031 handler, the corresponding operation doesn't take place which allows to
2032 prevent the text from being copied from or pasted to a control. It is also
2033 possible to examine the clipboard contents in the PASTE event handler and
2034 transform it in some way before inserting in a control -- for example,
2035 changing its case or removing invalid characters.
2037 Finally notice that a CUT event is always preceded by the COPY event which
2038 makes it possible to only process the latter if it doesn't matter if the
2039 text was copied or cut.
2042 These events are currently only generated by wxTextCtrl under GTK+.
2043 They are generated by all controls under Windows.
2045 @beginEventTable{wxClipboardTextEvent}
2046 @event{EVT_TEXT_COPY(id, func)}
2047 Some or all of the controls content was copied to the clipboard.
2048 @event{EVT_TEXT_CUT(id, func)}
2049 Some or all of the controls content was cut (i.e. copied and
2051 @event{EVT_TEXT_PASTE(id, func)}
2052 Clipboard content was pasted into the control.
2061 class wxClipboardTextEvent
: public wxCommandEvent
2067 wxClipboardTextEvent(wxEventType commandType
= wxEVT_NULL
, int id
= 0);
2075 This event class contains information about the events generated by the mouse:
2076 they include mouse buttons press and release events and mouse move events.
2078 All mouse events involving the buttons use @c wxMOUSE_BTN_LEFT for the
2079 left mouse button, @c wxMOUSE_BTN_MIDDLE for the middle one and
2080 @c wxMOUSE_BTN_RIGHT for the right one. And if the system supports more
2081 buttons, the @c wxMOUSE_BTN_AUX1 and @c wxMOUSE_BTN_AUX2 events
2082 can also be generated. Note that not all mice have even a middle button so a
2083 portable application should avoid relying on the events from it (but the right
2084 button click can be emulated using the left mouse button with the control key
2085 under Mac platforms with a single button mouse).
2087 For the @c wxEVT_ENTER_WINDOW and @c wxEVT_LEAVE_WINDOW events
2088 purposes, the mouse is considered to be inside the window if it is in the
2089 window client area and not inside one of its children. In other words, the
2090 parent window receives @c wxEVT_LEAVE_WINDOW event not only when the
2091 mouse leaves the window entirely but also when it enters one of its children.
2093 The position associated with a mouse event is expressed in the window
2094 coordinates of the window which generated the event, you can use
2095 wxWindow::ClientToScreen() to convert it to screen coordinates and possibly
2096 call wxWindow::ScreenToClient() next to convert it to window coordinates of
2099 @note Note that under Windows CE mouse enter and leave events are not natively
2100 supported by the system but are generated by wxWidgets itself. This has several
2101 drawbacks: the LEAVE_WINDOW event might be received some time after the mouse
2102 left the window and the state variables for it may have changed during this time.
2104 @note Note the difference between methods like wxMouseEvent::LeftDown and
2105 the inherited wxMouseState::LeftIsDown: the former returns @true when
2106 the event corresponds to the left mouse button click while the latter
2107 returns @true if the left mouse button is currently being pressed.
2108 For example, when the user is dragging the mouse you can use
2109 wxMouseEvent::LeftIsDown to test whether the left mouse button is
2110 (still) depressed. Also, by convention, if wxMouseEvent::LeftDown
2111 returns @true, wxMouseEvent::LeftIsDown will also return @true in
2112 wxWidgets whatever the underlying GUI behaviour is (which is
2113 platform-dependent). The same applies, of course, to other mouse
2117 @beginEventTable{wxMouseEvent}
2118 @event{EVT_LEFT_DOWN(func)}
2119 Process a @c wxEVT_LEFT_DOWN event. The handler of this event should normally
2120 call event.Skip() to allow the default processing to take place as otherwise
2121 the window under mouse wouldn't get the focus.
2122 @event{EVT_LEFT_UP(func)}
2123 Process a @c wxEVT_LEFT_UP event.
2124 @event{EVT_LEFT_DCLICK(func)}
2125 Process a @c wxEVT_LEFT_DCLICK event.
2126 @event{EVT_MIDDLE_DOWN(func)}
2127 Process a @c wxEVT_MIDDLE_DOWN event.
2128 @event{EVT_MIDDLE_UP(func)}
2129 Process a @c wxEVT_MIDDLE_UP event.
2130 @event{EVT_MIDDLE_DCLICK(func)}
2131 Process a @c wxEVT_MIDDLE_DCLICK event.
2132 @event{EVT_RIGHT_DOWN(func)}
2133 Process a @c wxEVT_RIGHT_DOWN event.
2134 @event{EVT_RIGHT_UP(func)}
2135 Process a @c wxEVT_RIGHT_UP event.
2136 @event{EVT_RIGHT_DCLICK(func)}
2137 Process a @c wxEVT_RIGHT_DCLICK event.
2138 @event{EVT_MOUSE_AUX1_DOWN(func)}
2139 Process a @c wxEVT_AUX1_DOWN event.
2140 @event{EVT_MOUSE_AUX1_UP(func)}
2141 Process a @c wxEVT_AUX1_UP event.
2142 @event{EVT_MOUSE_AUX1_DCLICK(func)}
2143 Process a @c wxEVT_AUX1_DCLICK event.
2144 @event{EVT_MOUSE_AUX2_DOWN(func)}
2145 Process a @c wxEVT_AUX2_DOWN event.
2146 @event{EVT_MOUSE_AUX2_UP(func)}
2147 Process a @c wxEVT_AUX2_UP event.
2148 @event{EVT_MOUSE_AUX2_DCLICK(func)}
2149 Process a @c wxEVT_AUX2_DCLICK event.
2150 @event{EVT_MOTION(func)}
2151 Process a @c wxEVT_MOTION event.
2152 @event{EVT_ENTER_WINDOW(func)}
2153 Process a @c wxEVT_ENTER_WINDOW event.
2154 @event{EVT_LEAVE_WINDOW(func)}
2155 Process a @c wxEVT_LEAVE_WINDOW event.
2156 @event{EVT_MOUSEWHEEL(func)}
2157 Process a @c wxEVT_MOUSEWHEEL event.
2158 @event{EVT_MOUSE_EVENTS(func)}
2159 Process all mouse events.
2167 class wxMouseEvent
: public wxEvent
,
2172 Constructor. Valid event types are:
2174 @li wxEVT_ENTER_WINDOW
2175 @li wxEVT_LEAVE_WINDOW
2178 @li wxEVT_LEFT_DCLICK
2179 @li wxEVT_MIDDLE_DOWN
2181 @li wxEVT_MIDDLE_DCLICK
2182 @li wxEVT_RIGHT_DOWN
2184 @li wxEVT_RIGHT_DCLICK
2185 @li wxEVT_MOUSE_AUX1_DOWN
2186 @li wxEVT_MOUSE_AUX1_UP
2187 @li wxEVT_MOUSE_AUX1_DCLICK
2188 @li wxEVT_MOUSE_AUX2_DOWN
2189 @li wxEVT_MOUSE_AUX2_UP
2190 @li wxEVT_MOUSE_AUX2_DCLICK
2192 @li wxEVT_MOUSEWHEEL
2194 wxMouseEvent(wxEventType mouseEventType
= wxEVT_NULL
);
2197 Returns @true if the event was a first extra button double click.
2199 bool Aux1DClick() const;
2202 Returns @true if the first extra button mouse button changed to down.
2204 bool Aux1Down() const;
2207 Returns @true if the first extra button mouse button changed to up.
2209 bool Aux1Up() const;
2212 Returns @true if the event was a second extra button double click.
2214 bool Aux2DClick() const;
2217 Returns @true if the second extra button mouse button changed to down.
2219 bool Aux2Down() const;
2222 Returns @true if the second extra button mouse button changed to up.
2224 bool Aux2Up() const;
2227 Returns @true if the event was generated by the specified button.
2229 @see wxMouseState::ButtoinIsDown()
2231 bool Button(wxMouseButton but
) const;
2234 If the argument is omitted, this returns @true if the event was a mouse
2235 double click event. Otherwise the argument specifies which double click event
2236 was generated (see Button() for the possible values).
2238 bool ButtonDClick(wxMouseButton but
= wxMOUSE_BTN_ANY
) const;
2241 If the argument is omitted, this returns @true if the event was a mouse
2242 button down event. Otherwise the argument specifies which button-down event
2243 was generated (see Button() for the possible values).
2245 bool ButtonDown(wxMouseButton but
= wxMOUSE_BTN_ANY
) const;
2248 If the argument is omitted, this returns @true if the event was a mouse
2249 button up event. Otherwise the argument specifies which button-up event
2250 was generated (see Button() for the possible values).
2252 bool ButtonUp(wxMouseButton but
= wxMOUSE_BTN_ANY
) const;
2255 Returns @true if this was a dragging event (motion while a button is depressed).
2259 bool Dragging() const;
2262 Returns @true if the mouse was entering the window.
2266 bool Entering() const;
2269 Returns the mouse button which generated this event or @c wxMOUSE_BTN_NONE
2270 if no button is involved (for mouse move, enter or leave event, for example).
2271 Otherwise @c wxMOUSE_BTN_LEFT is returned for the left button down, up and
2272 double click events, @c wxMOUSE_BTN_MIDDLE and @c wxMOUSE_BTN_RIGHT
2273 for the same events for the middle and the right buttons respectively.
2275 int GetButton() const;
2278 Returns the number of mouse clicks for this event: 1 for a simple click, 2
2279 for a double-click, 3 for a triple-click and so on.
2281 Currently this function is implemented only in wxMac and returns -1 for the
2282 other platforms (you can still distinguish simple clicks from double-clicks as
2283 they generate different kinds of events however).
2287 int GetClickCount() const;
2290 Returns the configured number of lines (or whatever) to be scrolled per
2291 wheel action. Defaults to three.
2293 int GetLinesPerAction() const;
2296 Returns the logical mouse position in pixels (i.e. translated according to the
2297 translation set for the DC, which usually indicates that the window has been
2300 wxPoint
GetLogicalPosition(const wxDC
& dc
) const;
2303 Get wheel delta, normally 120.
2305 This is the threshold for action to be taken, and one such action
2306 (for example, scrolling one increment) should occur for each delta.
2308 int GetWheelDelta() const;
2311 Get wheel rotation, positive or negative indicates direction of rotation.
2313 Current devices all send an event when rotation is at least +/-WheelDelta, but
2314 finer resolution devices can be created in the future.
2316 Because of this you shouldn't assume that one event is equal to 1 line, but you
2317 should be able to either do partial line scrolling or wait until several
2318 events accumulate before scrolling.
2320 int GetWheelRotation() const;
2323 Gets the axis the wheel operation concerns; @c 0 is the Y axis as on
2324 most mouse wheels, @c 1 is the X axis.
2326 Note that only some models of mouse have horizontal wheel axis.
2328 int GetWheelAxis() const;
2331 Returns @true if the event was a mouse button event (not necessarily a button
2332 down event - that may be tested using ButtonDown()).
2334 bool IsButton() const;
2337 Returns @true if the system has been setup to do page scrolling with
2338 the mouse wheel instead of line scrolling.
2340 bool IsPageScroll() const;
2343 Returns @true if the mouse was leaving the window.
2347 bool Leaving() const;
2350 Returns @true if the event was a left double click.
2352 bool LeftDClick() const;
2355 Returns @true if the left mouse button changed to down.
2357 bool LeftDown() const;
2360 Returns @true if the left mouse button changed to up.
2362 bool LeftUp() const;
2365 Returns @true if the Meta key was down at the time of the event.
2367 bool MetaDown() const;
2370 Returns @true if the event was a middle double click.
2372 bool MiddleDClick() const;
2375 Returns @true if the middle mouse button changed to down.
2377 bool MiddleDown() const;
2380 Returns @true if the middle mouse button changed to up.
2382 bool MiddleUp() const;
2385 Returns @true if this was a motion event and no mouse buttons were pressed.
2386 If any mouse button is held pressed, then this method returns @false and
2387 Dragging() returns @true.
2389 bool Moving() const;
2392 Returns @true if the event was a right double click.
2394 bool RightDClick() const;
2397 Returns @true if the right mouse button changed to down.
2399 bool RightDown() const;
2402 Returns @true if the right mouse button changed to up.
2404 bool RightUp() const;
2410 @class wxDropFilesEvent
2412 This class is used for drop files events, that is, when files have been dropped
2413 onto the window. This functionality is currently only available under Windows.
2415 The window must have previously been enabled for dropping by calling
2416 wxWindow::DragAcceptFiles().
2418 Important note: this is a separate implementation to the more general drag and drop
2419 implementation documented in the @ref overview_dnd. It uses the older, Windows
2420 message-based approach of dropping files.
2422 @beginEventTable{wxDropFilesEvent}
2423 @event{EVT_DROP_FILES(func)}
2424 Process a @c wxEVT_DROP_FILES event.
2432 @see @ref overview_events
2434 class wxDropFilesEvent
: public wxEvent
2440 wxDropFilesEvent(wxEventType id
= 0, int noFiles
= 0,
2441 wxString
* files
= NULL
);
2444 Returns an array of filenames.
2446 wxString
* GetFiles() const;
2449 Returns the number of files dropped.
2451 int GetNumberOfFiles() const;
2454 Returns the position at which the files were dropped.
2455 Returns an array of filenames.
2457 wxPoint
GetPosition() const;
2463 @class wxCommandEvent
2465 This event class contains information about command events, which originate
2466 from a variety of simple controls.
2468 Note that wxCommandEvents and wxCommandEvent-derived event classes by default
2469 and unlike other wxEvent-derived classes propagate upward from the source
2470 window (the window which emits the event) up to the first parent which processes
2471 the event. Be sure to read @ref overview_events_propagation.
2473 More complex controls, such as wxTreeCtrl, have separate command event classes.
2475 @beginEventTable{wxCommandEvent}
2476 @event{EVT_COMMAND(id, event, func)}
2477 Process a command, supplying the window identifier, command event identifier,
2478 and member function.
2479 @event{EVT_COMMAND_RANGE(id1, id2, event, func)}
2480 Process a command for a range of window identifiers, supplying the minimum and
2481 maximum window identifiers, command event identifier, and member function.
2482 @event{EVT_BUTTON(id, func)}
2483 Process a @c wxEVT_COMMAND_BUTTON_CLICKED command, which is generated by a wxButton control.
2484 @event{EVT_CHECKBOX(id, func)}
2485 Process a @c wxEVT_COMMAND_CHECKBOX_CLICKED command, which is generated by a wxCheckBox control.
2486 @event{EVT_CHOICE(id, func)}
2487 Process a @c wxEVT_COMMAND_CHOICE_SELECTED command, which is generated by a wxChoice control.
2488 @event{EVT_COMBOBOX(id, func)}
2489 Process a @c wxEVT_COMMAND_COMBOBOX_SELECTED command, which is generated by a wxComboBox control.
2490 @event{EVT_LISTBOX(id, func)}
2491 Process a @c wxEVT_COMMAND_LISTBOX_SELECTED command, which is generated by a wxListBox control.
2492 @event{EVT_LISTBOX_DCLICK(id, func)}
2493 Process a @c wxEVT_COMMAND_LISTBOX_DOUBLECLICKED command, which is generated by a wxListBox control.
2494 @event{EVT_CHECKLISTBOX(id, func)}
2495 Process a @c wxEVT_COMMAND_CHECKLISTBOX_TOGGLED command, which is generated by a wxCheckListBox control.
2496 @event{EVT_MENU(id, func)}
2497 Process a @c wxEVT_COMMAND_MENU_SELECTED command, which is generated by a menu item.
2498 @event{EVT_MENU_RANGE(id1, id2, func)}
2499 Process a @c wxEVT_COMMAND_MENU_RANGE command, which is generated by a range of menu items.
2500 @event{EVT_CONTEXT_MENU(func)}
2501 Process the event generated when the user has requested a popup menu to appear by
2502 pressing a special keyboard key (under Windows) or by right clicking the mouse.
2503 @event{EVT_RADIOBOX(id, func)}
2504 Process a @c wxEVT_COMMAND_RADIOBOX_SELECTED command, which is generated by a wxRadioBox control.
2505 @event{EVT_RADIOBUTTON(id, func)}
2506 Process a @c wxEVT_COMMAND_RADIOBUTTON_SELECTED command, which is generated by a wxRadioButton control.
2507 @event{EVT_SCROLLBAR(id, func)}
2508 Process a @c wxEVT_COMMAND_SCROLLBAR_UPDATED command, which is generated by a wxScrollBar
2509 control. This is provided for compatibility only; more specific scrollbar event macros
2510 should be used instead (see wxScrollEvent).
2511 @event{EVT_SLIDER(id, func)}
2512 Process a @c wxEVT_COMMAND_SLIDER_UPDATED command, which is generated by a wxSlider control.
2513 @event{EVT_TEXT(id, func)}
2514 Process a @c wxEVT_COMMAND_TEXT_UPDATED command, which is generated by a wxTextCtrl control.
2515 @event{EVT_TEXT_ENTER(id, func)}
2516 Process a @c wxEVT_COMMAND_TEXT_ENTER command, which is generated by a wxTextCtrl control.
2517 Note that you must use wxTE_PROCESS_ENTER flag when creating the control if you want it
2518 to generate such events.
2519 @event{EVT_TEXT_MAXLEN(id, func)}
2520 Process a @c wxEVT_COMMAND_TEXT_MAXLEN command, which is generated by a wxTextCtrl control
2521 when the user tries to enter more characters into it than the limit previously set
2522 with SetMaxLength().
2523 @event{EVT_TOGGLEBUTTON(id, func)}
2524 Process a @c wxEVT_COMMAND_TOGGLEBUTTON_CLICKED event.
2525 @event{EVT_TOOL(id, func)}
2526 Process a @c wxEVT_COMMAND_TOOL_CLICKED event (a synonym for @c wxEVT_COMMAND_MENU_SELECTED).
2527 Pass the id of the tool.
2528 @event{EVT_TOOL_RANGE(id1, id2, func)}
2529 Process a @c wxEVT_COMMAND_TOOL_CLICKED event for a range of identifiers. Pass the ids of the tools.
2530 @event{EVT_TOOL_RCLICKED(id, func)}
2531 Process a @c wxEVT_COMMAND_TOOL_RCLICKED event. Pass the id of the tool. (Not available on wxOSX.)
2532 @event{EVT_TOOL_RCLICKED_RANGE(id1, id2, func)}
2533 Process a @c wxEVT_COMMAND_TOOL_RCLICKED event for a range of ids. Pass the ids of the tools. (Not available on wxOSX.)
2534 @event{EVT_TOOL_ENTER(id, func)}
2535 Process a @c wxEVT_COMMAND_TOOL_ENTER event. Pass the id of the toolbar itself.
2536 The value of wxCommandEvent::GetSelection() is the tool id, or -1 if the mouse cursor
2537 has moved off a tool. (Not available on wxOSX.)
2538 @event{EVT_COMMAND_LEFT_CLICK(id, func)}
2539 Process a @c wxEVT_COMMAND_LEFT_CLICK command, which is generated by a control (wxMSW only).
2540 @event{EVT_COMMAND_LEFT_DCLICK(id, func)}
2541 Process a @c wxEVT_COMMAND_LEFT_DCLICK command, which is generated by a control (wxMSW only).
2542 @event{EVT_COMMAND_RIGHT_CLICK(id, func)}
2543 Process a @c wxEVT_COMMAND_RIGHT_CLICK command, which is generated by a control (wxMSW only).
2544 @event{EVT_COMMAND_SET_FOCUS(id, func)}
2545 Process a @c wxEVT_COMMAND_SET_FOCUS command, which is generated by a control (wxMSW only).
2546 @event{EVT_COMMAND_KILL_FOCUS(id, func)}
2547 Process a @c wxEVT_COMMAND_KILL_FOCUS command, which is generated by a control (wxMSW only).
2548 @event{EVT_COMMAND_ENTER(id, func)}
2549 Process a @c wxEVT_COMMAND_ENTER command, which is generated by a control.
2555 class wxCommandEvent
: public wxEvent
2561 wxCommandEvent(wxEventType commandEventType
= wxEVT_NULL
, int id
= 0);
2564 Returns client data pointer for a listbox or choice selection event
2565 (not valid for a deselection).
2567 void* GetClientData() const;
2570 Returns client object pointer for a listbox or choice selection event
2571 (not valid for a deselection).
2573 wxClientData
* GetClientObject() const;
2576 Returns extra information dependant on the event objects type.
2578 If the event comes from a listbox selection, it is a boolean
2579 determining whether the event was a selection (@true) or a
2580 deselection (@false). A listbox deselection only occurs for
2581 multiple-selection boxes, and in this case the index and string values
2582 are indeterminate and the listbox must be examined by the application.
2584 long GetExtraLong() const;
2587 Returns the integer identifier corresponding to a listbox, choice or
2588 radiobox selection (only if the event was a selection, not a deselection),
2589 or a boolean value representing the value of a checkbox.
2594 Returns item index for a listbox or choice selection event (not valid for
2597 int GetSelection() const;
2600 Returns item string for a listbox or choice selection event. If one
2601 or several items have been deselected, returns the index of the first
2602 deselected item. If some items have been selected and others deselected
2603 at the same time, it will return the index of the first selected item.
2605 wxString
GetString() const;
2608 This method can be used with checkbox and menu events: for the checkboxes, the
2609 method returns @true for a selection event and @false for a deselection one.
2610 For the menu events, this method indicates if the menu item just has become
2611 checked or unchecked (and thus only makes sense for checkable menu items).
2613 Notice that this method can not be used with wxCheckListBox currently.
2615 bool IsChecked() const;
2618 For a listbox or similar event, returns @true if it is a selection, @false
2619 if it is a deselection. If some items have been selected and others deselected
2620 at the same time, it will return @true.
2622 bool IsSelection() const;
2625 Sets the client data for this event.
2627 void SetClientData(void* clientData
);
2630 Sets the client object for this event. The client object is not owned by the
2631 event object and the event object will not delete the client object in its destructor.
2633 The client object must be owned and deleted by another object (e.g. a control)
2634 that has longer life time than the event object.
2636 void SetClientObject(wxClientData
* clientObject
);
2639 Sets the @b m_extraLong member.
2641 void SetExtraLong(long extraLong
);
2644 Sets the @b m_commandInt member.
2646 void SetInt(int intCommand
);
2649 Sets the @b m_commandString member.
2651 void SetString(const wxString
& string
);
2657 @class wxActivateEvent
2659 An activate event is sent when a window or application is being activated
2662 @beginEventTable{wxActivateEvent}
2663 @event{EVT_ACTIVATE(func)}
2664 Process a @c wxEVT_ACTIVATE event.
2665 @event{EVT_ACTIVATE_APP(func)}
2666 Process a @c wxEVT_ACTIVATE_APP event.
2667 This event is received by the wxApp-derived instance only.
2668 @event{EVT_HIBERNATE(func)}
2669 Process a hibernate event, supplying the member function. This event applies
2670 to wxApp only, and only on Windows SmartPhone and PocketPC.
2671 It is generated when the system is low on memory; the application should free
2672 up as much memory as possible, and restore full working state when it receives
2673 a wxEVT_ACTIVATE or wxEVT_ACTIVATE_APP event.
2679 @see @ref overview_events, wxApp::IsActive
2681 class wxActivateEvent
: public wxEvent
2687 wxActivateEvent(wxEventType eventType
= wxEVT_NULL
, bool active
= true,
2691 Returns @true if the application or window is being activated, @false otherwise.
2693 bool GetActive() const;
2699 @class wxContextMenuEvent
2701 This class is used for context menu events, sent to give
2702 the application a chance to show a context (popup) menu for a wxWindow.
2704 Note that if wxContextMenuEvent::GetPosition returns wxDefaultPosition, this
2705 means that the event originated from a keyboard context button event, and you
2706 should compute a suitable position yourself, for example by calling wxGetMousePosition().
2708 When a keyboard context menu button is pressed on Windows, a right-click event
2709 with default position is sent first, and if this event is not processed, the
2710 context menu event is sent. So if you process mouse events and you find your
2711 context menu event handler is not being called, you could call wxEvent::Skip()
2712 for mouse right-down events.
2714 @beginEventTable{wxContextMenuEvent}
2715 @event{EVT_CONTEXT_MENU(func)}
2716 A right click (or other context menu command depending on platform) has been detected.
2723 @see wxCommandEvent, @ref overview_events
2725 class wxContextMenuEvent
: public wxCommandEvent
2731 wxContextMenuEvent(wxEventType id
= wxEVT_NULL
, int id
= 0,
2732 const wxPoint
& pos
= wxDefaultPosition
);
2735 Returns the position in screen coordinates at which the menu should be shown.
2736 Use wxWindow::ScreenToClient to convert to client coordinates.
2738 You can also omit a position from wxWindow::PopupMenu in order to use
2739 the current mouse pointer position.
2741 If the event originated from a keyboard event, the value returned from this
2742 function will be wxDefaultPosition.
2744 const wxPoint
& GetPosition() const;
2747 Sets the position at which the menu should be shown.
2749 void SetPosition(const wxPoint
& point
);
2757 An erase event is sent when a window's background needs to be repainted.
2759 On some platforms, such as GTK+, this event is simulated (simply generated just
2760 before the paint event) and may cause flicker. It is therefore recommended that
2761 you set the text background colour explicitly in order to prevent flicker.
2762 The default background colour under GTK+ is grey.
2764 To intercept this event, use the EVT_ERASE_BACKGROUND macro in an event table
2767 You must call wxEraseEvent::GetDC and use the returned device context if it is
2768 non-@NULL. If it is @NULL, create your own temporary wxClientDC object.
2771 Use the device context returned by GetDC to draw on, don't create
2772 a wxPaintDC in the event handler.
2774 @beginEventTable{wxEraseEvent}
2775 @event{EVT_ERASE_BACKGROUND(func)}
2776 Process a @c wxEVT_ERASE_BACKGROUND event.
2782 @see @ref overview_events
2784 class wxEraseEvent
: public wxEvent
2790 wxEraseEvent(int id
= 0, wxDC
* dc
= NULL
);
2793 Returns the device context associated with the erase event to draw on.
2795 wxDC
* GetDC() const;
2803 A focus event is sent when a window's focus changes. The window losing focus
2804 receives a "kill focus" event while the window gaining it gets a "set focus" one.
2806 Notice that the set focus event happens both when the user gives focus to the
2807 window (whether using the mouse or keyboard) and when it is done from the
2808 program itself using wxWindow::SetFocus.
2810 @beginEventTable{wxFocusEvent}
2811 @event{EVT_SET_FOCUS(func)}
2812 Process a @c wxEVT_SET_FOCUS event.
2813 @event{EVT_KILL_FOCUS(func)}
2814 Process a @c wxEVT_KILL_FOCUS event.
2820 @see @ref overview_events
2822 class wxFocusEvent
: public wxEvent
2828 wxFocusEvent(wxEventType eventType
= wxEVT_NULL
, int id
= 0);
2831 Returns the window associated with this event, that is the window which had the
2832 focus before for the @c wxEVT_SET_FOCUS event and the window which is
2833 going to receive focus for the @c wxEVT_KILL_FOCUS one.
2835 Warning: the window pointer may be @NULL!
2837 wxWindow
*GetWindow() const;
2843 @class wxChildFocusEvent
2845 A child focus event is sent to a (parent-)window when one of its child windows
2846 gains focus, so that the window could restore the focus back to its corresponding
2847 child if it loses it now and regains later.
2849 Notice that child window is the direct child of the window receiving event.
2850 Use wxWindow::FindFocus() to retreive the window which is actually getting focus.
2852 @beginEventTable{wxChildFocusEvent}
2853 @event{EVT_CHILD_FOCUS(func)}
2854 Process a @c wxEVT_CHILD_FOCUS event.
2860 @see @ref overview_events
2862 class wxChildFocusEvent
: public wxCommandEvent
2869 The direct child which is (or which contains the window which is) receiving
2872 wxChildFocusEvent(wxWindow
* win
= NULL
);
2875 Returns the direct child which receives the focus, or a (grand-)parent of the
2876 control receiving the focus.
2878 To get the actually focused control use wxWindow::FindFocus.
2880 wxWindow
*GetWindow() const;
2886 @class wxMouseCaptureLostEvent
2888 An mouse capture lost event is sent to a window that obtained mouse capture,
2889 which was subsequently loss due to "external" event, for example when a dialog
2890 box is shown or if another application captures the mouse.
2892 If this happens, this event is sent to all windows that are on capture stack
2893 (i.e. called CaptureMouse, but didn't call ReleaseMouse yet). The event is
2894 not sent if the capture changes because of a call to CaptureMouse or
2897 This event is currently emitted under Windows only.
2899 @beginEventTable{wxMouseCaptureLostEvent}
2900 @event{EVT_MOUSE_CAPTURE_LOST(func)}
2901 Process a @c wxEVT_MOUSE_CAPTURE_LOST event.
2909 @see wxMouseCaptureChangedEvent, @ref overview_events,
2910 wxWindow::CaptureMouse, wxWindow::ReleaseMouse, wxWindow::GetCapture
2912 class wxMouseCaptureLostEvent
: public wxEvent
2918 wxMouseCaptureLostEvent(wxWindowID windowId
= 0);
2924 @class wxNotifyEvent
2926 This class is not used by the event handlers by itself, but is a base class
2927 for other event classes (such as wxBookCtrlEvent).
2929 It (or an object of a derived class) is sent when the controls state is being
2930 changed and allows the program to wxNotifyEvent::Veto() this change if it wants
2931 to prevent it from happening.
2936 @see wxBookCtrlEvent
2938 class wxNotifyEvent
: public wxCommandEvent
2942 Constructor (used internally by wxWidgets only).
2944 wxNotifyEvent(wxEventType eventType
= wxEVT_NULL
, int id
= 0);
2947 This is the opposite of Veto(): it explicitly allows the event to be processed.
2948 For most events it is not necessary to call this method as the events are allowed
2949 anyhow but some are forbidden by default (this will be mentioned in the corresponding
2955 Returns @true if the change is allowed (Veto() hasn't been called) or @false
2956 otherwise (if it was).
2958 bool IsAllowed() const;
2961 Prevents the change announced by this event from happening.
2963 It is in general a good idea to notify the user about the reasons for vetoing
2964 the change because otherwise the applications behaviour (which just refuses to
2965 do what the user wants) might be quite surprising.
2972 @class wxThreadEvent
2974 This class adds some simple functionalities to wxCommandEvent coinceived
2975 for inter-threads communications.
2977 This event is not natively emitted by any control/class: this is just
2978 an helper class for the user.
2979 Its most important feature is the GetEventCategory() implementation which
2980 allows thread events to @b NOT be processed by wxEventLoopBase::YieldFor calls
2981 (unless the @c wxEVT_CATEGORY_THREAD is specified - which is never in wx code).
2984 @category{events,threading}
2986 @see @ref overview_thread, wxEventLoopBase::YieldFor
2988 class wxThreadEvent
: public wxCommandEvent
2994 wxThreadEvent(wxEventType eventType
= wxEVT_COMMAND_THREAD
, int id
= wxID_ANY
);
2997 Clones this event making sure that all internal members which use
2998 COW (only @c m_commandString for now; see @ref overview_refcount)
2999 are unshared (see wxObject::UnShare).
3001 virtual wxEvent
*Clone() const;
3004 Returns @c wxEVT_CATEGORY_THREAD.
3006 This is important to avoid unwanted processing of thread events
3007 when calling wxEventLoopBase::YieldFor().
3009 virtual wxEventCategory
GetEventCategory() const;
3012 Sets custom data payload.
3014 The @a payload argument may be of any type that wxAny can handle
3015 (i.e. pretty much anything). Note that T's copy constructor must be
3016 thread-safe, i.e. create a copy that doesn't share anything with
3017 the original (see Clone()).
3019 @note This method is not available with Visual C++ 6.
3023 @see GetPayload(), wxAny
3025 template<typename T
>
3026 void SetPayload(const T
& payload
);
3029 Get custom data payload.
3031 Correct type is checked in debug builds.
3033 @note This method is not available with Visual C++ 6.
3037 @see SetPayload(), wxAny
3039 template<typename T
>
3040 T
GetPayload() const;
3047 A help event is sent when the user has requested context-sensitive help.
3048 This can either be caused by the application requesting context-sensitive help mode
3049 via wxContextHelp, or (on MS Windows) by the system generating a WM_HELP message when
3050 the user pressed F1 or clicked on the query button in a dialog caption.
3052 A help event is sent to the window that the user clicked on, and is propagated
3053 up the window hierarchy until the event is processed or there are no more event
3056 The application should call wxEvent::GetId to check the identity of the
3057 clicked-on window, and then either show some suitable help or call wxEvent::Skip()
3058 if the identifier is unrecognised.
3060 Calling Skip is important because it allows wxWidgets to generate further
3061 events for ancestors of the clicked-on window. Otherwise it would be impossible to
3062 show help for container windows, since processing would stop after the first window
3065 @beginEventTable{wxHelpEvent}
3066 @event{EVT_HELP(id, func)}
3067 Process a @c wxEVT_HELP event.
3068 @event{EVT_HELP_RANGE(id1, id2, func)}
3069 Process a @c wxEVT_HELP event for a range of ids.
3075 @see wxContextHelp, wxDialog, @ref overview_events
3077 class wxHelpEvent
: public wxCommandEvent
3081 Indicates how a wxHelpEvent was generated.
3085 Origin_Unknown
, /**< unrecognized event source. */
3086 Origin_Keyboard
, /**< event generated from F1 key press. */
3088 /** event generated by wxContextHelp or from the [?] button on
3089 the title bar (Windows). */
3096 wxHelpEvent(wxEventType type
= wxEVT_NULL
,
3097 wxWindowID winid
= 0,
3098 const wxPoint
& pt
= wxDefaultPosition
,
3099 wxHelpEvent::Origin origin
= Origin_Unknown
);
3102 Returns the origin of the help event which is one of the ::wxHelpEventOrigin
3105 The application may handle events generated using the keyboard or mouse
3106 differently, e.g. by using wxGetMousePosition() for the mouse events.
3110 wxHelpEvent::Origin
GetOrigin() const;
3113 Returns the left-click position of the mouse, in screen coordinates.
3114 This allows the application to position the help appropriately.
3116 const wxPoint
& GetPosition() const;
3119 Set the help event origin, only used internally by wxWidgets normally.
3123 void SetOrigin(wxHelpEvent::Origin origin
);
3126 Sets the left-click position of the mouse, in screen coordinates.
3128 void SetPosition(const wxPoint
& pt
);
3134 @class wxScrollEvent
3136 A scroll event holds information about events sent from stand-alone
3137 scrollbars (see wxScrollBar) and sliders (see wxSlider).
3139 Note that scrolled windows send the wxScrollWinEvent which does not derive from
3140 wxCommandEvent, but from wxEvent directly - don't confuse these two kinds of
3141 events and use the event table macros mentioned below only for the scrollbar-like
3144 @section scrollevent_diff The difference between EVT_SCROLL_THUMBRELEASE and EVT_SCROLL_CHANGED
3146 The EVT_SCROLL_THUMBRELEASE event is only emitted when actually dragging the thumb
3147 using the mouse and releasing it (This EVT_SCROLL_THUMBRELEASE event is also followed
3148 by an EVT_SCROLL_CHANGED event).
3150 The EVT_SCROLL_CHANGED event also occurs when using the keyboard to change the thumb
3151 position, and when clicking next to the thumb (In all these cases the EVT_SCROLL_THUMBRELEASE
3152 event does not happen).
3154 In short, the EVT_SCROLL_CHANGED event is triggered when scrolling/ moving has finished
3155 independently of the way it had started. Please see the widgets sample ("Slider" page)
3156 to see the difference between EVT_SCROLL_THUMBRELEASE and EVT_SCROLL_CHANGED in action.
3159 Note that unless specifying a scroll control identifier, you will need to test for scrollbar
3160 orientation with wxScrollEvent::GetOrientation, since horizontal and vertical scroll events
3161 are processed using the same event handler.
3163 @beginEventTable{wxScrollEvent}
3164 You can use EVT_COMMAND_SCROLL... macros with window IDs for when intercepting
3165 scroll events from controls, or EVT_SCROLL... macros without window IDs for
3166 intercepting scroll events from the receiving window -- except for this, the
3167 macros behave exactly the same.
3168 @event{EVT_SCROLL(func)}
3169 Process all scroll events.
3170 @event{EVT_SCROLL_TOP(func)}
3171 Process wxEVT_SCROLL_TOP scroll-to-top events (minimum position).
3172 @event{EVT_SCROLL_BOTTOM(func)}
3173 Process wxEVT_SCROLL_BOTTOM scroll-to-bottom events (maximum position).
3174 @event{EVT_SCROLL_LINEUP(func)}
3175 Process wxEVT_SCROLL_LINEUP line up events.
3176 @event{EVT_SCROLL_LINEDOWN(func)}
3177 Process wxEVT_SCROLL_LINEDOWN line down events.
3178 @event{EVT_SCROLL_PAGEUP(func)}
3179 Process wxEVT_SCROLL_PAGEUP page up events.
3180 @event{EVT_SCROLL_PAGEDOWN(func)}
3181 Process wxEVT_SCROLL_PAGEDOWN page down events.
3182 @event{EVT_SCROLL_THUMBTRACK(func)}
3183 Process wxEVT_SCROLL_THUMBTRACK thumbtrack events (frequent events sent as the
3184 user drags the thumbtrack).
3185 @event{EVT_SCROLL_THUMBRELEASE(func)}
3186 Process wxEVT_SCROLL_THUMBRELEASE thumb release events.
3187 @event{EVT_SCROLL_CHANGED(func)}
3188 Process wxEVT_SCROLL_CHANGED end of scrolling events (MSW only).
3189 @event{EVT_COMMAND_SCROLL(id, func)}
3190 Process all scroll events.
3191 @event{EVT_COMMAND_SCROLL_TOP(id, func)}
3192 Process wxEVT_SCROLL_TOP scroll-to-top events (minimum position).
3193 @event{EVT_COMMAND_SCROLL_BOTTOM(id, func)}
3194 Process wxEVT_SCROLL_BOTTOM scroll-to-bottom events (maximum position).
3195 @event{EVT_COMMAND_SCROLL_LINEUP(id, func)}
3196 Process wxEVT_SCROLL_LINEUP line up events.
3197 @event{EVT_COMMAND_SCROLL_LINEDOWN(id, func)}
3198 Process wxEVT_SCROLL_LINEDOWN line down events.
3199 @event{EVT_COMMAND_SCROLL_PAGEUP(id, func)}
3200 Process wxEVT_SCROLL_PAGEUP page up events.
3201 @event{EVT_COMMAND_SCROLL_PAGEDOWN(id, func)}
3202 Process wxEVT_SCROLL_PAGEDOWN page down events.
3203 @event{EVT_COMMAND_SCROLL_THUMBTRACK(id, func)}
3204 Process wxEVT_SCROLL_THUMBTRACK thumbtrack events (frequent events sent
3205 as the user drags the thumbtrack).
3206 @event{EVT_COMMAND_SCROLL_THUMBRELEASE(func)}
3207 Process wxEVT_SCROLL_THUMBRELEASE thumb release events.
3208 @event{EVT_COMMAND_SCROLL_CHANGED(func)}
3209 Process wxEVT_SCROLL_CHANGED end of scrolling events (MSW only).
3215 @see wxScrollBar, wxSlider, wxSpinButton, wxScrollWinEvent, @ref overview_events
3217 class wxScrollEvent
: public wxCommandEvent
3223 wxScrollEvent(wxEventType commandType
= wxEVT_NULL
, int id
= 0, int pos
= 0,
3224 int orientation
= 0);
3227 Returns wxHORIZONTAL or wxVERTICAL, depending on the orientation of the
3230 int GetOrientation() const;
3233 Returns the position of the scrollbar.
3235 int GetPosition() const;
3239 See wxIdleEvent::SetMode() for more info.
3243 /** Send idle events to all windows */
3246 /** Send idle events to windows that have the wxWS_EX_PROCESS_IDLE flag specified */
3247 wxIDLE_PROCESS_SPECIFIED
3254 This class is used for idle events, which are generated when the system becomes
3255 idle. Note that, unless you do something specifically, the idle events are not
3256 sent if the system remains idle once it has become it, e.g. only a single idle
3257 event will be generated until something else resulting in more normal events
3258 happens and only then is the next idle event sent again.
3260 If you need to ensure a continuous stream of idle events, you can either use
3261 wxIdleEvent::RequestMore method in your handler or call wxWakeUpIdle() periodically
3262 (for example from a timer event handler), but note that both of these approaches
3263 (and especially the first one) increase the system load and so should be avoided
3266 By default, idle events are sent to all windows (and also wxApp, as usual).
3267 If this is causing a significant overhead in your application, you can call
3268 wxIdleEvent::SetMode with the value wxIDLE_PROCESS_SPECIFIED, and set the
3269 wxWS_EX_PROCESS_IDLE extra window style for every window which should receive
3272 @beginEventTable{wxIdleEvent}
3273 @event{EVT_IDLE(func)}
3274 Process a @c wxEVT_IDLE event.
3280 @see @ref overview_events, wxUpdateUIEvent, wxWindow::OnInternalIdle
3282 class wxIdleEvent
: public wxEvent
3291 Returns @true if it is appropriate to send idle events to this window.
3293 This function looks at the mode used (see wxIdleEvent::SetMode),
3294 and the wxWS_EX_PROCESS_IDLE style in @a window to determine whether idle
3295 events should be sent to this window now.
3297 By default this will always return @true because the update mode is initially
3298 wxIDLE_PROCESS_ALL. You can change the mode to only send idle events to
3299 windows with the wxWS_EX_PROCESS_IDLE extra window style set.
3303 static bool CanSend(wxWindow
* window
);
3306 Static function returning a value specifying how wxWidgets will send idle
3307 events: to all windows, or only to those which specify that they
3308 will process the events.
3312 static wxIdleMode
GetMode();
3315 Returns @true if the OnIdle function processing this event requested more
3320 bool MoreRequested() const;
3323 Tells wxWidgets that more processing is required.
3325 This function can be called by an OnIdle handler for a window or window event
3326 handler to indicate that wxApp::OnIdle should forward the OnIdle event once
3327 more to the application windows.
3329 If no window calls this function during OnIdle, then the application will
3330 remain in a passive event loop (not calling OnIdle) until a new event is
3331 posted to the application by the windowing system.
3333 @see MoreRequested()
3335 void RequestMore(bool needMore
= true);
3338 Static function for specifying how wxWidgets will send idle events: to
3339 all windows, or only to those which specify that they will process the events.
3342 Can be one of the ::wxIdleMode values.
3343 The default is wxIDLE_PROCESS_ALL.
3345 static void SetMode(wxIdleMode mode
);
3351 @class wxInitDialogEvent
3353 A wxInitDialogEvent is sent as a dialog or panel is being initialised.
3354 Handlers for this event can transfer data to the window.
3356 The default handler calls wxWindow::TransferDataToWindow.
3358 @beginEventTable{wxInitDialogEvent}
3359 @event{EVT_INIT_DIALOG(func)}
3360 Process a @c wxEVT_INIT_DIALOG event.
3366 @see @ref overview_events
3368 class wxInitDialogEvent
: public wxEvent
3374 wxInitDialogEvent(int id
= 0);
3380 @class wxWindowDestroyEvent
3382 This event is sent as early as possible during the window destruction
3385 For the top level windows, as early as possible means that this is done by
3386 wxFrame or wxDialog destructor, i.e. after the destructor of the derived
3387 class was executed and so any methods specific to the derived class can't
3388 be called any more from this event handler. If you need to do this, you
3389 must call wxWindow::SendDestroyEvent() from your derived class destructor.
3391 For the child windows, this event is generated just before deleting the
3392 window from wxWindow::Destroy() (which is also called when the parent
3393 window is deleted) or from the window destructor if operator @c delete was
3394 used directly (which is not recommended for this very reason).
3396 It is usually pointless to handle this event in the window itself but it ca
3397 be very useful to receive notifications about the window destruction in the
3398 parent window or in any other object interested in this window.
3403 @see @ref overview_events, wxWindowCreateEvent
3405 class wxWindowDestroyEvent
: public wxCommandEvent
3411 wxWindowDestroyEvent(wxWindow
* win
= NULL
);
3413 /// Retutn the window being destroyed.
3414 wxWindow
*GetWindow() const;
3419 @class wxNavigationKeyEvent
3421 This event class contains information about navigation events,
3422 generated by navigation keys such as tab and page down.
3424 This event is mainly used by wxWidgets implementations.
3425 A wxNavigationKeyEvent handler is automatically provided by wxWidgets
3426 when you make a class into a control container with the macro
3427 WX_DECLARE_CONTROL_CONTAINER.
3429 @beginEventTable{wxNavigationKeyEvent}
3430 @event{EVT_NAVIGATION_KEY(func)}
3431 Process a navigation key event.
3437 @see wxWindow::Navigate, wxWindow::NavigateIn
3439 class wxNavigationKeyEvent
: public wxEvent
3443 Flags which can be used with wxNavigationKeyEvent.
3445 enum wxNavigationKeyEventFlags
3447 IsBackward
= 0x0000,
3453 wxNavigationKeyEvent();
3454 wxNavigationKeyEvent(const wxNavigationKeyEvent
& event
);
3457 Returns the child that has the focus, or @NULL.
3459 wxWindow
* GetCurrentFocus() const;
3462 Returns @true if the navigation was in the forward direction.
3464 bool GetDirection() const;
3467 Returns @true if the navigation event was from a tab key.
3468 This is required for proper navigation over radio buttons.
3470 bool IsFromTab() const;
3473 Returns @true if the navigation event represents a window change
3474 (for example, from Ctrl-Page Down in a notebook).
3476 bool IsWindowChange() const;
3479 Sets the current focus window member.
3481 void SetCurrentFocus(wxWindow
* currentFocus
);
3484 Sets the direction to forward if @a direction is @true, or backward
3487 void SetDirection(bool direction
);
3490 Sets the flags for this event.
3491 The @a flags can be a combination of the ::wxNavigationKeyEventFlags values.
3493 void SetFlags(long flags
);
3496 Marks the navigation event as from a tab key.
3498 void SetFromTab(bool fromTab
);
3501 Marks the event as a window change event.
3503 void SetWindowChange(bool windowChange
);
3509 @class wxMouseCaptureChangedEvent
3511 An mouse capture changed event is sent to a window that loses its
3512 mouse capture. This is called even if wxWindow::ReleaseMouse
3513 was called by the application code. Handling this event allows
3514 an application to cater for unexpected capture releases which
3515 might otherwise confuse mouse handling code.
3519 @beginEventTable{wxMouseCaptureChangedEvent}
3520 @event{EVT_MOUSE_CAPTURE_CHANGED(func)}
3521 Process a @c wxEVT_MOUSE_CAPTURE_CHANGED event.
3527 @see wxMouseCaptureLostEvent, @ref overview_events,
3528 wxWindow::CaptureMouse, wxWindow::ReleaseMouse, wxWindow::GetCapture
3530 class wxMouseCaptureChangedEvent
: public wxEvent
3536 wxMouseCaptureChangedEvent(wxWindowID windowId
= 0,
3537 wxWindow
* gainedCapture
= NULL
);
3540 Returns the window that gained the capture, or @NULL if it was a
3541 non-wxWidgets window.
3543 wxWindow
* GetCapturedWindow() const;
3551 This event class contains information about window and session close events.
3553 The handler function for EVT_CLOSE is called when the user has tried to close a
3554 a frame or dialog box using the window manager (X) or system menu (Windows).
3555 It can also be invoked by the application itself programmatically, for example by
3556 calling the wxWindow::Close function.
3558 You should check whether the application is forcing the deletion of the window
3559 using wxCloseEvent::CanVeto. If this is @false, you @e must destroy the window
3560 using wxWindow::Destroy.
3562 If the return value is @true, it is up to you whether you respond by destroying
3565 If you don't destroy the window, you should call wxCloseEvent::Veto to
3566 let the calling code know that you did not destroy the window.
3567 This allows the wxWindow::Close function to return @true or @false depending
3568 on whether the close instruction was honoured or not.
3570 Example of a wxCloseEvent handler:
3573 void MyFrame::OnClose(wxCloseEvent& event)
3575 if ( event.CanVeto() && m_bFileNotSaved )
3577 if ( wxMessageBox("The file has not been saved... continue closing?",
3579 wxICON_QUESTION | wxYES_NO) != wxYES )
3586 Destroy(); // you may also do: event.Skip();
3587 // since the default event handler does call Destroy(), too
3591 The EVT_END_SESSION event is slightly different as it is sent by the system
3592 when the user session is ending (e.g. because of log out or shutdown) and
3593 so all windows are being forcefully closed. At least under MSW, after the
3594 handler for this event is executed the program is simply killed by the
3595 system. Because of this, the default handler for this event provided by
3596 wxWidgets calls all the usual cleanup code (including wxApp::OnExit()) so
3597 that it could still be executed and exit()s the process itself, without
3598 waiting for being killed. If this behaviour is for some reason undesirable,
3599 make sure that you define a handler for this event in your wxApp-derived
3600 class and do not call @c event.Skip() in it (but be aware that the system
3601 will still kill your application).
3603 @beginEventTable{wxCloseEvent}
3604 @event{EVT_CLOSE(func)}
3605 Process a @c wxEVT_CLOSE_WINDOW command event, supplying the member function.
3606 This event applies to wxFrame and wxDialog classes.
3607 @event{EVT_QUERY_END_SESSION(func)}
3608 Process a @c wxEVT_QUERY_END_SESSION session event, supplying the member function.
3609 This event can be handled in wxApp-derived class only.
3610 @event{EVT_END_SESSION(func)}
3611 Process a @c wxEVT_END_SESSION session event, supplying the member function.
3612 This event can be handled in wxApp-derived class only.
3618 @see wxWindow::Close, @ref overview_windowdeletion
3620 class wxCloseEvent
: public wxEvent
3626 wxCloseEvent(wxEventType commandEventType
= wxEVT_NULL
, int id
= 0);
3629 Returns @true if you can veto a system shutdown or a window close event.
3630 Vetoing a window close event is not possible if the calling code wishes to
3631 force the application to exit, and so this function must be called to check this.
3633 bool CanVeto() const;
3636 Returns @true if the user is just logging off or @false if the system is
3637 shutting down. This method can only be called for end session and query end
3638 session events, it doesn't make sense for close window event.
3640 bool GetLoggingOff() const;
3643 Sets the 'can veto' flag.
3645 void SetCanVeto(bool canVeto
);
3648 Sets the 'logging off' flag.
3650 void SetLoggingOff(bool loggingOff
);
3653 Call this from your event handler to veto a system shutdown or to signal
3654 to the calling application that a window close did not happen.
3656 You can only veto a shutdown if CanVeto() returns @true.
3658 void Veto(bool veto
= true);
3666 This class is used for a variety of menu-related events. Note that
3667 these do not include menu command events, which are
3668 handled using wxCommandEvent objects.
3670 The default handler for @c wxEVT_MENU_HIGHLIGHT displays help
3671 text in the first field of the status bar.
3673 @beginEventTable{wxMenuEvent}
3674 @event{EVT_MENU_OPEN(func)}
3675 A menu is about to be opened. On Windows, this is only sent once for each
3676 navigation of the menubar (up until all menus have closed).
3677 @event{EVT_MENU_CLOSE(func)}
3678 A menu has been just closed.
3679 @event{EVT_MENU_HIGHLIGHT(id, func)}
3680 The menu item with the specified id has been highlighted: used to show
3681 help prompts in the status bar by wxFrame
3682 @event{EVT_MENU_HIGHLIGHT_ALL(func)}
3683 A menu item has been highlighted, i.e. the currently selected menu item has changed.
3689 @see wxCommandEvent, @ref overview_events
3691 class wxMenuEvent
: public wxEvent
3697 wxMenuEvent(wxEventType id
= wxEVT_NULL
, int id
= 0, wxMenu
* menu
= NULL
);
3700 Returns the menu which is being opened or closed. This method should only be
3701 used with the @c OPEN and @c CLOSE events and even for them the
3702 returned pointer may be @NULL in some ports.
3704 wxMenu
* GetMenu() const;
3707 Returns the menu identifier associated with the event.
3708 This method should be only used with the @c HIGHLIGHT events.
3710 int GetMenuId() const;
3713 Returns @true if the menu which is being opened or closed is a popup menu,
3714 @false if it is a normal one.
3716 This method should only be used with the @c OPEN and @c CLOSE events.
3718 bool IsPopup() const;
3724 An event being sent when the window is shown or hidden.
3725 The event is triggered by calls to wxWindow::Show(), and any user
3726 action showing a previously hidden window or vice versa (if allowed by
3727 the current platform and/or window manager).
3728 Notice that the event is not triggered when the application is iconized
3729 (minimized) or restored under wxMSW.
3731 Currently only wxMSW, wxGTK and wxOS2 generate such events.
3733 @onlyfor{wxmsw,wxgtk,wxos2}
3735 @beginEventTable{wxShowEvent}
3736 @event{EVT_SHOW(func)}
3737 Process a @c wxEVT_SHOW event.
3743 @see @ref overview_events, wxWindow::Show,
3747 class wxShowEvent
: public wxEvent
3753 wxShowEvent(int winid
= 0, bool show
= false);
3756 Set whether the windows was shown or hidden.
3758 void SetShow(bool show
);
3761 Return @true if the window has been shown, @false if it has been
3764 bool IsShown() const;
3767 @deprecated This function is deprecated in favour of IsShown().
3769 bool GetShow() const;
3775 @class wxIconizeEvent
3777 An event being sent when the frame is iconized (minimized) or restored.
3779 Currently only wxMSW and wxGTK generate such events.
3781 @onlyfor{wxmsw,wxgtk}
3783 @beginEventTable{wxIconizeEvent}
3784 @event{EVT_ICONIZE(func)}
3785 Process a @c wxEVT_ICONIZE event.
3791 @see @ref overview_events, wxTopLevelWindow::Iconize,
3792 wxTopLevelWindow::IsIconized
3794 class wxIconizeEvent
: public wxEvent
3800 wxIconizeEvent(int id
= 0, bool iconized
= true);
3803 Returns @true if the frame has been iconized, @false if it has been
3806 bool IsIconized() const;
3809 @deprecated This function is deprecated in favour of IsIconized().
3811 bool Iconized() const;
3819 A move event holds information about wxTopLevelWindow move change events.
3821 @beginEventTable{wxMoveEvent}
3822 @event{EVT_MOVE(func)}
3823 Process a @c wxEVT_MOVE event, which is generated when a window is moved.
3824 @event{EVT_MOVE_START(func)}
3825 Process a @c wxEVT_MOVE_START event, which is generated when the user starts
3826 to move or size a window. wxMSW only.
3827 @event{EVT_MOVE_END(func)}
3828 Process a @c wxEVT_MOVE_END event, which is generated when the user stops
3829 moving or sizing a window. wxMSW only.
3835 @see wxPoint, @ref overview_events
3837 class wxMoveEvent
: public wxEvent
3843 wxMoveEvent(const wxPoint
& pt
, int id
= 0);
3846 Returns the position of the window generating the move change event.
3848 wxPoint
GetPosition() const;
3855 A size event holds information about size change events of wxWindow.
3857 The EVT_SIZE handler function will be called when the window has been resized.
3859 You may wish to use this for frames to resize their child windows as appropriate.
3861 Note that the size passed is of the whole window: call wxWindow::GetClientSize()
3862 for the area which may be used by the application.
3864 When a window is resized, usually only a small part of the window is damaged
3865 and you may only need to repaint that area. However, if your drawing depends on the
3866 size of the window, you may need to clear the DC explicitly and repaint the whole window.
3867 In which case, you may need to call wxWindow::Refresh to invalidate the entire window.
3869 @beginEventTable{wxSizeEvent}
3870 @event{EVT_SIZE(func)}
3871 Process a @c wxEVT_SIZE event.
3877 @see wxSize, @ref overview_events
3879 class wxSizeEvent
: public wxEvent
3885 wxSizeEvent(const wxSize
& sz
, int id
= 0);
3888 Returns the entire size of the window generating the size change event.
3890 This is the new total size of the window, i.e. the same size as would
3891 be returned by wxWindow::GetSize() if it were called now. Use
3892 wxWindow::GetClientSize() if you catch this event in a top level window
3893 such as wxFrame to find the size available for the window contents.
3895 wxSize
GetSize() const;
3901 @class wxSetCursorEvent
3903 A wxSetCursorEvent is generated from wxWindow when the mouse cursor is about
3904 to be set as a result of mouse motion.
3906 This event gives the application the chance to perform specific mouse cursor
3907 processing based on the current position of the mouse within the window.
3908 Use wxSetCursorEvent::SetCursor to specify the cursor you want to be displayed.
3910 @beginEventTable{wxSetCursorEvent}
3911 @event{EVT_SET_CURSOR(func)}
3912 Process a @c wxEVT_SET_CURSOR event.
3918 @see ::wxSetCursor, wxWindow::wxSetCursor
3920 class wxSetCursorEvent
: public wxEvent
3924 Constructor, used by the library itself internally to initialize the event
3927 wxSetCursorEvent(wxCoord x
= 0, wxCoord y
= 0);
3930 Returns a reference to the cursor specified by this event.
3932 const wxCursor
& GetCursor() const;
3935 Returns the X coordinate of the mouse in client coordinates.
3937 wxCoord
GetX() const;
3940 Returns the Y coordinate of the mouse in client coordinates.
3942 wxCoord
GetY() const;
3945 Returns @true if the cursor specified by this event is a valid cursor.
3947 @remarks You cannot specify wxNullCursor with this event, as it is not
3948 considered a valid cursor.
3950 bool HasCursor() const;
3953 Sets the cursor associated with this event.
3955 void SetCursor(const wxCursor
& cursor
);
3960 // ============================================================================
3961 // Global functions/macros
3962 // ============================================================================
3964 /** @addtogroup group_funcmacro_events */
3968 A value uniquely identifying the type of the event.
3970 The values of this type should only be created using wxNewEventType().
3972 See the macro DEFINE_EVENT_TYPE() for more info.
3974 @see @ref overview_events_introduction
3976 typedef int wxEventType
;
3979 A special event type usually used to indicate that some wxEvent has yet
3982 wxEventType wxEVT_NULL
;
3985 Generates a new unique event type.
3987 Usually this function is only used by wxDEFINE_EVENT() and not called
3990 wxEventType
wxNewEventType();
3993 Define a new event type associated with the specified event class.
3995 This macro defines a new unique event type @a name associated with the
4000 wxDEFINE_EVENT(MY_COMMAND_EVENT, wxCommandEvent);
4002 class MyCustomEvent : public wxEvent { ... };
4003 wxDEFINE_EVENT(MY_CUSTOM_EVENT, MyCustomEvent);
4006 @see wxDECLARE_EVENT(), @ref overview_events_custom
4008 #define wxDEFINE_EVENT(name, cls) \
4009 const wxEventTypeTag< cls > name(wxNewEventType())
4012 Declares a custom event type.
4014 This macro declares a variable called @a name which must be defined
4015 elsewhere using wxDEFINE_EVENT().
4017 The class @a cls must be the wxEvent-derived class associated with the
4018 events of this type and its full declaration must be visible from the point
4019 of use of this macro.
4023 wxDECLARE_EVENT(MY_COMMAND_EVENT, wxCommandEvent);
4025 class MyCustomEvent : public wxEvent { ... };
4026 wxDECLARE_EVENT(MY_CUSTOM_EVENT, MyCustomEvent);
4029 #define wxDECLARE_EVENT(name, cls) \
4030 wxDECLARE_EXPORTED_EVENT(wxEMPTY_PARAMETER_VALUE, name, cls)
4033 Variant of wxDECLARE_EVENT() used for event types defined inside a shared
4036 This is mostly used by wxWidgets internally, e.g.
4038 wxDECLARE_EXPORTED_EVENT(WXDLLIMPEXP_CORE, wxEVT_COMMAND_BUTTON_CLICKED, wxCommandEvent)
4041 #define wxDECLARE_EXPORTED_EVENT( expdecl, name, cls ) \
4042 extern const expdecl wxEventTypeTag< cls > name;
4045 Helper macro for definition of custom event table macros.
4047 This macro must only be used if wxEVENTS_COMPATIBILITY_2_8 is 1, otherwise
4048 it is better and more clear to just use the address of the function
4049 directly as this is all this macro does in this case. However it needs to
4050 explicitly cast @a func to @a functype, which is the type of wxEvtHandler
4051 member function taking the custom event argument when
4052 wxEVENTS_COMPATIBILITY_2_8 is 0.
4054 See wx__DECLARE_EVT0 for an example of use.
4056 @see @ref overview_events_custom_ownclass
4058 #define wxEVENT_HANDLER_CAST(functype, func) (&func)
4061 This macro is used to define event table macros for handling custom
4066 class MyEvent : public wxEvent { ... };
4068 // note that this is not necessary unless using old compilers: for the
4069 // reasonably new ones just use &func instead of MyEventHandler(func)
4070 typedef void (wxEvtHandler::*MyEventFunction)(MyEvent&);
4071 #define MyEventHandler(func) wxEVENT_HANDLER_CAST(MyEventFunction, func)
4073 wxDEFINE_EVENT(MY_EVENT_TYPE, MyEvent);
4075 #define EVT_MY(id, func) \
4076 wx__DECLARE_EVT1(MY_EVENT_TYPE, id, MyEventHandler(func))
4080 wxBEGIN_EVENT_TABLE(MyFrame, wxFrame)
4081 EVT_MY(wxID_ANY, MyFrame::OnMyEvent)
4086 The event type to handle.
4088 The identifier of events to handle.
4090 The event handler method.
4092 #define wx__DECLARE_EVT1(evt, id, fn) \
4093 wx__DECLARE_EVT2(evt, id, wxID_ANY, fn)
4096 Generalized version of the wx__DECLARE_EVT1() macro taking a range of
4097 IDs instead of a single one.
4098 Argument @a id1 is the first identifier of the range, @a id2 is the
4099 second identifier of the range.
4101 #define wx__DECLARE_EVT2(evt, id1, id2, fn) \
4102 DECLARE_EVENT_TABLE_ENTRY(evt, id1, id2, fn, NULL),
4105 Simplified version of the wx__DECLARE_EVT1() macro, to be used when the
4106 event type must be handled regardless of the ID associated with the
4107 specific event instances.
4109 #define wx__DECLARE_EVT0(evt, fn) \
4110 wx__DECLARE_EVT1(evt, wxID_ANY, fn)
4113 Use this macro inside a class declaration to declare a @e static event table
4116 In the implementation file you'll need to use the wxBEGIN_EVENT_TABLE()
4117 and the wxEND_EVENT_TABLE() macros, plus some additional @c EVT_xxx macro
4120 Note that this macro requires a final semicolon.
4122 @see @ref overview_events_eventtables
4124 #define wxDECLARE_EVENT_TABLE()
4127 Use this macro in a source file to start listing @e static event handlers
4128 for a specific class.
4130 Use wxEND_EVENT_TABLE() to terminate the event-declaration block.
4132 @see @ref overview_events_eventtables
4134 #define wxBEGIN_EVENT_TABLE(theClass, baseClass)
4137 Use this macro in a source file to end listing @e static event handlers
4138 for a specific class.
4140 Use wxBEGIN_EVENT_TABLE() to start the event-declaration block.
4142 @see @ref overview_events_eventtables
4144 #define wxEND_EVENT_TABLE()
4147 In a GUI application, this function posts @a event to the specified @e dest
4148 object using wxEvtHandler::AddPendingEvent().
4150 Otherwise, it dispatches @a event immediately using
4151 wxEvtHandler::ProcessEvent(). See the respective documentation for details
4152 (and caveats). Because of limitation of wxEvtHandler::AddPendingEvent()
4153 this function is not thread-safe for event objects having wxString fields,
4154 use wxQueueEvent() instead.
4158 void wxPostEvent(wxEvtHandler
* dest
, const wxEvent
& event
);
4161 Queue an event for processing on the given object.
4163 This is a wrapper around wxEvtHandler::QueueEvent(), see its documentation
4169 The object to queue the event on, can't be @c NULL.
4171 The heap-allocated and non-@c NULL event to queue, the function takes
4174 void wxQueueEvent(wxEvtHandler
* dest
, wxEvent
*event
);