Added EVT_GRID_EDITOR_CREATED and wxGridEditorCreatedEvent so the user

[wxWidgets.git] / docs / latex / wx / app.tex

diff --git a/docs/latex/wx/app.tex b/docs/latex/wx/app.tex
index b5e7d313404f89ff0c34b5f86645a0c016be7a7c..ec2ac10d7f32ae5ae0366f126ea01608db864801 100644 (file)
--- a/docs/latex/wx/app.tex
+++ b/docs/latex/wx/app.tex
@@ -38,8 +38,9 @@ a reference to your application object) to be visible to other files.
 
 Constructor. Called implicitly with a definition of a wxApp object.
 
 
 Constructor. Called implicitly with a definition of a wxApp object.
 

-The argument is a language identifier; this is an experimental
-feature and will be expanded and documented in future versions.
+% VZ: there is no such feature so far...
+% The argument is a language identifier; this is an experimental
+% feature and will be expanded and documented in future versions.

 
 \membersection{wxApp::\destruct{wxApp}}
 
 
 \membersection{wxApp::\destruct{wxApp}}
 


@@ -133,7 +134,7 @@ otherwise.
 
 \membersection{wxApp::GetTopWindow}\label{wxappgettopwindow}
 
 
 \membersection{wxApp::GetTopWindow}\label{wxappgettopwindow}
 

-\constfunc{wxWindow *}{GetTopWindow}{\void}
+\constfunc{virtual wxWindow *}{GetTopWindow}{\void}

 
 Returns a pointer to the top window.
 
 
 Returns a pointer to the top window.
 


@@ -233,6 +234,23 @@ If you use this member, you can selectively consume keypress events by calling\r
 \helpref{wxKeyEvent}{wxkeyevent}, \helpref{wxWindow::OnChar}{wxwindowonchar},\rtfsp
 \helpref{wxWindow::OnCharHook}{wxwindowoncharhook}, \helpref{wxDialog::OnCharHook}{wxdialogoncharhook}
 
 \helpref{wxKeyEvent}{wxkeyevent}, \helpref{wxWindow::OnChar}{wxwindowonchar},\rtfsp
 \helpref{wxWindow::OnCharHook}{wxwindowoncharhook}, \helpref{wxDialog::OnCharHook}{wxdialogoncharhook}
 

+\membersection{wxApp::OnFatalException}\label{wxapponfatalexception}
+
+\func{void}{OnFatalException}{\void}
+
+This function may be called if something fatal happens: an unhandled
+exception under Win32 or a a fatal signal under Unix, for example. However,
+this will not happen by default: you have to explicitly call 
+\helpref{wxHandleFatalExceptions}{wxhandlefatalexceptions} to enable this.
+
+Generally speaking, this function should only show a message to the user and
+return. You may attempt to save unsaved data but this is not guaranteed to
+work and, in fact, probably won't.
+
+\wxheading{See also}
+
+\helpref{wxHandleFatalExcetions}{wxhandlefatalexceptions}
+

 \membersection{wxApp::OnIdle}\label{wxapponidle}
 
 \func{void}{OnIdle}{\param{wxIdleEvent\& }{event}}
 \membersection{wxApp::OnIdle}\label{wxapponidle}
 
 \func{void}{OnIdle}{\param{wxIdleEvent\& }{event}}


@@ -440,7 +458,7 @@ deleted. If FALSE, the application will continue to run.}
 
 Sets the `top' window. You can call this from within \helpref{wxApp::OnInit}{wxapponinit} to
 let wxWindows know which is the main window. You don't have to set the top window;
 
 Sets the `top' window. You can call this from within \helpref{wxApp::OnInit}{wxapponinit} to
 let wxWindows know which is the main window. You don't have to set the top window;

-it's only a convenience so that (for example) certain dialogs without parents can use a
+it is only a convenience so that (for example) certain dialogs without parents can use a

 specific window as the top window. If no top window is specified by the application,
 wxWindows just uses the first frame or dialog in its top-level window list, when it
 needs to use the top window.
 specific window as the top window. If no top window is specified by the application,
 wxWindows just uses the first frame or dialog in its top-level window list, when it
 needs to use the top window.