rolled back exceptions handling patch, it relied on incorrect assumption about vtables
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@34748 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
parent
32f65e50e7
commit
763b330106
@ -9,8 +9,6 @@ All:
|
||||
|
||||
- Fixed wxScopeGuard to work with VC++, documented it.
|
||||
- Fixed proxy handling in wxURL.
|
||||
- Changed exceptions handling to work under wxGTK, added
|
||||
virtual wxEvtHandler::DoHandleEvent()
|
||||
|
||||
wxMSW:
|
||||
|
||||
|
@ -197,20 +197,6 @@ different visuals, false otherwise.
|
||||
Returns the application's vendor name.
|
||||
|
||||
|
||||
\membersection{wxApp::HandleEvent}\label{wxapphandleevent}
|
||||
|
||||
\constfunc{virtual void}{HandleEvent}{\param{wxEvtHandler}{ *handler}, \param{wxEventFunction}{ func}, \param{wxEvent\& }{event}}
|
||||
|
||||
This function simply invokes the
|
||||
\helpref{DoHandleEvent}{wxevthandlerdohandleevent} method of event handler
|
||||
\arg{handler}, passing \arg{func} and \arg{event} as parameters. If an
|
||||
exception occurs, \helpref{OnExceptionInMainLoop}{wxapponexceptioninmainloop}
|
||||
is called by this function. You can override it to customize exceptions
|
||||
handling.
|
||||
|
||||
If you want to modify this behaviour, override this function.
|
||||
|
||||
|
||||
\membersection{wxApp::IsActive}\label{wxappisactive}
|
||||
|
||||
\constfunc{bool}{IsActive}{\void}
|
||||
@ -679,6 +665,18 @@ This function currently only has effect under GTK.
|
||||
|
||||
\docparam{flag}{If true, the app will use the best visual.}
|
||||
|
||||
|
||||
\membersection{wxApp::HandleEvent}\label{wxapphandleevent}
|
||||
|
||||
\constfunc{virtual void}{HandleEvent}{\param{wxEvtHandler}{ *handler}, \param{wxEventFunction}{ func}, \param{wxEvent\& }{event}}
|
||||
|
||||
This function simply invokes the given method \arg{func} of the specified
|
||||
event handler \arg{handler} with the \arg{event} as parameter. It exists solely
|
||||
to allow to catch the C++ exceptions which could be thrown by all event
|
||||
handlers in the application in one place: if you want to do this, override this
|
||||
function in your wxApp-derived class and add try/catch clause(s) to it.
|
||||
|
||||
|
||||
\membersection{wxApp::Yield}\label{wxappyield}
|
||||
|
||||
\func{bool}{Yield}{\param{bool}{ onlyIfNeeded = false}}
|
||||
|
@ -155,20 +155,6 @@ to disconnect functions connected using the (static) event tables.
|
||||
\perlnote{In wxPerl this function takes 3 arguments: \texttt{id,
|
||||
lastid, type}.}
|
||||
|
||||
\membersection{wxEvtHandler::DoHandleEvent}\label{wxevthandlerdohandleevent}
|
||||
|
||||
\func{virtual void}{DoHandleEvent}{\param{wxEventFunction}{ func}, \param{wxEvent\& }{event}}
|
||||
|
||||
This function simply invokes the given method \arg{func} of this
|
||||
event handler with the \arg{event} as parameter. It exists solely
|
||||
to allow to catch the C++ exceptions which could be thrown by this event
|
||||
handlers in one place: if you want to do this, override this
|
||||
function in your wxEvtHandler-derived class and add try/catch clause(s) to it.
|
||||
|
||||
Exceptions not caught at this level propagate to
|
||||
\helpref{wxApp::HandleEvent}{wxapphandleevent} which in turn calls
|
||||
\helpref{wxApp::OnExceptionInMainLoop}{wxapponexceptioninmainloop}.
|
||||
|
||||
\membersection{wxEvtHandler::GetClientData}\label{wxevthandlergetclientdata}
|
||||
|
||||
\func{void* }{GetClientData}{\void}
|
||||
|
Loading…
Reference in New Issue
Block a user