1 /////////////////////////////////////////////////////////////////////////////
3 // Purpose: interface of wxEvtHandler, wxEventBlocker and many
4 // wxEvent-derived classes
5 // Author: wxWidgets team
7 // Licence: wxWindows license
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
338 class wxEvtHandler
: public wxObject
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 An instance where you might actually override the ProcessEvent() function is where
457 you want to direct event processing to event handlers not normally noticed by
458 wxWidgets. For example, in the document/view architecture, documents and views
459 are potential event handlers. When an event reaches a frame, ProcessEvent() will
460 need to be called on the associated document and view in case event handler functions
461 are associated with these objects. The property classes library (wxProperty) also
462 overrides ProcessEvent() for similar reasons.
464 The normal order of event table searching is as follows:
465 -# If the object is disabled (via a call to wxEvtHandler::SetEvtHandlerEnabled)
466 the function skips to step (6).
467 -# If the object is a wxWindow, ProcessEvent() is recursively called on the
468 window's wxValidator. If this returns @true, the function exits.
469 -# SearchEventTable() is called for this event handler. If this fails, the base
470 class table is tried, and so on until no more tables exist or an appropriate
471 function was found, in which case the function exits.
472 -# The search is applied down the entire chain of event handlers (usually the
473 chain has a length of one). This chain can be formed using wxEvtHandler::SetNextHandler():
474 @image html overview_events_chain.png
475 (referring to the image, if @c A->ProcessEvent is called and it doesn't handle
476 the event, @c B->ProcessEvent will be called and so on...).
477 Note that in the case of wxWindow you can build a stack of event handlers
478 (see wxWindow::PushEventHandler() for more info).
479 If any of the handlers of the chain return @true, the function exits.
480 -# If the object is a wxWindow and the event is a wxCommandEvent, ProcessEvent()
481 is recursively applied to the parent window's event handler.
482 If this returns @true, the function exits.
483 -# Finally, ProcessEvent() is called on the wxApp object.
488 @return @true if a suitable event handler function was found and
489 executed, and the function did not call wxEvent::Skip.
491 @see SearchEventTable()
493 virtual bool ProcessEvent(wxEvent
& event
);
496 Processes an event by calling ProcessEvent() and handles any exceptions
497 that occur in the process.
498 If an exception is thrown in event handler, wxApp::OnExceptionInMainLoop is called.
503 @return @true if the event was processed, @false if no handler was found
504 or an exception was thrown.
506 @see wxWindow::HandleWindowEvent
508 bool SafelyProcessEvent(wxEvent
& event
);
511 Searches the event table, executing an event handler function if an appropriate
515 Event table to be searched.
517 Event to be matched against an event table entry.
519 @return @true if a suitable event handler function was found and
520 executed, and the function did not call wxEvent::Skip.
522 @remarks This function looks through the object's event table and tries
523 to find an entry that will match the event.
524 An entry will match if:
525 @li The event type matches, and
526 @li the identifier or identifier range matches, or the event table
527 entry's identifier is zero.
529 If a suitable function is called but calls wxEvent::Skip, this
530 function will fail, and searching will continue.
534 virtual bool SearchEventTable(wxEventTable
& table
,
541 @name Connecting and disconnecting
546 Connects the given function dynamically with the event handler, id and
549 This is an alternative to the use of static event tables. It is more
550 flexible as it allows to connect events generated by some object to an
551 event handler defined in a different object of a different class (which
552 is impossible to do directly with the event tables -- the events can be
553 only handled in another object if they are propagated upwards to it).
554 Do make sure to specify the correct @a eventSink when connecting to an
555 event of a different object.
557 See @ref overview_events_connect for more detailed explanation
558 of this function and the @ref page_samples_event sample for usage
561 This specific overload allows you to connect an event handler to a @e range
563 Do not confuse @e source IDs with event @e types: source IDs identify the
564 event generator objects (typically wxMenuItem or wxWindow objects) while the
565 event @e type identify which type of events should be handled by the
566 given @e function (an event generator object may generate many different
570 The first ID of the identifier range to be associated with the event
573 The last ID of the identifier range to be associated with the event
576 The event type to be associated with this event handler.
578 The event handler function. Note that this function should
579 be explicitly converted to the correct type which can be done using a macro
580 called @c wxFooEventHandler for the handler for any @c wxFooEvent.
582 Data to be associated with the event table entry.
584 Object whose member function should be called. It must be specified
585 when connecting an event generated by one object to a member
586 function of a different object. If it is omitted, @c this is used.
588 void Connect(int id
, int lastId
, wxEventType eventType
,
589 wxObjectEventFunction function
,
590 wxObject
* userData
= NULL
,
591 wxEvtHandler
* eventSink
= NULL
);
594 See the Connect(int, int, wxEventType, wxObjectEventFunction, wxObject*, wxEvtHandler*)
595 overload for more info.
597 This overload can be used to attach an event handler to a single source ID:
601 frame->Connect( wxID_EXIT,
602 wxEVT_COMMAND_MENU_SELECTED,
603 wxCommandEventHandler(MyFrame::OnQuit) );
606 void Connect(int id
, wxEventType eventType
,
607 wxObjectEventFunction function
,
608 wxObject
* userData
= NULL
,
609 wxEvtHandler
* eventSink
= NULL
);
612 See the Connect(int, int, wxEventType, wxObjectEventFunction, wxObject*, wxEvtHandler*)
613 overload for more info.
615 This overload will connect the given event handler so that regardless of the
616 ID of the event source, the handler will be called.
618 void Connect(wxEventType eventType
,
619 wxObjectEventFunction function
,
620 wxObject
* userData
= NULL
,
621 wxEvtHandler
* eventSink
= NULL
);
624 Disconnects the given function dynamically from the event handler, using the
625 specified parameters as search criteria and returning @true if a matching
626 function has been found and removed.
628 This method can only disconnect functions which have been added using the
629 Connect() method. There is no way to disconnect functions connected using
630 the (static) event tables.
633 The event type associated with this event handler.
635 The event handler function.
637 Data associated with the event table entry.
639 Object whose member function should be called.
641 bool Disconnect(wxEventType eventType
,
642 wxObjectEventFunction function
,
643 wxObject
* userData
= NULL
,
644 wxEvtHandler
* eventSink
= NULL
);
647 See the Disconnect(wxEventType, wxObjectEventFunction, wxObject*, wxEvtHandler*)
648 overload for more info.
650 This overload takes the additional @a id parameter.
652 bool Disconnect(int id
= wxID_ANY
,
653 wxEventType eventType
= wxEVT_NULL
,
654 wxObjectEventFunction function
= NULL
,
655 wxObject
* userData
= NULL
,
656 wxEvtHandler
* eventSink
= NULL
);
659 See the Disconnect(wxEventType, wxObjectEventFunction, wxObject*, wxEvtHandler*)
660 overload for more info.
662 This overload takes an additional range of source IDs.
664 bool Disconnect(int id
, int lastId
,
665 wxEventType eventType
,
666 wxObjectEventFunction function
= NULL
,
667 wxObject
* userData
= NULL
,
668 wxEvtHandler
* eventSink
= NULL
);
673 @name User-supplied data
678 Returns user-supplied client data.
680 @remarks Normally, any extra data the programmer wishes to associate with
681 the object should be made available by deriving a new class with
686 void* GetClientData() const;
689 Returns a pointer to the user-supplied client data object.
691 @see SetClientObject(), wxClientData
693 wxClientData
* GetClientObject() const;
696 Sets user-supplied client data.
699 Data to be associated with the event handler.
701 @remarks Normally, any extra data the programmer wishes to associate
702 with the object should be made available by deriving a new
703 class with new data members. You must not call this method
704 and SetClientObject on the same class - only one of them.
708 void SetClientData(void* data
);
711 Set the client data object. Any previous object will be deleted.
713 @see GetClientObject(), wxClientData
715 void SetClientObject(wxClientData
* data
);
721 @name Event handler chaining
723 wxEvtHandler can be arranged in a double-linked list of handlers
724 which is automatically iterated by ProcessEvent() if needed.
729 Returns @true if the event handler is enabled, @false otherwise.
731 @see SetEvtHandlerEnabled()
733 bool GetEvtHandlerEnabled() const;
736 Returns the pointer to the next handler in the chain.
738 @see SetNextHandler(), GetPreviousHandler(), SetPreviousHandler(),
739 wxWindow::PushEventHandler, wxWindow::PopEventHandler
741 wxEvtHandler
* GetNextHandler() const;
744 Returns the pointer to the previous handler in the chain.
746 @see SetPreviousHandler(), GetNextHandler(), SetNextHandler(),
747 wxWindow::PushEventHandler, wxWindow::PopEventHandler
749 wxEvtHandler
* GetPreviousHandler() const;
752 Enables or disables the event handler.
755 @true if the event handler is to be enabled, @false if it is to be disabled.
757 @remarks You can use this function to avoid having to remove the event
758 handler from the chain, for example when implementing a
759 dialog editor and changing from edit to test mode.
761 @see GetEvtHandlerEnabled()
763 void SetEvtHandlerEnabled(bool enabled
);
766 Sets the pointer to the next handler.
769 See ProcessEvent() for more info about how the chains of event handlers
771 Also remember that wxEvtHandler uses double-linked lists and thus if you
772 use this function, you should also call SetPreviousHandler() on the
773 argument passed to this function:
775 handlerA->SetNextHandler(handlerB);
776 handlerB->SetPreviousHandler(handlerA);
780 The event handler to be set as the next handler.
783 @see @ref overview_events_processing
785 virtual void SetNextHandler(wxEvtHandler
* handler
);
788 Sets the pointer to the previous handler.
789 All remarks about SetNextHandler() apply to this function as well.
792 The event handler to be set as the previous handler.
795 @see @ref overview_events_processing
797 virtual void SetPreviousHandler(wxEvtHandler
* handler
);
800 Unlinks this event handler from the chain it's part of (if any);
801 then links the "previous" event handler to the "next" one
802 (so that the chain won't be interrupted).
804 E.g. if before calling Unlink() you have the following chain:
805 @image html evthandler_unlink_before.png
806 then after calling @c B->Unlink() you'll have:
807 @image html evthandler_unlink_after.png
814 Returns @true if the next and the previous handler pointers of this
815 event handler instance are @NULL.
819 @see SetPreviousHandler(), SetNextHandler()
821 bool IsUnlinked() const;
830 This event class contains information about keypress (character) events.
832 Notice that there are three different kinds of keyboard events in wxWidgets:
833 key down and up events and char events. The difference between the first two
834 is clear - the first corresponds to a key press and the second to a key
835 release - otherwise they are identical. Just note that if the key is
836 maintained in a pressed state you will typically get a lot of (automatically
837 generated) down events but only one up so it is wrong to assume that there is
838 one up event corresponding to each down one.
840 Both key events provide untranslated key codes while the char event carries
841 the translated one. The untranslated code for alphanumeric keys is always
842 an upper case value. For the other keys it is one of @c WXK_XXX values
843 from the ::wxKeyCode enumeration.
844 The translated key is, in general, the character the user expects to appear
845 as the result of the key combination when typing the text into a text entry
848 A few examples to clarify this (all assume that CAPS LOCK is unpressed
849 and the standard US keyboard): when the @c 'A' key is pressed, the key down
850 event key code is equal to @c ASCII A == 65. But the char event key code
851 is @c ASCII a == 97. On the other hand, if you press both SHIFT and
852 @c 'A' keys simultaneously , the key code in key down event will still be
853 just @c 'A' while the char event key code parameter will now be @c 'A'
856 Although in this simple case it is clear that the correct key code could be
857 found in the key down event handler by checking the value returned by
858 wxKeyEvent::ShiftDown(), in general you should use @c EVT_CHAR for this as
859 for non-alphanumeric keys the translation is keyboard-layout dependent and
860 can only be done properly by the system itself.
862 Another kind of translation is done when the control key is pressed: for
863 example, for CTRL-A key press the key down event still carries the
864 same key code @c 'a' as usual but the char event will have key code of 1,
865 the ASCII value of this key combination.
867 You may discover how the other keys on your system behave interactively by
868 running the @ref page_samples_text wxWidgets sample and pressing some keys
869 in any of the text controls shown in it.
871 @b Tip: be sure to call @c event.Skip() for events that you don't process in
872 key event function, otherwise menu shortcuts may cease to work under Windows.
874 @note If a key down (@c EVT_KEY_DOWN) event is caught and the event handler
875 does not call @c event.Skip() then the corresponding char event
876 (@c EVT_CHAR) will not happen.
877 This is by design and enables the programs that handle both types of
878 events to be a bit simpler.
880 @note For Windows programmers: The key and char events in wxWidgets are
881 similar to but slightly different from Windows @c WM_KEYDOWN and
882 @c WM_CHAR events. In particular, Alt-x combination will generate a
883 char event in wxWidgets (unless it is used as an accelerator).
886 @beginEventTable{wxKeyEvent}
887 @event{EVT_KEY_DOWN(func)}
888 Process a @c wxEVT_KEY_DOWN event (any key has been pressed).
889 @event{EVT_KEY_UP(func)}
890 Process a @c wxEVT_KEY_UP event (any key has been released).
891 @event{EVT_CHAR(func)}
892 Process a @c wxEVT_CHAR event.
900 class wxKeyEvent
: public wxEvent
,
901 public wxKeyboardState
906 Currently, the only valid event types are @c wxEVT_CHAR and @c wxEVT_CHAR_HOOK.
908 wxKeyEvent(wxEventType keyEventType
= wxEVT_NULL
);
911 Returns the virtual key code. ASCII events return normal ASCII values,
912 while non-ASCII events return values such as @b WXK_LEFT for the left cursor
913 key. See ::wxKeyCode for a full list of the virtual key codes.
915 Note that in Unicode build, the returned value is meaningful only if the
916 user entered a character that can be represented in current locale's default
917 charset. You can obtain the corresponding Unicode character using GetUnicodeKey().
919 int GetKeyCode() const;
923 Obtains the position (in client coordinates) at which the key was pressed.
925 wxPoint
GetPosition() const;
926 void GetPosition(long* x
, long* y
) const;
930 Returns the raw key code for this event. This is a platform-dependent scan code
931 which should only be used in advanced applications.
933 @note Currently the raw key codes are not supported by all ports, use
934 @ifdef_ wxHAS_RAW_KEY_CODES to determine if this feature is available.
936 wxUint32
GetRawKeyCode() const;
939 Returns the low level key flags for this event. The flags are
940 platform-dependent and should only be used in advanced applications.
942 @note Currently the raw key flags are not supported by all ports, use
943 @ifdef_ wxHAS_RAW_KEY_CODES to determine if this feature is available.
945 wxUint32
GetRawKeyFlags() const;
948 Returns the Unicode character corresponding to this key event.
950 This function is only available in Unicode build, i.e. when
951 @c wxUSE_UNICODE is 1.
953 wxChar
GetUnicodeKey() const;
956 Returns the X position (in client coordinates) of the event.
958 wxCoord
GetX() const;
961 Returns the Y position (in client coordinates) of the event.
963 wxCoord
GetY() const;
969 @class wxJoystickEvent
971 This event class contains information about joystick events, particularly
972 events received by windows.
974 @beginEventTable{wxJoystickEvent}
975 @event{EVT_JOY_BUTTON_DOWN(func)}
976 Process a @c wxEVT_JOY_BUTTON_DOWN event.
977 @event{EVT_JOY_BUTTON_UP(func)}
978 Process a @c wxEVT_JOY_BUTTON_UP event.
979 @event{EVT_JOY_MOVE(func)}
980 Process a @c wxEVT_JOY_MOVE event.
981 @event{EVT_JOY_ZMOVE(func)}
982 Process a @c wxEVT_JOY_ZMOVE event.
983 @event{EVT_JOYSTICK_EVENTS(func)}
984 Processes all joystick events.
992 class wxJoystickEvent
: public wxEvent
998 wxJoystickEvent(wxEventType eventType
= wxEVT_NULL
, int state
= 0,
999 int joystick
= wxJOYSTICK1
,
1003 Returns @true if the event was a down event from the specified button
1007 Can be @c wxJOY_BUTTONn where @c n is 1, 2, 3 or 4; or @c wxJOY_BUTTON_ANY to
1008 indicate any button down event.
1010 bool ButtonDown(int button
= wxJOY_BUTTON_ANY
) const;
1013 Returns @true if the specified button (or any button) was in a down state.
1016 Can be @c wxJOY_BUTTONn where @c n is 1, 2, 3 or 4; or @c wxJOY_BUTTON_ANY to
1017 indicate any button down event.
1019 bool ButtonIsDown(int button
= wxJOY_BUTTON_ANY
) const;
1022 Returns @true if the event was an up event from the specified button
1026 Can be @c wxJOY_BUTTONn where @c n is 1, 2, 3 or 4; or @c wxJOY_BUTTON_ANY to
1027 indicate any button down event.
1029 bool ButtonUp(int button
= wxJOY_BUTTON_ANY
) const;
1032 Returns the identifier of the button changing state.
1034 This is a @c wxJOY_BUTTONn identifier, where @c n is one of 1, 2, 3, 4.
1036 int GetButtonChange() const;
1039 Returns the down state of the buttons.
1041 This is a @c wxJOY_BUTTONn identifier, where @c n is one of 1, 2, 3, 4.
1043 int GetButtonState() const;
1046 Returns the identifier of the joystick generating the event - one of
1047 wxJOYSTICK1 and wxJOYSTICK2.
1049 int GetJoystick() const;
1052 Returns the x, y position of the joystick event.
1054 wxPoint
GetPosition() const;
1057 Returns the z position of the joystick event.
1059 int GetZPosition() const;
1062 Returns @true if this was a button up or down event
1063 (@e not 'is any button down?').
1065 bool IsButton() const;
1068 Returns @true if this was an x, y move event.
1070 bool IsMove() const;
1073 Returns @true if this was a z move event.
1075 bool IsZMove() const;
1081 @class wxScrollWinEvent
1083 A scroll event holds information about events sent from scrolling windows.
1085 Note that you can use the EVT_SCROLLWIN* macros for intercepting scroll window events
1086 from the receiving window.
1088 @beginEventTable{wxScrollWinEvent}
1089 @event{EVT_SCROLLWIN(func)}
1090 Process all scroll events.
1091 @event{EVT_SCROLLWIN_TOP(func)}
1092 Process wxEVT_SCROLLWIN_TOP scroll-to-top events.
1093 @event{EVT_SCROLLWIN_BOTTOM(func)}
1094 Process wxEVT_SCROLLWIN_BOTTOM scroll-to-bottom events.
1095 @event{EVT_SCROLLWIN_LINEUP(func)}
1096 Process wxEVT_SCROLLWIN_LINEUP line up events.
1097 @event{EVT_SCROLLWIN_LINEDOWN(func)}
1098 Process wxEVT_SCROLLWIN_LINEDOWN line down events.
1099 @event{EVT_SCROLLWIN_PAGEUP(func)}
1100 Process wxEVT_SCROLLWIN_PAGEUP page up events.
1101 @event{EVT_SCROLLWIN_PAGEDOWN(func)}
1102 Process wxEVT_SCROLLWIN_PAGEDOWN page down events.
1103 @event{EVT_SCROLLWIN_THUMBTRACK(func)}
1104 Process wxEVT_SCROLLWIN_THUMBTRACK thumbtrack events
1105 (frequent events sent as the user drags the thumbtrack).
1106 @event{EVT_SCROLLWIN_THUMBRELEASE(func)}
1107 Process wxEVT_SCROLLWIN_THUMBRELEASE thumb release events.
1114 @see wxScrollEvent, @ref overview_events
1116 class wxScrollWinEvent
: public wxEvent
1122 wxScrollWinEvent(wxEventType commandType
= wxEVT_NULL
, int pos
= 0,
1123 int orientation
= 0);
1126 Returns wxHORIZONTAL or wxVERTICAL, depending on the orientation of the
1129 @todo wxHORIZONTAL and wxVERTICAL should go in their own enum
1131 int GetOrientation() const;
1134 Returns the position of the scrollbar for the thumb track and release events.
1136 Note that this field can't be used for the other events, you need to query
1137 the window itself for the current position in that case.
1139 int GetPosition() const;
1145 @class wxSysColourChangedEvent
1147 This class is used for system colour change events, which are generated
1148 when the user changes the colour settings using the control panel.
1149 This is only appropriate under Windows.
1152 The default event handler for this event propagates the event to child windows,
1153 since Windows only sends the events to top-level windows.
1154 If intercepting this event for a top-level window, remember to call the base
1155 class handler, or to pass the event on to the window's children explicitly.
1157 @beginEventTable{wxSysColourChangedEvent}
1158 @event{EVT_SYS_COLOUR_CHANGED(func)}
1159 Process a @c wxEVT_SYS_COLOUR_CHANGED event.
1165 @see @ref overview_events
1167 class wxSysColourChangedEvent
: public wxEvent
1173 wxSysColourChangedEvent();
1179 @class wxWindowCreateEvent
1181 This event is sent just after the actual window associated with a wxWindow
1182 object has been created.
1184 Since it is derived from wxCommandEvent, the event propagates up
1185 the window hierarchy.
1187 @beginEventTable{wxWindowCreateEvent}
1188 @event{EVT_WINDOW_CREATE(func)}
1189 Process a @c wxEVT_CREATE event.
1195 @see @ref overview_events, wxWindowDestroyEvent
1197 class wxWindowCreateEvent
: public wxCommandEvent
1203 wxWindowCreateEvent(wxWindow
* win
= NULL
);
1205 /// Retutn the window being created.
1206 wxWindow
*GetWindow() const;
1214 A paint event is sent when a window's contents needs to be repainted.
1216 Please notice that in general it is impossible to change the drawing of a
1217 standard control (such as wxButton) and so you shouldn't attempt to handle
1218 paint events for them as even if it might work on some platforms, this is
1219 inherently not portable and won't work everywhere.
1222 Note that in a paint event handler, the application must always create a
1223 wxPaintDC object, even if you do not use it. Otherwise, under MS Windows,
1224 refreshing for this and other windows will go wrong.
1227 void MyWindow::OnPaint(wxPaintEvent& event)
1234 You can optimize painting by retrieving the rectangles that have been damaged
1235 and only repainting these. The rectangles are in terms of the client area,
1236 and are unscrolled, so you will need to do some calculations using the current
1237 view position to obtain logical, scrolled units.
1238 Here is an example of using the wxRegionIterator class:
1240 // Called when window needs to be repainted.
1241 void MyWindow::OnPaint(wxPaintEvent& event)
1245 // Find Out where the window is scrolled to
1246 int vbX,vbY; // Top left corner of client
1247 GetViewStart(&vbX,&vbY);
1249 int vX,vY,vW,vH; // Dimensions of client area in pixels
1250 wxRegionIterator upd(GetUpdateRegion()); // get the update rect list
1259 // Alternatively we can do this:
1260 // wxRect rect(upd.GetRect());
1262 // Repaint this rectangle
1271 @beginEventTable{wxPaintEvent}
1272 @event{EVT_PAINT(func)}
1273 Process a @c wxEVT_PAINT event.
1279 @see @ref overview_events
1281 class wxPaintEvent
: public wxEvent
1287 wxPaintEvent(int id
= 0);
1293 @class wxMaximizeEvent
1295 An event being sent when a top level window is maximized. Notice that it is
1296 not sent when the window is restored to its original size after it had been
1297 maximized, only a normal wxSizeEvent is generated in this case.
1299 @beginEventTable{wxMaximizeEvent}
1300 @event{EVT_MAXIMIZE(func)}
1301 Process a @c wxEVT_MAXIMIZE event.
1307 @see @ref overview_events, wxTopLevelWindow::Maximize,
1308 wxTopLevelWindow::IsMaximized
1310 class wxMaximizeEvent
: public wxEvent
1314 Constructor. Only used by wxWidgets internally.
1316 wxMaximizeEvent(int id
= 0);
1320 The possibles modes to pass to wxUpdateUIEvent::SetMode().
1324 /** Send UI update events to all windows. */
1325 wxUPDATE_UI_PROCESS_ALL
,
1327 /** Send UI update events to windows that have
1328 the wxWS_EX_PROCESS_UI_UPDATES flag specified. */
1329 wxUPDATE_UI_PROCESS_SPECIFIED
1334 @class wxUpdateUIEvent
1336 This class is used for pseudo-events which are called by wxWidgets
1337 to give an application the chance to update various user interface elements.
1339 Without update UI events, an application has to work hard to check/uncheck,
1340 enable/disable, show/hide, and set the text for elements such as menu items
1341 and toolbar buttons. The code for doing this has to be mixed up with the code
1342 that is invoked when an action is invoked for a menu item or button.
1344 With update UI events, you define an event handler to look at the state of the
1345 application and change UI elements accordingly. wxWidgets will call your member
1346 functions in idle time, so you don't have to worry where to call this code.
1348 In addition to being a clearer and more declarative method, it also means you don't
1349 have to worry whether you're updating a toolbar or menubar identifier. The same
1350 handler can update a menu item and toolbar button, if the identifier is the same.
1351 Instead of directly manipulating the menu or button, you call functions in the event
1352 object, such as wxUpdateUIEvent::Check. wxWidgets will determine whether such a
1353 call has been made, and which UI element to update.
1355 These events will work for popup menus as well as menubars. Just before a menu is
1356 popped up, wxMenu::UpdateUI is called to process any UI events for the window that
1359 If you find that the overhead of UI update processing is affecting your application,
1360 you can do one or both of the following:
1361 @li Call wxUpdateUIEvent::SetMode with a value of wxUPDATE_UI_PROCESS_SPECIFIED,
1362 and set the extra style wxWS_EX_PROCESS_UI_UPDATES for every window that should
1363 receive update events. No other windows will receive update events.
1364 @li Call wxUpdateUIEvent::SetUpdateInterval with a millisecond value to set the delay
1365 between updates. You may need to call wxWindow::UpdateWindowUI at critical points,
1366 for example when a dialog is about to be shown, in case the user sees a slight
1367 delay before windows are updated.
1369 Note that although events are sent in idle time, defining a wxIdleEvent handler
1370 for a window does not affect this because the events are sent from wxWindow::OnInternalIdle
1371 which is always called in idle time.
1373 wxWidgets tries to optimize update events on some platforms.
1374 On Windows and GTK+, events for menubar items are only sent when the menu is about
1375 to be shown, and not in idle time.
1378 @beginEventTable{wxUpdateUIEvent}
1379 @event{EVT_UPDATE_UI(id, func)}
1380 Process a @c wxEVT_UPDATE_UI event for the command with the given id.
1381 @event{EVT_UPDATE_UI_RANGE(id1, id2, func)}
1382 Process a @c wxEVT_UPDATE_UI event for any command with id included in the given range.
1388 @see @ref overview_events
1390 class wxUpdateUIEvent
: public wxCommandEvent
1396 wxUpdateUIEvent(wxWindowID commandId
= 0);
1399 Returns @true if it is appropriate to update (send UI update events to)
1402 This function looks at the mode used (see wxUpdateUIEvent::SetMode),
1403 the wxWS_EX_PROCESS_UI_UPDATES flag in @a window, the time update events
1404 were last sent in idle time, and the update interval, to determine whether
1405 events should be sent to this window now. By default this will always
1406 return @true because the update mode is initially wxUPDATE_UI_PROCESS_ALL
1407 and the interval is set to 0; so update events will be sent as often as
1408 possible. You can reduce the frequency that events are sent by changing the
1409 mode and/or setting an update interval.
1411 @see ResetUpdateTime(), SetUpdateInterval(), SetMode()
1413 static bool CanUpdate(wxWindow
* window
);
1416 Check or uncheck the UI element.
1418 void Check(bool check
);
1421 Enable or disable the UI element.
1423 void Enable(bool enable
);
1426 Returns @true if the UI element should be checked.
1428 bool GetChecked() const;
1431 Returns @true if the UI element should be enabled.
1433 bool GetEnabled() const;
1436 Static function returning a value specifying how wxWidgets will send update
1437 events: to all windows, or only to those which specify that they will process
1442 static wxUpdateUIMode
GetMode();
1445 Returns @true if the application has called Check().
1446 For wxWidgets internal use only.
1448 bool GetSetChecked() const;
1451 Returns @true if the application has called Enable().
1452 For wxWidgets internal use only.
1454 bool GetSetEnabled() const;
1457 Returns @true if the application has called Show().
1458 For wxWidgets internal use only.
1460 bool GetSetShown() const;
1463 Returns @true if the application has called SetText().
1464 For wxWidgets internal use only.
1466 bool GetSetText() const;
1469 Returns @true if the UI element should be shown.
1471 bool GetShown() const;
1474 Returns the text that should be set for the UI element.
1476 wxString
GetText() const;
1479 Returns the current interval between updates in milliseconds.
1480 The value -1 disables updates, 0 updates as frequently as possible.
1482 @see SetUpdateInterval().
1484 static long GetUpdateInterval();
1487 Used internally to reset the last-updated time to the current time.
1489 It is assumed that update events are normally sent in idle time, so this
1490 is called at the end of idle processing.
1492 @see CanUpdate(), SetUpdateInterval(), SetMode()
1494 static void ResetUpdateTime();
1497 Specify how wxWidgets will send update events: to all windows, or only to
1498 those which specify that they will process the events.
1501 this parameter may be one of the ::wxUpdateUIMode enumeration values.
1502 The default mode is wxUPDATE_UI_PROCESS_ALL.
1504 static void SetMode(wxUpdateUIMode mode
);
1507 Sets the text for this UI element.
1509 void SetText(const wxString
& text
);
1512 Sets the interval between updates in milliseconds.
1514 Set to -1 to disable updates, or to 0 to update as frequently as possible.
1517 Use this to reduce the overhead of UI update events if your application
1518 has a lot of windows. If you set the value to -1 or greater than 0,
1519 you may also need to call wxWindow::UpdateWindowUI at appropriate points
1520 in your application, such as when a dialog is about to be shown.
1522 static void SetUpdateInterval(long updateInterval
);
1525 Show or hide the UI element.
1527 void Show(bool show
);
1533 @class wxClipboardTextEvent
1535 This class represents the events generated by a control (typically a
1536 wxTextCtrl but other windows can generate these events as well) when its
1537 content gets copied or cut to, or pasted from the clipboard.
1539 There are three types of corresponding events wxEVT_COMMAND_TEXT_COPY,
1540 wxEVT_COMMAND_TEXT_CUT and wxEVT_COMMAND_TEXT_PASTE.
1542 If any of these events is processed (without being skipped) by an event
1543 handler, the corresponding operation doesn't take place which allows to
1544 prevent the text from being copied from or pasted to a control. It is also
1545 possible to examine the clipboard contents in the PASTE event handler and
1546 transform it in some way before inserting in a control -- for example,
1547 changing its case or removing invalid characters.
1549 Finally notice that a CUT event is always preceded by the COPY event which
1550 makes it possible to only process the latter if it doesn't matter if the
1551 text was copied or cut.
1554 These events are currently only generated by wxTextCtrl under GTK+.
1555 They are generated by all controls under Windows.
1557 @beginEventTable{wxClipboardTextEvent}
1558 @event{EVT_TEXT_COPY(id, func)}
1559 Some or all of the controls content was copied to the clipboard.
1560 @event{EVT_TEXT_CUT(id, func)}
1561 Some or all of the controls content was cut (i.e. copied and
1563 @event{EVT_TEXT_PASTE(id, func)}
1564 Clipboard content was pasted into the control.
1573 class wxClipboardTextEvent
: public wxCommandEvent
1579 wxClipboardTextEvent(wxEventType commandType
= wxEVT_NULL
, int id
= 0);
1587 This event class contains information about the events generated by the mouse:
1588 they include mouse buttons press and release events and mouse move events.
1590 All mouse events involving the buttons use @c wxMOUSE_BTN_LEFT for the
1591 left mouse button, @c wxMOUSE_BTN_MIDDLE for the middle one and
1592 @c wxMOUSE_BTN_RIGHT for the right one. And if the system supports more
1593 buttons, the @c wxMOUSE_BTN_AUX1 and @c wxMOUSE_BTN_AUX2 events
1594 can also be generated. Note that not all mice have even a middle button so a
1595 portable application should avoid relying on the events from it (but the right
1596 button click can be emulated using the left mouse button with the control key
1597 under Mac platforms with a single button mouse).
1599 For the @c wxEVT_ENTER_WINDOW and @c wxEVT_LEAVE_WINDOW events
1600 purposes, the mouse is considered to be inside the window if it is in the
1601 window client area and not inside one of its children. In other words, the
1602 parent window receives @c wxEVT_LEAVE_WINDOW event not only when the
1603 mouse leaves the window entirely but also when it enters one of its children.
1605 The position associated with a mouse event is expressed in the window
1606 coordinates of the window which generated the event, you can use
1607 wxWindow::ClientToScreen() to convert it to screen coordinates and possibly
1608 call wxWindow::ScreenToClient() next to convert it to window coordinates of
1611 @note Note that under Windows CE mouse enter and leave events are not natively
1612 supported by the system but are generated by wxWidgets itself. This has several
1613 drawbacks: the LEAVE_WINDOW event might be received some time after the mouse
1614 left the window and the state variables for it may have changed during this time.
1616 @note Note the difference between methods like wxMouseEvent::LeftDown and
1617 wxMouseEvent::LeftIsDown: the former returns @true when the event corresponds
1618 to the left mouse button click while the latter returns @true if the left
1619 mouse button is currently being pressed. For example, when the user is dragging
1620 the mouse you can use wxMouseEvent::LeftIsDown to test whether the left mouse
1621 button is (still) depressed. Also, by convention, if wxMouseEvent::LeftDown
1622 returns @true, wxMouseEvent::LeftIsDown will also return @true in wxWidgets
1623 whatever the underlying GUI behaviour is (which is platform-dependent).
1624 The same applies, of course, to other mouse buttons as well.
1627 @beginEventTable{wxMouseEvent}
1628 @event{EVT_LEFT_DOWN(func)}
1629 Process a @c wxEVT_LEFT_DOWN event. The handler of this event should normally
1630 call event.Skip() to allow the default processing to take place as otherwise
1631 the window under mouse wouldn't get the focus.
1632 @event{EVT_LEFT_UP(func)}
1633 Process a @c wxEVT_LEFT_UP event.
1634 @event{EVT_LEFT_DCLICK(func)}
1635 Process a @c wxEVT_LEFT_DCLICK event.
1636 @event{EVT_MIDDLE_DOWN(func)}
1637 Process a @c wxEVT_MIDDLE_DOWN event.
1638 @event{EVT_MIDDLE_UP(func)}
1639 Process a @c wxEVT_MIDDLE_UP event.
1640 @event{EVT_MIDDLE_DCLICK(func)}
1641 Process a @c wxEVT_MIDDLE_DCLICK event.
1642 @event{EVT_RIGHT_DOWN(func)}
1643 Process a @c wxEVT_RIGHT_DOWN event.
1644 @event{EVT_RIGHT_UP(func)}
1645 Process a @c wxEVT_RIGHT_UP event.
1646 @event{EVT_RIGHT_DCLICK(func)}
1647 Process a @c wxEVT_RIGHT_DCLICK event.
1648 @event{EVT_MOUSE_AUX1_DOWN(func)}
1649 Process a @c wxEVT_MOUSE_AUX1_DOWN event.
1650 @event{EVT_MOUSE_AUX1_UP(func)}
1651 Process a @c wxEVT_MOUSE_AUX1_UP event.
1652 @event{EVT_MOUSE_AUX1_DCLICK(func)}
1653 Process a @c wxEVT_MOUSE_AUX1_DCLICK event.
1654 @event{EVT_MOUSE_AUX2_DOWN(func)}
1655 Process a @c wxEVT_MOUSE_AUX2_DOWN event.
1656 @event{EVT_MOUSE_AUX2_UP(func)}
1657 Process a @c wxEVT_MOUSE_AUX2_UP event.
1658 @event{EVT_MOUSE_AUX2_DCLICK(func)}
1659 Process a @c wxEVT_MOUSE_AUX2_DCLICK event.
1660 @event{EVT_MOTION(func)}
1661 Process a @c wxEVT_MOTION event.
1662 @event{EVT_ENTER_WINDOW(func)}
1663 Process a @c wxEVT_ENTER_WINDOW event.
1664 @event{EVT_LEAVE_WINDOW(func)}
1665 Process a @c wxEVT_LEAVE_WINDOW event.
1666 @event{EVT_MOUSEWHEEL(func)}
1667 Process a @c wxEVT_MOUSEWHEEL event.
1668 @event{EVT_MOUSE_EVENTS(func)}
1669 Process all mouse events.
1677 class wxMouseEvent
: public wxEvent
,
1682 Constructor. Valid event types are:
1684 @li wxEVT_ENTER_WINDOW
1685 @li wxEVT_LEAVE_WINDOW
1688 @li wxEVT_LEFT_DCLICK
1689 @li wxEVT_MIDDLE_DOWN
1691 @li wxEVT_MIDDLE_DCLICK
1692 @li wxEVT_RIGHT_DOWN
1694 @li wxEVT_RIGHT_DCLICK
1695 @li wxEVT_MOUSE_AUX1_DOWN
1696 @li wxEVT_MOUSE_AUX1_UP
1697 @li wxEVT_MOUSE_AUX1_DCLICK
1698 @li wxEVT_MOUSE_AUX2_DOWN
1699 @li wxEVT_MOUSE_AUX2_UP
1700 @li wxEVT_MOUSE_AUX2_DCLICK
1702 @li wxEVT_MOUSEWHEEL
1704 wxMouseEvent(wxEventType mouseEventType
= wxEVT_NULL
);
1707 Returns @true if the event was a first extra button double click.
1709 bool Aux1DClick() const;
1712 Returns @true if the first extra button mouse button changed to down.
1714 bool Aux1Down() const;
1717 Returns @true if the first extra button mouse button is currently down,
1718 independent of the current event type.
1720 bool Aux1IsDown() const;
1723 Returns @true if the first extra button mouse button changed to up.
1725 bool Aux1Up() const;
1728 Returns @true if the event was a second extra button double click.
1730 bool Aux2DClick() const;
1733 Returns @true if the second extra button mouse button changed to down.
1735 bool Aux2Down() const;
1738 Returns @true if the second extra button mouse button is currently down,
1739 independent of the current event type.
1741 bool Aux2IsDown() const;
1744 Returns @true if the second extra button mouse button changed to up.
1746 bool Aux2Up() const;
1749 Returns @true if the identified mouse button is changing state.
1750 Valid values of @a button are:
1752 @li @c wxMOUSE_BTN_LEFT: check if left button was pressed
1753 @li @c wxMOUSE_BTN_MIDDLE: check if middle button was pressed
1754 @li @c wxMOUSE_BTN_RIGHT: check if right button was pressed
1755 @li @c wxMOUSE_BTN_AUX1: check if the first extra button was pressed
1756 @li @c wxMOUSE_BTN_AUX2: check if the second extra button was pressed
1757 @li @c wxMOUSE_BTN_ANY: check if any button was pressed
1759 @todo introduce wxMouseButton enum
1761 bool Button(int button
) const;
1764 If the argument is omitted, this returns @true if the event was a mouse
1765 double click event. Otherwise the argument specifies which double click event
1766 was generated (see Button() for the possible values).
1768 bool ButtonDClick(int but
= wxMOUSE_BTN_ANY
) const;
1771 If the argument is omitted, this returns @true if the event was a mouse
1772 button down event. Otherwise the argument specifies which button-down event
1773 was generated (see Button() for the possible values).
1775 bool ButtonDown(int = wxMOUSE_BTN_ANY
) const;
1778 If the argument is omitted, this returns @true if the event was a mouse
1779 button up event. Otherwise the argument specifies which button-up event
1780 was generated (see Button() for the possible values).
1782 bool ButtonUp(int = wxMOUSE_BTN_ANY
) const;
1785 Returns @true if this was a dragging event (motion while a button is depressed).
1789 bool Dragging() const;
1792 Returns @true if the mouse was entering the window.
1796 bool Entering() const;
1799 Returns the mouse button which generated this event or @c wxMOUSE_BTN_NONE
1800 if no button is involved (for mouse move, enter or leave event, for example).
1801 Otherwise @c wxMOUSE_BTN_LEFT is returned for the left button down, up and
1802 double click events, @c wxMOUSE_BTN_MIDDLE and @c wxMOUSE_BTN_RIGHT
1803 for the same events for the middle and the right buttons respectively.
1805 int GetButton() const;
1808 Returns the number of mouse clicks for this event: 1 for a simple click, 2
1809 for a double-click, 3 for a triple-click and so on.
1811 Currently this function is implemented only in wxMac and returns -1 for the
1812 other platforms (you can still distinguish simple clicks from double-clicks as
1813 they generate different kinds of events however).
1817 int GetClickCount() const;
1820 Returns the configured number of lines (or whatever) to be scrolled per
1821 wheel action. Defaults to three.
1823 int GetLinesPerAction() const;
1826 Returns the logical mouse position in pixels (i.e. translated according to the
1827 translation set for the DC, which usually indicates that the window has been
1830 wxPoint
GetLogicalPosition(const wxDC
& dc
) const;
1834 Sets *x and *y to the position at which the event occurred.
1835 Returns the physical mouse position in pixels.
1837 Note that if the mouse event has been artificially generated from a special
1838 keyboard combination (e.g. under Windows when the "menu" key is pressed), the
1839 returned position is ::wxDefaultPosition.
1841 wxPoint
GetPosition() const;
1842 void GetPosition(wxCoord
* x
, wxCoord
* y
) const;
1843 void GetPosition(long* x
, long* y
) const;
1847 Get wheel delta, normally 120.
1849 This is the threshold for action to be taken, and one such action
1850 (for example, scrolling one increment) should occur for each delta.
1852 int GetWheelDelta() const;
1855 Get wheel rotation, positive or negative indicates direction of rotation.
1857 Current devices all send an event when rotation is at least +/-WheelDelta, but
1858 finer resolution devices can be created in the future.
1860 Because of this you shouldn't assume that one event is equal to 1 line, but you
1861 should be able to either do partial line scrolling or wait until several
1862 events accumulate before scrolling.
1864 int GetWheelRotation() const;
1867 Gets the axis the wheel operation concerns; @c 0 is the Y axis as on
1868 most mouse wheels, @c 1 is the X axis.
1870 Note that only some models of mouse have horizontal wheel axis.
1872 int GetWheelAxis() const;
1875 Returns X coordinate of the physical mouse event position.
1877 wxCoord
GetX() const;
1880 Returns Y coordinate of the physical mouse event position.
1882 wxCoord
GetY() const;
1885 Returns @true if the event was a mouse button event (not necessarily a button
1886 down event - that may be tested using ButtonDown()).
1888 bool IsButton() const;
1891 Returns @true if the system has been setup to do page scrolling with
1892 the mouse wheel instead of line scrolling.
1894 bool IsPageScroll() const;
1897 Returns @true if the mouse was leaving the window.
1901 bool Leaving() const;
1904 Returns @true if the event was a left double click.
1906 bool LeftDClick() const;
1909 Returns @true if the left mouse button changed to down.
1911 bool LeftDown() const;
1914 Returns @true if the left mouse button is currently down, independent
1915 of the current event type.
1917 Please notice that it is not the same as LeftDown() which returns @true if the
1918 event was generated by the left mouse button being pressed. Rather, it simply
1919 describes the state of the left mouse button at the time when the event was
1920 generated (so while it will be @true for a left click event, it can also be @true
1921 for a right click if it happened while the left mouse button was pressed).
1923 This event is usually used in the mouse event handlers which process "move
1924 mouse" messages to determine whether the user is (still) dragging the mouse.
1926 bool LeftIsDown() const;
1929 Returns @true if the left mouse button changed to up.
1931 bool LeftUp() const;
1934 Returns @true if the Meta key was down at the time of the event.
1936 bool MetaDown() const;
1939 Returns @true if the event was a middle double click.
1941 bool MiddleDClick() const;
1944 Returns @true if the middle mouse button changed to down.
1946 bool MiddleDown() const;
1949 Returns @true if the middle mouse button is currently down, independent
1950 of the current event type.
1952 bool MiddleIsDown() const;
1955 Returns @true if the middle mouse button changed to up.
1957 bool MiddleUp() const;
1960 Returns @true if this was a motion event and no mouse buttons were pressed.
1961 If any mouse button is held pressed, then this method returns @false and
1962 Dragging() returns @true.
1964 bool Moving() const;
1967 Returns @true if the event was a right double click.
1969 bool RightDClick() const;
1972 Returns @true if the right mouse button changed to down.
1974 bool RightDown() const;
1977 Returns @true if the right mouse button is currently down, independent
1978 of the current event type.
1980 bool RightIsDown() const;
1983 Returns @true if the right mouse button changed to up.
1985 bool RightUp() const;
1991 @class wxDropFilesEvent
1993 This class is used for drop files events, that is, when files have been dropped
1994 onto the window. This functionality is currently only available under Windows.
1996 The window must have previously been enabled for dropping by calling
1997 wxWindow::DragAcceptFiles().
1999 Important note: this is a separate implementation to the more general drag and drop
2000 implementation documented in the @ref overview_dnd. It uses the older, Windows
2001 message-based approach of dropping files.
2003 @beginEventTable{wxDropFilesEvent}
2004 @event{EVT_DROP_FILES(func)}
2005 Process a @c wxEVT_DROP_FILES event.
2013 @see @ref overview_events
2015 class wxDropFilesEvent
: public wxEvent
2021 wxDropFilesEvent(wxEventType id
= 0, int noFiles
= 0,
2022 wxString
* files
= NULL
);
2025 Returns an array of filenames.
2027 wxString
* GetFiles() const;
2030 Returns the number of files dropped.
2032 int GetNumberOfFiles() const;
2035 Returns the position at which the files were dropped.
2036 Returns an array of filenames.
2038 wxPoint
GetPosition() const;
2044 @class wxCommandEvent
2046 This event class contains information about command events, which originate
2047 from a variety of simple controls.
2049 Note that wxCommandEvents and wxCommandEvent-derived event classes by default
2050 and unlike other wxEvent-derived classes propagate upward from the source
2051 window (the window which emits the event) up to the first parent which processes
2052 the event. Be sure to read @ref overview_events_propagation.
2054 More complex controls, such as wxTreeCtrl, have separate command event classes.
2056 @beginEventTable{wxCommandEvent}
2057 @event{EVT_COMMAND(id, event, func)}
2058 Process a command, supplying the window identifier, command event identifier,
2059 and member function.
2060 @event{EVT_COMMAND_RANGE(id1, id2, event, func)}
2061 Process a command for a range of window identifiers, supplying the minimum and
2062 maximum window identifiers, command event identifier, and member function.
2063 @event{EVT_BUTTON(id, func)}
2064 Process a @c wxEVT_COMMAND_BUTTON_CLICKED command, which is generated by a wxButton control.
2065 @event{EVT_CHECKBOX(id, func)}
2066 Process a @c wxEVT_COMMAND_CHECKBOX_CLICKED command, which is generated by a wxCheckBox control.
2067 @event{EVT_CHOICE(id, func)}
2068 Process a @c wxEVT_COMMAND_CHOICE_SELECTED command, which is generated by a wxChoice control.
2069 @event{EVT_COMBOBOX(id, func)}
2070 Process a @c wxEVT_COMMAND_COMBOBOX_SELECTED command, which is generated by a wxComboBox control.
2071 @event{EVT_LISTBOX(id, func)}
2072 Process a @c wxEVT_COMMAND_LISTBOX_SELECTED command, which is generated by a wxListBox control.
2073 @event{EVT_LISTBOX_DCLICK(id, func)}
2074 Process a @c wxEVT_COMMAND_LISTBOX_DOUBLECLICKED command, which is generated by a wxListBox control.
2075 @event{EVT_CHECKLISTBOX(id, func)}
2076 Process a @c wxEVT_COMMAND_CHECKLISTBOX_TOGGLED command, which is generated by a wxCheckListBox control.
2077 @event{EVT_MENU(id, func)}
2078 Process a @c wxEVT_COMMAND_MENU_SELECTED command, which is generated by a menu item.
2079 @event{EVT_MENU_RANGE(id1, id2, func)}
2080 Process a @c wxEVT_COMMAND_MENU_RANGE command, which is generated by a range of menu items.
2081 @event{EVT_CONTEXT_MENU(func)}
2082 Process the event generated when the user has requested a popup menu to appear by
2083 pressing a special keyboard key (under Windows) or by right clicking the mouse.
2084 @event{EVT_RADIOBOX(id, func)}
2085 Process a @c wxEVT_COMMAND_RADIOBOX_SELECTED command, which is generated by a wxRadioBox control.
2086 @event{EVT_RADIOBUTTON(id, func)}
2087 Process a @c wxEVT_COMMAND_RADIOBUTTON_SELECTED command, which is generated by a wxRadioButton control.
2088 @event{EVT_SCROLLBAR(id, func)}
2089 Process a @c wxEVT_COMMAND_SCROLLBAR_UPDATED command, which is generated by a wxScrollBar
2090 control. This is provided for compatibility only; more specific scrollbar event macros
2091 should be used instead (see wxScrollEvent).
2092 @event{EVT_SLIDER(id, func)}
2093 Process a @c wxEVT_COMMAND_SLIDER_UPDATED command, which is generated by a wxSlider control.
2094 @event{EVT_TEXT(id, func)}
2095 Process a @c wxEVT_COMMAND_TEXT_UPDATED command, which is generated by a wxTextCtrl control.
2096 @event{EVT_TEXT_ENTER(id, func)}
2097 Process a @c wxEVT_COMMAND_TEXT_ENTER command, which is generated by a wxTextCtrl control.
2098 Note that you must use wxTE_PROCESS_ENTER flag when creating the control if you want it
2099 to generate such events.
2100 @event{EVT_TEXT_MAXLEN(id, func)}
2101 Process a @c wxEVT_COMMAND_TEXT_MAXLEN command, which is generated by a wxTextCtrl control
2102 when the user tries to enter more characters into it than the limit previously set
2103 with SetMaxLength().
2104 @event{EVT_TOGGLEBUTTON(id, func)}
2105 Process a @c wxEVT_COMMAND_TOGGLEBUTTON_CLICKED event.
2106 @event{EVT_TOOL(id, func)}
2107 Process a @c wxEVT_COMMAND_TOOL_CLICKED event (a synonym for @c wxEVT_COMMAND_MENU_SELECTED).
2108 Pass the id of the tool.
2109 @event{EVT_TOOL_RANGE(id1, id2, func)}
2110 Process a @c wxEVT_COMMAND_TOOL_CLICKED event for a range of identifiers. Pass the ids of the tools.
2111 @event{EVT_TOOL_RCLICKED(id, func)}
2112 Process a @c wxEVT_COMMAND_TOOL_RCLICKED event. Pass the id of the tool.
2113 @event{EVT_TOOL_RCLICKED_RANGE(id1, id2, func)}
2114 Process a @c wxEVT_COMMAND_TOOL_RCLICKED event for a range of ids. Pass the ids of the tools.
2115 @event{EVT_TOOL_ENTER(id, func)}
2116 Process a @c wxEVT_COMMAND_TOOL_ENTER event. Pass the id of the toolbar itself.
2117 The value of wxCommandEvent::GetSelection() is the tool id, or -1 if the mouse cursor
2118 has moved off a tool.
2119 @event{EVT_COMMAND_LEFT_CLICK(id, func)}
2120 Process a @c wxEVT_COMMAND_LEFT_CLICK command, which is generated by a control (wxMSW only).
2121 @event{EVT_COMMAND_LEFT_DCLICK(id, func)}
2122 Process a @c wxEVT_COMMAND_LEFT_DCLICK command, which is generated by a control (wxMSW only).
2123 @event{EVT_COMMAND_RIGHT_CLICK(id, func)}
2124 Process a @c wxEVT_COMMAND_RIGHT_CLICK command, which is generated by a control (wxMSW only).
2125 @event{EVT_COMMAND_SET_FOCUS(id, func)}
2126 Process a @c wxEVT_COMMAND_SET_FOCUS command, which is generated by a control (wxMSW only).
2127 @event{EVT_COMMAND_KILL_FOCUS(id, func)}
2128 Process a @c wxEVT_COMMAND_KILL_FOCUS command, which is generated by a control (wxMSW only).
2129 @event{EVT_COMMAND_ENTER(id, func)}
2130 Process a @c wxEVT_COMMAND_ENTER command, which is generated by a control.
2136 class wxCommandEvent
: public wxEvent
2142 wxCommandEvent(wxEventType commandEventType
= wxEVT_NULL
, int id
= 0);
2145 Returns client data pointer for a listbox or choice selection event
2146 (not valid for a deselection).
2148 void* GetClientData() const;
2151 Returns client object pointer for a listbox or choice selection event
2152 (not valid for a deselection).
2154 wxClientData
* GetClientObject() const;
2157 Returns extra information dependant on the event objects type.
2159 If the event comes from a listbox selection, it is a boolean
2160 determining whether the event was a selection (@true) or a
2161 deselection (@false). A listbox deselection only occurs for
2162 multiple-selection boxes, and in this case the index and string values
2163 are indeterminate and the listbox must be examined by the application.
2165 long GetExtraLong() const;
2168 Returns the integer identifier corresponding to a listbox, choice or
2169 radiobox selection (only if the event was a selection, not a deselection),
2170 or a boolean value representing the value of a checkbox.
2175 Returns item index for a listbox or choice selection event (not valid for
2178 int GetSelection() const;
2181 Returns item string for a listbox or choice selection event. If one
2182 or several items have been deselected, returns the index of the first
2183 deselected item. If some items have been selected and others deselected
2184 at the same time, it will return the index of the first selected item.
2186 wxString
GetString() const;
2189 This method can be used with checkbox and menu events: for the checkboxes, the
2190 method returns @true for a selection event and @false for a deselection one.
2191 For the menu events, this method indicates if the menu item just has become
2192 checked or unchecked (and thus only makes sense for checkable menu items).
2194 Notice that this method can not be used with wxCheckListBox currently.
2196 bool IsChecked() const;
2199 For a listbox or similar event, returns @true if it is a selection, @false
2200 if it is a deselection. If some items have been selected and others deselected
2201 at the same time, it will return @true.
2203 bool IsSelection() const;
2206 Sets the client data for this event.
2208 void SetClientData(void* clientData
);
2211 Sets the client object for this event. The client object is not owned by the
2212 event object and the event object will not delete the client object in its destructor.
2214 The client object must be owned and deleted by another object (e.g. a control)
2215 that has longer life time than the event object.
2217 void SetClientObject(wxClientData
* clientObject
);
2220 Sets the @b m_extraLong member.
2222 void SetExtraLong(long extraLong
);
2225 Sets the @b m_commandInt member.
2227 void SetInt(int intCommand
);
2230 Sets the @b m_commandString member.
2232 void SetString(const wxString
& string
);
2238 @class wxActivateEvent
2240 An activate event is sent when a window or application is being activated
2243 @beginEventTable{wxActivateEvent}
2244 @event{EVT_ACTIVATE(func)}
2245 Process a @c wxEVT_ACTIVATE event.
2246 @event{EVT_ACTIVATE_APP(func)}
2247 Process a @c wxEVT_ACTIVATE_APP event.
2248 This event is received by the wxApp-derived instance only.
2249 @event{EVT_HIBERNATE(func)}
2250 Process a hibernate event, supplying the member function. This event applies
2251 to wxApp only, and only on Windows SmartPhone and PocketPC.
2252 It is generated when the system is low on memory; the application should free
2253 up as much memory as possible, and restore full working state when it receives
2254 a wxEVT_ACTIVATE or wxEVT_ACTIVATE_APP event.
2260 @see @ref overview_events, wxApp::IsActive
2262 class wxActivateEvent
: public wxEvent
2268 wxActivateEvent(wxEventType eventType
= wxEVT_NULL
, bool active
= true,
2272 Returns @true if the application or window is being activated, @false otherwise.
2274 bool GetActive() const;
2280 @class wxContextMenuEvent
2282 This class is used for context menu events, sent to give
2283 the application a chance to show a context (popup) menu for a wxWindow.
2285 Note that if wxContextMenuEvent::GetPosition returns wxDefaultPosition, this
2286 means that the event originated from a keyboard context button event, and you
2287 should compute a suitable position yourself, for example by calling wxGetMousePosition().
2289 When a keyboard context menu button is pressed on Windows, a right-click event
2290 with default position is sent first, and if this event is not processed, the
2291 context menu event is sent. So if you process mouse events and you find your
2292 context menu event handler is not being called, you could call wxEvent::Skip()
2293 for mouse right-down events.
2295 @beginEventTable{wxContextMenuEvent}
2296 @event{EVT_CONTEXT_MENU(func)}
2297 A right click (or other context menu command depending on platform) has been detected.
2304 @see wxCommandEvent, @ref overview_events
2306 class wxContextMenuEvent
: public wxCommandEvent
2312 wxContextMenuEvent(wxEventType id
= wxEVT_NULL
, int id
= 0,
2313 const wxPoint
& pos
= wxDefaultPosition
);
2316 Returns the position in screen coordinates at which the menu should be shown.
2317 Use wxWindow::ScreenToClient to convert to client coordinates.
2319 You can also omit a position from wxWindow::PopupMenu in order to use
2320 the current mouse pointer position.
2322 If the event originated from a keyboard event, the value returned from this
2323 function will be wxDefaultPosition.
2325 const wxPoint
& GetPosition() const;
2328 Sets the position at which the menu should be shown.
2330 void SetPosition(const wxPoint
& point
);
2338 An erase event is sent when a window's background needs to be repainted.
2340 On some platforms, such as GTK+, this event is simulated (simply generated just
2341 before the paint event) and may cause flicker. It is therefore recommended that
2342 you set the text background colour explicitly in order to prevent flicker.
2343 The default background colour under GTK+ is grey.
2345 To intercept this event, use the EVT_ERASE_BACKGROUND macro in an event table
2348 You must call wxEraseEvent::GetDC and use the returned device context if it is
2349 non-@NULL. If it is @NULL, create your own temporary wxClientDC object.
2352 Use the device context returned by GetDC to draw on, don't create
2353 a wxPaintDC in the event handler.
2355 @beginEventTable{wxEraseEvent}
2356 @event{EVT_ERASE_BACKGROUND(func)}
2357 Process a @c wxEVT_ERASE_BACKGROUND event.
2363 @see @ref overview_events
2365 class wxEraseEvent
: public wxEvent
2371 wxEraseEvent(int id
= 0, wxDC
* dc
= NULL
);
2374 Returns the device context associated with the erase event to draw on.
2376 wxDC
* GetDC() const;
2384 A focus event is sent when a window's focus changes. The window losing focus
2385 receives a "kill focus" event while the window gaining it gets a "set focus" one.
2387 Notice that the set focus event happens both when the user gives focus to the
2388 window (whether using the mouse or keyboard) and when it is done from the
2389 program itself using wxWindow::SetFocus.
2391 @beginEventTable{wxFocusEvent}
2392 @event{EVT_SET_FOCUS(func)}
2393 Process a @c wxEVT_SET_FOCUS event.
2394 @event{EVT_KILL_FOCUS(func)}
2395 Process a @c wxEVT_KILL_FOCUS event.
2401 @see @ref overview_events
2403 class wxFocusEvent
: public wxEvent
2409 wxFocusEvent(wxEventType eventType
= wxEVT_NULL
, int id
= 0);
2412 Returns the window associated with this event, that is the window which had the
2413 focus before for the @c wxEVT_SET_FOCUS event and the window which is
2414 going to receive focus for the @c wxEVT_KILL_FOCUS one.
2416 Warning: the window pointer may be @NULL!
2418 wxWindow
*GetWindow() const;
2424 @class wxChildFocusEvent
2426 A child focus event is sent to a (parent-)window when one of its child windows
2427 gains focus, so that the window could restore the focus back to its corresponding
2428 child if it loses it now and regains later.
2430 Notice that child window is the direct child of the window receiving event.
2431 Use wxWindow::FindFocus() to retreive the window which is actually getting focus.
2433 @beginEventTable{wxChildFocusEvent}
2434 @event{EVT_CHILD_FOCUS(func)}
2435 Process a @c wxEVT_CHILD_FOCUS event.
2441 @see @ref overview_events
2443 class wxChildFocusEvent
: public wxCommandEvent
2450 The direct child which is (or which contains the window which is) receiving
2453 wxChildFocusEvent(wxWindow
* win
= NULL
);
2456 Returns the direct child which receives the focus, or a (grand-)parent of the
2457 control receiving the focus.
2459 To get the actually focused control use wxWindow::FindFocus.
2461 wxWindow
*GetWindow() const;
2467 @class wxMouseCaptureLostEvent
2469 An mouse capture lost event is sent to a window that obtained mouse capture,
2470 which was subsequently loss due to "external" event, for example when a dialog
2471 box is shown or if another application captures the mouse.
2473 If this happens, this event is sent to all windows that are on capture stack
2474 (i.e. called CaptureMouse, but didn't call ReleaseMouse yet). The event is
2475 not sent if the capture changes because of a call to CaptureMouse or
2478 This event is currently emitted under Windows only.
2480 @beginEventTable{wxMouseCaptureLostEvent}
2481 @event{EVT_MOUSE_CAPTURE_LOST(func)}
2482 Process a @c wxEVT_MOUSE_CAPTURE_LOST event.
2490 @see wxMouseCaptureChangedEvent, @ref overview_events,
2491 wxWindow::CaptureMouse, wxWindow::ReleaseMouse, wxWindow::GetCapture
2493 class wxMouseCaptureLostEvent
: public wxEvent
2499 wxMouseCaptureLostEvent(wxWindowID windowId
= 0);
2505 @class wxNotifyEvent
2507 This class is not used by the event handlers by itself, but is a base class
2508 for other event classes (such as wxBookCtrlEvent).
2510 It (or an object of a derived class) is sent when the controls state is being
2511 changed and allows the program to wxNotifyEvent::Veto() this change if it wants
2512 to prevent it from happening.
2517 @see wxBookCtrlEvent
2519 class wxNotifyEvent
: public wxCommandEvent
2523 Constructor (used internally by wxWidgets only).
2525 wxNotifyEvent(wxEventType eventType
= wxEVT_NULL
, int id
= 0);
2528 This is the opposite of Veto(): it explicitly allows the event to be processed.
2529 For most events it is not necessary to call this method as the events are allowed
2530 anyhow but some are forbidden by default (this will be mentioned in the corresponding
2536 Returns @true if the change is allowed (Veto() hasn't been called) or @false
2537 otherwise (if it was).
2539 bool IsAllowed() const;
2542 Prevents the change announced by this event from happening.
2544 It is in general a good idea to notify the user about the reasons for vetoing
2545 the change because otherwise the applications behaviour (which just refuses to
2546 do what the user wants) might be quite surprising.
2553 @class wxThreadEvent
2555 This class adds some simple functionalities to wxCommandEvent coinceived
2556 for inter-threads communications.
2558 This event is not natively emitted by any control/class: this is just
2559 an helper class for the user.
2560 Its most important feature is the GetEventCategory() implementation which
2561 allows thread events to @b NOT be processed by wxEventLoopBase::YieldFor calls
2562 (unless the @c wxEVT_CATEGORY_THREAD is specified - which is never in wx code).
2567 @see @ref overview_thread, wxEventLoopBase::YieldFor
2569 class wxThreadEvent
: public wxCommandEvent
2575 wxThreadEvent(wxEventType eventType
= wxEVT_COMMAND_THREAD
, int id
= wxID_ANY
);
2578 Clones this event making sure that all internal members which use
2579 COW (only @c m_commandString for now; see @ref overview_refcount)
2580 are unshared (see wxObject::UnShare).
2582 virtual wxEvent
*Clone() const;
2585 Returns @c wxEVT_CATEGORY_THREAD.
2587 This is important to avoid unwanted processing of thread events
2588 when calling wxEventLoopBase::YieldFor().
2590 virtual wxEventCategory
GetEventCategory() const;
2597 A help event is sent when the user has requested context-sensitive help.
2598 This can either be caused by the application requesting context-sensitive help mode
2599 via wxContextHelp, or (on MS Windows) by the system generating a WM_HELP message when
2600 the user pressed F1 or clicked on the query button in a dialog caption.
2602 A help event is sent to the window that the user clicked on, and is propagated
2603 up the window hierarchy until the event is processed or there are no more event
2606 The application should call wxEvent::GetId to check the identity of the
2607 clicked-on window, and then either show some suitable help or call wxEvent::Skip()
2608 if the identifier is unrecognised.
2610 Calling Skip is important because it allows wxWidgets to generate further
2611 events for ancestors of the clicked-on window. Otherwise it would be impossible to
2612 show help for container windows, since processing would stop after the first window
2615 @beginEventTable{wxHelpEvent}
2616 @event{EVT_HELP(id, func)}
2617 Process a @c wxEVT_HELP event.
2618 @event{EVT_HELP_RANGE(id1, id2, func)}
2619 Process a @c wxEVT_HELP event for a range of ids.
2625 @see wxContextHelp, wxDialog, @ref overview_events
2627 class wxHelpEvent
: public wxCommandEvent
2631 Indicates how a wxHelpEvent was generated.
2635 Origin_Unknown
, /**< unrecognized event source. */
2636 Origin_Keyboard
, /**< event generated from F1 key press. */
2638 /** event generated by wxContextHelp or from the [?] button on
2639 the title bar (Windows). */
2646 wxHelpEvent(wxEventType type
= wxEVT_NULL
,
2647 wxWindowID winid
= 0,
2648 const wxPoint
& pt
= wxDefaultPosition
,
2649 wxHelpEvent::Origin origin
= Origin_Unknown
);
2652 Returns the origin of the help event which is one of the ::wxHelpEventOrigin
2655 The application may handle events generated using the keyboard or mouse
2656 differently, e.g. by using wxGetMousePosition() for the mouse events.
2660 wxHelpEvent::Origin
GetOrigin() const;
2663 Returns the left-click position of the mouse, in screen coordinates.
2664 This allows the application to position the help appropriately.
2666 const wxPoint
& GetPosition() const;
2669 Set the help event origin, only used internally by wxWidgets normally.
2673 void SetOrigin(wxHelpEvent::Origin origin
);
2676 Sets the left-click position of the mouse, in screen coordinates.
2678 void SetPosition(const wxPoint
& pt
);
2684 @class wxScrollEvent
2686 A scroll event holds information about events sent from stand-alone
2687 scrollbars (see wxScrollBar) and sliders (see wxSlider).
2689 Note that scrolled windows send the wxScrollWinEvent which does not derive from
2690 wxCommandEvent, but from wxEvent directly - don't confuse these two kinds of
2691 events and use the event table macros mentioned below only for the scrollbar-like
2694 @section scrollevent_diff The difference between EVT_SCROLL_THUMBRELEASE and EVT_SCROLL_CHANGED
2696 The EVT_SCROLL_THUMBRELEASE event is only emitted when actually dragging the thumb
2697 using the mouse and releasing it (This EVT_SCROLL_THUMBRELEASE event is also followed
2698 by an EVT_SCROLL_CHANGED event).
2700 The EVT_SCROLL_CHANGED event also occurs when using the keyboard to change the thumb
2701 position, and when clicking next to the thumb (In all these cases the EVT_SCROLL_THUMBRELEASE
2702 event does not happen).
2704 In short, the EVT_SCROLL_CHANGED event is triggered when scrolling/ moving has finished
2705 independently of the way it had started. Please see the widgets sample ("Slider" page)
2706 to see the difference between EVT_SCROLL_THUMBRELEASE and EVT_SCROLL_CHANGED in action.
2709 Note that unless specifying a scroll control identifier, you will need to test for scrollbar
2710 orientation with wxScrollEvent::GetOrientation, since horizontal and vertical scroll events
2711 are processed using the same event handler.
2713 @beginEventTable{wxScrollEvent}
2714 You can use EVT_COMMAND_SCROLL... macros with window IDs for when intercepting
2715 scroll events from controls, or EVT_SCROLL... macros without window IDs for
2716 intercepting scroll events from the receiving window -- except for this, the
2717 macros behave exactly the same.
2718 @event{EVT_SCROLL(func)}
2719 Process all scroll events.
2720 @event{EVT_SCROLL_TOP(func)}
2721 Process wxEVT_SCROLL_TOP scroll-to-top events (minimum position).
2722 @event{EVT_SCROLL_BOTTOM(func)}
2723 Process wxEVT_SCROLL_BOTTOM scroll-to-bottom events (maximum position).
2724 @event{EVT_SCROLL_LINEUP(func)}
2725 Process wxEVT_SCROLL_LINEUP line up events.
2726 @event{EVT_SCROLL_LINEDOWN(func)}
2727 Process wxEVT_SCROLL_LINEDOWN line down events.
2728 @event{EVT_SCROLL_PAGEUP(func)}
2729 Process wxEVT_SCROLL_PAGEUP page up events.
2730 @event{EVT_SCROLL_PAGEDOWN(func)}
2731 Process wxEVT_SCROLL_PAGEDOWN page down events.
2732 @event{EVT_SCROLL_THUMBTRACK(func)}
2733 Process wxEVT_SCROLL_THUMBTRACK thumbtrack events (frequent events sent as the
2734 user drags the thumbtrack).
2735 @event{EVT_SCROLL_THUMBRELEASE(func)}
2736 Process wxEVT_SCROLL_THUMBRELEASE thumb release events.
2737 @event{EVT_SCROLL_CHANGED(func)}
2738 Process wxEVT_SCROLL_CHANGED end of scrolling events (MSW only).
2739 @event{EVT_COMMAND_SCROLL(id, func)}
2740 Process all scroll events.
2741 @event{EVT_COMMAND_SCROLL_TOP(id, func)}
2742 Process wxEVT_SCROLL_TOP scroll-to-top events (minimum position).
2743 @event{EVT_COMMAND_SCROLL_BOTTOM(id, func)}
2744 Process wxEVT_SCROLL_BOTTOM scroll-to-bottom events (maximum position).
2745 @event{EVT_COMMAND_SCROLL_LINEUP(id, func)}
2746 Process wxEVT_SCROLL_LINEUP line up events.
2747 @event{EVT_COMMAND_SCROLL_LINEDOWN(id, func)}
2748 Process wxEVT_SCROLL_LINEDOWN line down events.
2749 @event{EVT_COMMAND_SCROLL_PAGEUP(id, func)}
2750 Process wxEVT_SCROLL_PAGEUP page up events.
2751 @event{EVT_COMMAND_SCROLL_PAGEDOWN(id, func)}
2752 Process wxEVT_SCROLL_PAGEDOWN page down events.
2753 @event{EVT_COMMAND_SCROLL_THUMBTRACK(id, func)}
2754 Process wxEVT_SCROLL_THUMBTRACK thumbtrack events (frequent events sent
2755 as the user drags the thumbtrack).
2756 @event{EVT_COMMAND_SCROLL_THUMBRELEASE(func)}
2757 Process wxEVT_SCROLL_THUMBRELEASE thumb release events.
2758 @event{EVT_COMMAND_SCROLL_CHANGED(func)}
2759 Process wxEVT_SCROLL_CHANGED end of scrolling events (MSW only).
2765 @see wxScrollBar, wxSlider, wxSpinButton, wxScrollWinEvent, @ref overview_events
2767 class wxScrollEvent
: public wxCommandEvent
2773 wxScrollEvent(wxEventType commandType
= wxEVT_NULL
, int id
= 0, int pos
= 0,
2774 int orientation
= 0);
2777 Returns wxHORIZONTAL or wxVERTICAL, depending on the orientation of the
2780 int GetOrientation() const;
2783 Returns the position of the scrollbar.
2785 int GetPosition() const;
2789 See wxIdleEvent::SetMode() for more info.
2793 /** Send idle events to all windows */
2796 /** Send idle events to windows that have the wxWS_EX_PROCESS_IDLE flag specified */
2797 wxIDLE_PROCESS_SPECIFIED
2804 This class is used for idle events, which are generated when the system becomes
2805 idle. Note that, unless you do something specifically, the idle events are not
2806 sent if the system remains idle once it has become it, e.g. only a single idle
2807 event will be generated until something else resulting in more normal events
2808 happens and only then is the next idle event sent again.
2810 If you need to ensure a continuous stream of idle events, you can either use
2811 wxIdleEvent::RequestMore method in your handler or call wxWakeUpIdle() periodically
2812 (for example from a timer event handler), but note that both of these approaches
2813 (and especially the first one) increase the system load and so should be avoided
2816 By default, idle events are sent to all windows (and also wxApp, as usual).
2817 If this is causing a significant overhead in your application, you can call
2818 wxIdleEvent::SetMode with the value wxIDLE_PROCESS_SPECIFIED, and set the
2819 wxWS_EX_PROCESS_IDLE extra window style for every window which should receive
2822 @beginEventTable{wxIdleEvent}
2823 @event{EVT_IDLE(func)}
2824 Process a @c wxEVT_IDLE event.
2830 @see @ref overview_events, wxUpdateUIEvent, wxWindow::OnInternalIdle
2832 class wxIdleEvent
: public wxEvent
2841 Returns @true if it is appropriate to send idle events to this window.
2843 This function looks at the mode used (see wxIdleEvent::SetMode),
2844 and the wxWS_EX_PROCESS_IDLE style in @a window to determine whether idle
2845 events should be sent to this window now.
2847 By default this will always return @true because the update mode is initially
2848 wxIDLE_PROCESS_ALL. You can change the mode to only send idle events to
2849 windows with the wxWS_EX_PROCESS_IDLE extra window style set.
2853 static bool CanSend(wxWindow
* window
);
2856 Static function returning a value specifying how wxWidgets will send idle
2857 events: to all windows, or only to those which specify that they
2858 will process the events.
2862 static wxIdleMode
GetMode();
2865 Returns @true if the OnIdle function processing this event requested more
2870 bool MoreRequested() const;
2873 Tells wxWidgets that more processing is required.
2875 This function can be called by an OnIdle handler for a window or window event
2876 handler to indicate that wxApp::OnIdle should forward the OnIdle event once
2877 more to the application windows.
2879 If no window calls this function during OnIdle, then the application will
2880 remain in a passive event loop (not calling OnIdle) until a new event is
2881 posted to the application by the windowing system.
2883 @see MoreRequested()
2885 void RequestMore(bool needMore
= true);
2888 Static function for specifying how wxWidgets will send idle events: to
2889 all windows, or only to those which specify that they will process the events.
2892 Can be one of the ::wxIdleMode values.
2893 The default is wxIDLE_PROCESS_ALL.
2895 static void SetMode(wxIdleMode mode
);
2901 @class wxInitDialogEvent
2903 A wxInitDialogEvent is sent as a dialog or panel is being initialised.
2904 Handlers for this event can transfer data to the window.
2906 The default handler calls wxWindow::TransferDataToWindow.
2908 @beginEventTable{wxInitDialogEvent}
2909 @event{EVT_INIT_DIALOG(func)}
2910 Process a @c wxEVT_INIT_DIALOG event.
2916 @see @ref overview_events
2918 class wxInitDialogEvent
: public wxEvent
2924 wxInitDialogEvent(int id
= 0);
2930 @class wxWindowDestroyEvent
2932 This event is sent as early as possible during the window destruction
2935 For the top level windows, as early as possible means that this is done by
2936 wxFrame or wxDialog destructor, i.e. after the destructor of the derived
2937 class was executed and so any methods specific to the derived class can't
2938 be called any more from this event handler. If you need to do this, you
2939 must call wxWindow::SendDestroyEvent() from your derived class destructor.
2941 For the child windows, this event is generated just before deleting the
2942 window from wxWindow::Destroy() (which is also called when the parent
2943 window is deleted) or from the window destructor if operator @c delete was
2944 used directly (which is not recommended for this very reason).
2946 It is usually pointless to handle this event in the window itself but it ca
2947 be very useful to receive notifications about the window destruction in the
2948 parent window or in any other object interested in this window.
2953 @see @ref overview_events, wxWindowCreateEvent
2955 class wxWindowDestroyEvent
: public wxCommandEvent
2961 wxWindowDestroyEvent(wxWindow
* win
= NULL
);
2963 /// Retutn the window being destroyed.
2964 wxWindow
*GetWindow() const;
2969 @class wxNavigationKeyEvent
2971 This event class contains information about navigation events,
2972 generated by navigation keys such as tab and page down.
2974 This event is mainly used by wxWidgets implementations.
2975 A wxNavigationKeyEvent handler is automatically provided by wxWidgets
2976 when you make a class into a control container with the macro
2977 WX_DECLARE_CONTROL_CONTAINER.
2979 @beginEventTable{wxNavigationKeyEvent}
2980 @event{EVT_NAVIGATION_KEY(func)}
2981 Process a navigation key event.
2987 @see wxWindow::Navigate, wxWindow::NavigateIn
2989 class wxNavigationKeyEvent
: public wxEvent
2993 Flags which can be used with wxNavigationKeyEvent.
2995 enum wxNavigationKeyEventFlags
2997 IsBackward
= 0x0000,
3003 wxNavigationKeyEvent();
3004 wxNavigationKeyEvent(const wxNavigationKeyEvent
& event
);
3007 Returns the child that has the focus, or @NULL.
3009 wxWindow
* GetCurrentFocus() const;
3012 Returns @true if the navigation was in the forward direction.
3014 bool GetDirection() const;
3017 Returns @true if the navigation event was from a tab key.
3018 This is required for proper navigation over radio buttons.
3020 bool IsFromTab() const;
3023 Returns @true if the navigation event represents a window change
3024 (for example, from Ctrl-Page Down in a notebook).
3026 bool IsWindowChange() const;
3029 Sets the current focus window member.
3031 void SetCurrentFocus(wxWindow
* currentFocus
);
3034 Sets the direction to forward if @a direction is @true, or backward
3037 void SetDirection(bool direction
);
3040 Sets the flags for this event.
3041 The @a flags can be a combination of the ::wxNavigationKeyEventFlags values.
3043 void SetFlags(long flags
);
3046 Marks the navigation event as from a tab key.
3048 void SetFromTab(bool fromTab
);
3051 Marks the event as a window change event.
3053 void SetWindowChange(bool windowChange
);
3059 @class wxMouseCaptureChangedEvent
3061 An mouse capture changed event is sent to a window that loses its
3062 mouse capture. This is called even if wxWindow::ReleaseMouse
3063 was called by the application code. Handling this event allows
3064 an application to cater for unexpected capture releases which
3065 might otherwise confuse mouse handling code.
3069 @beginEventTable{wxMouseCaptureChangedEvent}
3070 @event{EVT_MOUSE_CAPTURE_CHANGED(func)}
3071 Process a @c wxEVT_MOUSE_CAPTURE_CHANGED event.
3077 @see wxMouseCaptureLostEvent, @ref overview_events,
3078 wxWindow::CaptureMouse, wxWindow::ReleaseMouse, wxWindow::GetCapture
3080 class wxMouseCaptureChangedEvent
: public wxEvent
3086 wxMouseCaptureChangedEvent(wxWindowID windowId
= 0,
3087 wxWindow
* gainedCapture
= NULL
);
3090 Returns the window that gained the capture, or @NULL if it was a
3091 non-wxWidgets window.
3093 wxWindow
* GetCapturedWindow() const;
3101 This event class contains information about window and session close events.
3103 The handler function for EVT_CLOSE is called when the user has tried to close a
3104 a frame or dialog box using the window manager (X) or system menu (Windows).
3105 It can also be invoked by the application itself programmatically, for example by
3106 calling the wxWindow::Close function.
3108 You should check whether the application is forcing the deletion of the window
3109 using wxCloseEvent::CanVeto. If this is @false, you @e must destroy the window
3110 using wxWindow::Destroy.
3112 If the return value is @true, it is up to you whether you respond by destroying
3115 If you don't destroy the window, you should call wxCloseEvent::Veto to
3116 let the calling code know that you did not destroy the window.
3117 This allows the wxWindow::Close function to return @true or @false depending
3118 on whether the close instruction was honoured or not.
3120 Example of a wxCloseEvent handler:
3123 void MyFrame::OnClose(wxCloseEvent& event)
3125 if ( event.CanVeto() && m_bFileNotSaved )
3127 if ( wxMessageBox("The file has not been saved... continue closing?",
3129 wxICON_QUESTION | wxYES_NO) != wxYES )
3136 Destroy(); // you may also do: event.Skip();
3137 // since the default event handler does call Destroy(), too
3141 The EVT_END_SESSION event is slightly different as it is sent by the system
3142 when the user session is ending (e.g. because of log out or shutdown) and
3143 so all windows are being forcefully closed. At least under MSW, after the
3144 handler for this event is executed the program is simply killed by the
3145 system. Because of this, the default handler for this event provided by
3146 wxWidgets calls all the usual cleanup code (including wxApp::OnExit()) so
3147 that it could still be executed and exit()s the process itself, without
3148 waiting for being killed. If this behaviour is for some reason undesirable,
3149 make sure that you define a handler for this event in your wxApp-derived
3150 class and do not call @c event.Skip() in it (but be aware that the system
3151 will still kill your application).
3153 @beginEventTable{wxCloseEvent}
3154 @event{EVT_CLOSE(func)}
3155 Process a close event, supplying the member function.
3156 This event applies to wxFrame and wxDialog classes.
3157 @event{EVT_QUERY_END_SESSION(func)}
3158 Process a query end session event, supplying the member function.
3159 This event can be handled in wxApp-derived class only.
3160 @event{EVT_END_SESSION(func)}
3161 Process an end session event, supplying the member function.
3162 This event can be handled in wxApp-derived class only.
3168 @see wxWindow::Close, @ref overview_windowdeletion
3170 class wxCloseEvent
: public wxEvent
3176 wxCloseEvent(wxEventType commandEventType
= wxEVT_NULL
, int id
= 0);
3179 Returns @true if you can veto a system shutdown or a window close event.
3180 Vetoing a window close event is not possible if the calling code wishes to
3181 force the application to exit, and so this function must be called to check this.
3183 bool CanVeto() const;
3186 Returns @true if the user is just logging off or @false if the system is
3187 shutting down. This method can only be called for end session and query end
3188 session events, it doesn't make sense for close window event.
3190 bool GetLoggingOff() const;
3193 Sets the 'can veto' flag.
3195 void SetCanVeto(bool canVeto
);
3198 Sets the 'logging off' flag.
3200 void SetLoggingOff(bool loggingOff
);
3203 Call this from your event handler to veto a system shutdown or to signal
3204 to the calling application that a window close did not happen.
3206 You can only veto a shutdown if CanVeto() returns @true.
3208 void Veto(bool veto
= true);
3216 This class is used for a variety of menu-related events. Note that
3217 these do not include menu command events, which are
3218 handled using wxCommandEvent objects.
3220 The default handler for @c wxEVT_MENU_HIGHLIGHT displays help
3221 text in the first field of the status bar.
3223 @beginEventTable{wxMenuEvent}
3224 @event{EVT_MENU_OPEN(func)}
3225 A menu is about to be opened. On Windows, this is only sent once for each
3226 navigation of the menubar (up until all menus have closed).
3227 @event{EVT_MENU_CLOSE(func)}
3228 A menu has been just closed.
3229 @event{EVT_MENU_HIGHLIGHT(id, func)}
3230 The menu item with the specified id has been highlighted: used to show
3231 help prompts in the status bar by wxFrame
3232 @event{EVT_MENU_HIGHLIGHT_ALL(func)}
3233 A menu item has been highlighted, i.e. the currently selected menu item has changed.
3239 @see wxCommandEvent, @ref overview_events
3241 class wxMenuEvent
: public wxEvent
3247 wxMenuEvent(wxEventType id
= wxEVT_NULL
, int id
= 0, wxMenu
* menu
= NULL
);
3250 Returns the menu which is being opened or closed. This method should only be
3251 used with the @c OPEN and @c CLOSE events and even for them the
3252 returned pointer may be @NULL in some ports.
3254 wxMenu
* GetMenu() const;
3257 Returns the menu identifier associated with the event.
3258 This method should be only used with the @c HIGHLIGHT events.
3260 int GetMenuId() const;
3263 Returns @true if the menu which is being opened or closed is a popup menu,
3264 @false if it is a normal one.
3266 This method should only be used with the @c OPEN and @c CLOSE events.
3268 bool IsPopup() const;
3274 An event being sent when the window is shown or hidden.
3276 Currently only wxMSW, wxGTK and wxOS2 generate such events.
3278 @onlyfor{wxmsw,wxgtk,wxos2}
3280 @beginEventTable{wxShowEvent}
3281 @event{EVT_SHOW(func)}
3282 Process a @c wxEVT_SHOW event.
3288 @see @ref overview_events, wxWindow::Show,
3292 class wxShowEvent
: public wxEvent
3298 wxShowEvent(int winid
= 0, bool show
= false);
3301 Set whether the windows was shown or hidden.
3303 void SetShow(bool show
);
3306 Return @true if the window has been shown, @false if it has been
3309 bool IsShown() const;
3312 @deprecated This function is deprecated in favour of IsShown().
3314 bool GetShow() const;
3320 @class wxIconizeEvent
3322 An event being sent when the frame is iconized (minimized) or restored.
3324 Currently only wxMSW and wxGTK generate such events.
3326 @onlyfor{wxmsw,wxgtk}
3328 @beginEventTable{wxIconizeEvent}
3329 @event{EVT_ICONIZE(func)}
3330 Process a @c wxEVT_ICONIZE event.
3336 @see @ref overview_events, wxTopLevelWindow::Iconize,
3337 wxTopLevelWindow::IsIconized
3339 class wxIconizeEvent
: public wxEvent
3345 wxIconizeEvent(int id
= 0, bool iconized
= true);
3348 Returns @true if the frame has been iconized, @false if it has been
3351 bool IsIconized() const;
3354 @deprecated This function is deprecated in favour of IsIconized().
3356 bool Iconized() const;
3364 A move event holds information about wxTopLevelWindow move change events.
3366 @beginEventTable{wxMoveEvent}
3367 @event{EVT_MOVE(func)}
3368 Process a @c wxEVT_MOVE event, which is generated when a window is moved.
3369 @event{EVT_MOVE_START(func)}
3370 Process a @c wxEVT_MOVE_START event, which is generated when the user starts
3371 to move or size a window. wxMSW only.
3372 @event{EVT_MOVE_END(func)}
3373 Process a @c wxEVT_MOVE_END event, which is generated when the user stops
3374 moving or sizing a window. wxMSW only.
3380 @see wxPoint, @ref overview_events
3382 class wxMoveEvent
: public wxEvent
3388 wxMoveEvent(const wxPoint
& pt
, int id
= 0);
3391 Returns the position of the window generating the move change event.
3393 wxPoint
GetPosition() const;
3400 A size event holds information about size change events of wxWindow.
3402 The EVT_SIZE handler function will be called when the window has been resized.
3404 You may wish to use this for frames to resize their child windows as appropriate.
3406 Note that the size passed is of the whole window: call wxWindow::GetClientSize
3407 for the area which may be used by the application.
3409 When a window is resized, usually only a small part of the window is damaged
3410 and you may only need to repaint that area. However, if your drawing depends on the
3411 size of the window, you may need to clear the DC explicitly and repaint the whole window.
3412 In which case, you may need to call wxWindow::Refresh to invalidate the entire window.
3414 @beginEventTable{wxSizeEvent}
3415 @event{EVT_SIZE(func)}
3416 Process a @c wxEVT_SIZE event.
3422 @see wxSize, @ref overview_events
3424 class wxSizeEvent
: public wxEvent
3430 wxSizeEvent(const wxSize
& sz
, int id
= 0);
3433 Returns the entire size of the window generating the size change event.
3435 wxSize
GetSize() const;
3441 @class wxSetCursorEvent
3443 A wxSetCursorEvent is generated from wxWindow when the mouse cursor is about
3444 to be set as a result of mouse motion.
3446 This event gives the application the chance to perform specific mouse cursor
3447 processing based on the current position of the mouse within the window.
3448 Use wxSetCursorEvent::SetCursor to specify the cursor you want to be displayed.
3450 @beginEventTable{wxSetCursorEvent}
3451 @event{EVT_SET_CURSOR(func)}
3452 Process a @c wxEVT_SET_CURSOR event.
3458 @see ::wxSetCursor, wxWindow::wxSetCursor
3460 class wxSetCursorEvent
: public wxEvent
3464 Constructor, used by the library itself internally to initialize the event
3467 wxSetCursorEvent(wxCoord x
= 0, wxCoord y
= 0);
3470 Returns a reference to the cursor specified by this event.
3472 const wxCursor
& GetCursor() const;
3475 Returns the X coordinate of the mouse in client coordinates.
3477 wxCoord
GetX() const;
3480 Returns the Y coordinate of the mouse in client coordinates.
3482 wxCoord
GetY() const;
3485 Returns @true if the cursor specified by this event is a valid cursor.
3487 @remarks You cannot specify wxNullCursor with this event, as it is not
3488 considered a valid cursor.
3490 bool HasCursor() const;
3493 Sets the cursor associated with this event.
3495 void SetCursor(const wxCursor
& cursor
);
3500 // ============================================================================
3501 // Global functions/macros
3502 // ============================================================================
3504 /** @addtogroup group_funcmacro_events */
3508 A value uniquely identifying the type of the event.
3510 The values of this type should only be created using wxNewEventType().
3512 See the macro DEFINE_EVENT_TYPE() for more info.
3514 @see @ref overview_events_introduction
3516 typedef int wxEventType
;
3519 A special event type usually used to indicate that some wxEvent has yet
3522 wxEventType wxEVT_NULL
;
3525 Initializes a new event type using wxNewEventType().
3527 @deprecated Use wxDEFINE_EVENT() instead
3529 #define DEFINE_EVENT_TYPE(name) const wxEventType name = wxNewEventType();
3532 Generates a new unique event type.
3534 Usually this function is only used by wxDEFINE_EVENT() and not called
3537 wxEventType
wxNewEventType();
3540 Define a new event type associated with the specified event class.
3542 This macro defines a new unique event type @a name associated with the
3547 wxDEFINE_EVENT(MY_COMMAND_EVENT, wxCommandEvent);
3549 class MyCustomEvent : public wxEvent { ... };
3550 wxDEFINE_EVENT(MY_CUSTOM_EVENT, MyCustomEvent);
3553 @see wxDECLARE_EVENT(), @ref overview_events_custom
3555 #define wxDEFINE_EVENT(name, cls) \
3556 const wxEventTypeTag< cls > name(wxNewEventType())
3559 Declares a custom event type.
3561 This macro declares a variable called @a name which must be defined
3562 elsewhere using wxDEFINE_EVENT().
3564 The class @a cls must be the wxEvent-derived class associated with the
3565 events of this type and its full declaration must be visible from the point
3566 of use of this macro.
3568 #define wxDECLARE_EVENT(name, cls) \
3569 wxDECLARE_EXPORTED_EVENT(wxEMPTY_PARAMETER_VALUE, name, cls)
3572 Variant of wxDECLARE_EVENT() used for event types defined inside a shared
3575 This is mostly used by wxWidgets internally, e.g.
3577 wxDECLARE_EXPORTED_EVENT(WXDLLIMPEXP_CORE, wxEVT_COMMAND_BUTTON_CLICKED, wxCommandEvent)
3580 #define wxDECLARE_EXPORTED_EVENT( expdecl, name, cls ) \
3581 extern const expdecl wxEventTypeTag< cls > name;
3584 Helper macro for definition of custom event table macros.
3586 This macro must only be used if wxEVENTS_COMPATIBILITY_2_8 is 1, otherwise
3587 it is better and more clear to just use the address of the function
3588 directly as this is all this macro does in this case. However it needs to
3589 explicitly cast @a func to @a functype, which is the type of wxEvtHandler
3590 member function taking the custom event argument when
3591 wxEVENTS_COMPATIBILITY_2_8 is 0.
3593 See wx__DECLARE_EVT0 for an example of use.
3595 @see @ref overview_events_custom_ownclass
3597 #define wxEVENT_HANDLER_CAST(functype, func) (&func)
3601 These macros are used to define event table macros for handling custom
3606 class MyEvent : public wxEvent { ... };
3608 // note that this is not necessary unless using old compilers: for the
3609 // reasonably new ones just use &func instead of MyEventHandler(func)
3610 typedef void (wxEvtHandler::*MyEventFunction)(MyEvent&);
3611 #define MyEventHandler(func) wxEVENT_HANDLER_CAST(MyEventFunction, func)
3613 wxDEFINE_EVENT(MY_EVENT_TYPE, MyEvent);
3615 #define EVT_MY(id, func) \
3616 wx__DECLARE_EVT1(MY_EVENT_TYPE, id, MyEventHandler(func))
3620 BEGIN_EVENT_TABLE(MyFrame, wxFrame)
3621 EVT_MY(wxID_ANY, MyFrame::OnMyEvent)
3626 The event type to handle.
3628 The identifier of events to handle.
3630 The first identifier of the range.
3632 The second identifier of the range.
3634 The event handler method.
3636 #define wx__DECLARE_EVT2(evt, id1, id2, fn) \
3637 DECLARE_EVENT_TABLE_ENTRY(evt, id1, id2, fn, NULL),
3638 #define wx__DECLARE_EVT1(evt, id, fn) \
3639 wx__DECLARE_EVT2(evt, id, wxID_ANY, fn)
3640 #define wx__DECLARE_EVT0(evt, fn) \
3641 wx__DECLARE_EVT1(evt, wxID_ANY, fn)
3646 Use this macro inside a class declaration to declare a @e static event table
3649 In the implementation file you'll need to use the BEGIN_EVENT_TABLE()
3650 and the END_EVENT_TABLE() macros, plus some additional @c EVT_xxx macro
3653 @see @ref overview_events_eventtables
3655 #define DECLARE_EVENT_TABLE()
3658 Use this macro in a source file to start listing @e static event handlers
3659 for a specific class.
3661 Use END_EVENT_TABLE() to terminate the event-declaration block.
3663 @see @ref overview_events_eventtables
3665 #define BEGIN_EVENT_TABLE(theClass, baseClass)
3668 Use this macro in a source file to end listing @e static event handlers
3669 for a specific class.
3671 Use BEGIN_EVENT_TABLE() to start the event-declaration block.
3673 @see @ref overview_events_eventtables
3675 #define END_EVENT_TABLE()
3678 In a GUI application, this function posts @a event to the specified @e dest
3679 object using wxEvtHandler::AddPendingEvent().
3681 Otherwise, it dispatches @a event immediately using
3682 wxEvtHandler::ProcessEvent(). See the respective documentation for details
3683 (and caveats). Because of limitation of wxEvtHandler::AddPendingEvent()
3684 this function is not thread-safe for event objects having wxString fields,
3685 use wxQueueEvent() instead.
3689 void wxPostEvent(wxEvtHandler
* dest
, const wxEvent
& event
);
3692 Queue an event for processing on the given object.
3694 This is a wrapper around wxEvtHandler::QueueEvent(), see its documentation
3700 The object to queue the event on, can't be @c NULL.
3702 The heap-allocated and non-@c NULL event to queue, the function takes
3705 void wxQueueEvent(wxEvtHandler
* dest
, wxEvent
*event
);