X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/ccaaf5b08351d01b9ed1a83c0dc81764435cb4cc..93fa67c0e6124d2657488971800c8fd068dc0d0e:/docs/latex/wx/evthand.tex diff --git a/docs/latex/wx/evthand.tex b/docs/latex/wx/evthand.tex index 84bd8b92b4..e891d4f826 100644 --- a/docs/latex/wx/evthand.tex +++ b/docs/latex/wx/evthand.tex @@ -36,9 +36,7 @@ each other. \func{virtual void}{AddPendingEvent}{\param{wxEvent\& }{event}} -Adds an event to be processed later. The function will return immediately and the -event will get processed in idle time using the \helpref{wxEvtHandler::ProcessEvent}{wxevthandlerprocessevent} -method. +This function posts an event to be processed later. \wxheading{Parameters} @@ -46,34 +44,37 @@ method. \wxheading{Remarks} -Note that this requires that the event has a fully implemented Clone() -method so that the event can be duplicated and stored until it gets processed later. -Not all events in wxWindows currently have a fully implemented Clone() method, -so you may have to look at the source to verify this. +The difference between sending an event (using the +\helpref{ProcessEvent}{wxevthandlerprocessevent} method) and posting it is +that in the first case the event is processed before the function returns, +while in the second case, the function returns immediately and the event will +be processed sometime later (usually during the next event loop iteration). -This methods automatically wakes up idle handling even if the underlying window -system is currently idle anyway and thus would not send any idle events. (Waking -up the idle handling is done calling \helpref{::wxWakeUpIdle}{wxwakeupidle}.) +A copy of {\it event} is made by the function, so the original can be deleted +as soon as function returns (it is common that the original is created on the +stack). This requires that the \helpref{wxEvent::Clone}{wxeventclone} method +be implemented by {\it event} so that it can be duplicated and stored until +it gets processed. -This is also the method to call for inter-thread communication. In -a multi-threaded program, you will often have to inform the main GUI thread -about the status of other working threads and this has to be done using this -method - which also means that this method is thread safe by means of using -crtical sections where needed. +This is also the method to call for inter-thread communication---it will +post events safely between different threads which means that this method is +thread-safe by using critical sections where needed. In a multi-threaded +program, you often need to inform the main GUI thread about the status of +other working threads and such notification should be done using this method. -Furthermore, it may be noted that some ports of wxWindows will probably move -to using this method more and more in preference over calling ProcessEvent() -directly so as to avoid problems with reentrant code. +This method automatically wakes up idle handling if the underlying window +system is currently idle and thus would not send any idle events. (Waking +up idle handling is done calling \helpref{::wxWakeUpIdle}{wxwakeupidle}.) \membersection{wxEvtHandler::Connect}\label{wxevthandlerconnect} \func{void}{Connect}{\param{int}{ id}, \param{wxEventType }{eventType}, \param{wxObjectEventFunction}{ function}, - \param{wxObject*}{ userData = NULL}} + \param{wxObject*}{ userData = NULL}, \param{wxEvtHandler*}{ eventSink = NULL}} \func{void}{Connect}{\param{int}{ id}, \param{int}{ lastId}, \param{wxEventType }{eventType}, \param{wxObjectEventFunction}{ function}, - \param{wxObject*}{ userData = NULL}} + \param{wxObject*}{ userData = NULL}, \param{wxEvtHandler*}{ eventSink = NULL}} Connects the given function dynamically with the event handler, id and event type. This is an alternative to the use of static event tables. See the 'dynamic' sample for usage. @@ -90,6 +91,9 @@ is an alternative to the use of static event tables. See the 'dynamic' sample fo \docparam{userData}{Data to be associated with the event table entry.} +\docparam{eventSink}{Object whose member function should be called. If this is NULL, +'this' will be used.} + \wxheading{Example} \begin{verbatim} @@ -101,15 +105,15 @@ is an alternative to the use of static event tables. See the 'dynamic' sample fo \membersection{wxEvtHandler::Disconnect}\label{wxevthandlerdisconnect} \func{bool}{Disconnect}{\param{int}{ id}, - \param{wxEventType }{eventType = wxEVT_NULL}, \param{wxObjectEventFunction}{ function = NULL}, - \param{wxObject*}{ userData = NULL}} + \param{wxEventType }{eventType = wxEVT\_NULL}, \param{wxObjectEventFunction}{ function = NULL}, + \param{wxObject*}{ userData = NULL}, \param{wxEvtHandler*}{ eventSink = NULL}} \func{bool}{Disconnect}{\param{int}{ id}, \param{int}{ lastId = -1}, - \param{wxEventType }{eventType = wxEVT_NULL}, \param{wxObjectEventFunction}{ function = NULL}, - \param{wxObject*}{ userData = NULL}} + \param{wxEventType }{eventType = wxEVT\_NULL}, \param{wxObjectEventFunction}{ function = NULL}, + \param{wxObject*}{ userData = NULL}, \param{wxEvtHandler*}{ eventSink = NULL}} Disconnects the given function dynamically from the event handler, using the specified -parameters as search criteria and returning TRUE if a matching function has been +parameters as search criteria and returning true if a matching function has been found and removed. This method can only disconnect functions which have been added using the \helpref{wxEvtHandler::Connect}{wxevthandlerconnect} method. There is no way to disconnect functions connected using the (static) event tables. @@ -126,6 +130,8 @@ to disconnect functions connected using the (static) event tables. \docparam{userData}{Data associated with the event table entry.} +\docparam{eventSink}{Object whose member function should be called.} + \membersection{wxEvtHandler::GetClientData}\label{wxevthandlergetclientdata} \func{void* }{GetClientData}{\void} @@ -141,11 +147,22 @@ should be made available by deriving a new class with new data members. \helpref{wxEvtHandler::SetClientData}{wxevthandlersetclientdata} +\membersection{wxEvtHandler::GetClientObject}\label{wxevthandlergetclientobject} + +\constfunc{wxClientData*}{GetClientObject}{\void} + +Get a pointer to the user-supplied client data object. + +\wxheading{See also} + +\helpref{wxEvtHandler::SetClientObject}{wxevthandlersetclientobject}, +\helpref{wxClientData}{wxclientdata} + \membersection{wxEvtHandler::GetEvtHandlerEnabled}\label{wxevthandlergetevthandlerenabled} \func{bool}{GetEvtHandlerEnabled}{\void} -Returns TRUE if the event handler is enabled, FALSE otherwise. +Returns true if the event handler is enabled, false otherwise. \wxheading{See also} @@ -191,7 +208,7 @@ Processes an event, searching event tables and calling zero or more suitable eve \wxheading{Return value} -TRUE if a suitable event handler function was found and executed, and the function did not +true if a suitable event handler function was found and executed, and the function did not call \helpref{wxEvent::Skip}{wxeventskip}. \wxheading{Remarks} @@ -215,14 +232,14 @@ The normal order of event table searching is as follows: \item If the object is disabled (via a call to \helpref{wxEvtHandler::SetEvtHandlerEnabled}{wxevthandlersetevthandlerenabled}) the function skips to step (6). \item If the object is a wxWindow, {\bf ProcessEvent} is recursively called on the window's\rtfsp -\helpref{wxValidator}{wxvalidator}. If this returns TRUE, the function exits. +\helpref{wxValidator}{wxvalidator}. If this returns true, the function exits. \item {\bf SearchEventTable} is called for this event handler. If this fails, the base class table is tried, and so on until no more tables exist or an appropriate function was found, in which case the function exits. \item The search is applied down the entire chain of event handlers (usually the chain has a length of one). If this succeeds, the function exits. \item If the object is a wxWindow and the event is a wxCommandEvent, {\bf ProcessEvent} is -recursively applied to the parent window's event handler. If this returns TRUE, the function exits. +recursively applied to the parent window's event handler. If this returns true, the function exits. \item Finally, {\bf ProcessEvent} is called on the wxApp object. \end{enumerate} @@ -245,7 +262,7 @@ is found. \wxheading{Return value} -TRUE if a suitable event handler function was found and executed, and the function did not +true if a suitable event handler function was found and executed, and the function did not call \helpref{wxEvent::Skip}{wxeventskip}. \wxheading{Remarks} @@ -281,12 +298,25 @@ Sets user-supplied client data. Normally, any extra data the programmer wishes to associate with the object should be made available by deriving a new class -with new data members. +with new data members. You must not call this method and +\helpref{SetClientObject}{wxevthandlersetclientobject} on the +same class - only one of them. \wxheading{See also} \helpref{wxEvtHandler::GetClientData}{wxevthandlergetclientdata} +\membersection{wxEvtHandler::SetClientObject}\label{wxevthandlersetclientobject} + +\func{void}{SetClientObject}{\param{wxClientData* }{data}} + +Set the client data object. Any previous object will be deleted. + +\wxheading{See also} + +\helpref{wxEvtHandler::GetClientObject}{wxevthandlergetclientobject}, +\helpref{wxClientData}{wxclientdata} + \membersection{wxEvtHandler::SetEvtHandlerEnabled}\label{wxevthandlersetevthandlerenabled} \func{void}{SetEvtHandlerEnabled}{\param{bool }{enabled}} @@ -295,7 +325,7 @@ Enables or disables the event handler. \wxheading{Parameters} -\docparam{enabled}{TRUE if the event handler is to be enabled, FALSE if it is to be disabled.} +\docparam{enabled}{true if the event handler is to be enabled, false if it is to be disabled.} \wxheading{Remarks}