]> git.saurik.com Git - wxWidgets.git/blame - docs/latex/wx/tapp.tex
Corrected some spacing and typo errors.
[wxWidgets.git] / docs / latex / wx / tapp.tex
CommitLineData
a660d684
KB
1\section{wxApp overview}\label{wxappoverview}
2
3Classes: \helpref{wxApp}{wxapp}
4
fc2171bd 5A wxWidgets application does not have a {\it main} procedure; the equivalent is the
a660d684
KB
6\rtfsp\helpref{OnInit}{wxapponinit} member defined for a class derived from wxApp.\rtfsp
7\rtfsp{\it OnInit} will usually create a top window as a bare minimum.
8
fc2171bd 9Unlike in earlier versions of wxWidgets, OnInit does not return a frame. Instead it
cc81d32f 10returns a boolean value which indicates whether processing should continue (true) or not (false).
fc2171bd 11You call \helpref{wxApp::SetTopWindow}{wxappsettopwindow} to let wxWidgets know
a660d684
KB
12about the top window.
13
90a1a975
JS
14Note that the program's command line arguments, represented by {\it argc}
15and {\it argv}, are available from within wxApp member functions.
a660d684
KB
16
17An application closes by destroying all windows. Because all frames must
18be destroyed for the application to exit, it is advisable to use parent
19frames wherever possible when creating new frames, so that deleting the
20top level frame will automatically delete child frames. The alternative
f4fcc291 21is to explicitly delete child frames in the top-level frame's \helpref{wxCloseEvent}{wxcloseevent}\rtfsp
a660d684
KB
22handler.
23
24In emergencies the \helpref{wxExit}{wxexit} function can be called to kill the
1cbee0b4
VZ
25application however normally the applications shuts down automatically,
26\helpref{see below}{wxappshutdownoverview}.
a660d684
KB
27
28An example of defining an application follows:
29
30\begin{verbatim}
6e6110ee 31class DerivedApp : public wxApp
a660d684 32{
6e6110ee
VZ
33public:
34 virtual bool OnInit();
a660d684
KB
35};
36
37IMPLEMENT_APP(DerivedApp)
38
6e6110ee 39bool DerivedApp::OnInit()
a660d684 40{
90a1a975 41 wxFrame *the_frame = new wxFrame(NULL, ID_MYFRAME, argv[0]);
a660d684 42 ...
cc81d32f 43 the_frame->Show(true);
a660d684
KB
44 SetTopWindow(the_frame);
45
cc81d32f 46 return true;
a660d684
KB
47}
48\end{verbatim}
49
fc2171bd
JS
50Note the use of IMPLEMENT\_APP(appClass), which allows wxWidgets to dynamically create an instance of the application object
51at the appropriate point in wxWidgets initialization. Previous versions of wxWidgets used
a660d684
KB
52to rely on the creation of a global application object, but this is no longer recommended,
53because required global initialization may not have been performed at application object
54construction time.
55
56You can also use DECLARE\_APP(appClass) in a header file to declare the wxGetApp function which returns
41cd03e9
VZ
57a reference to the application object. Otherwise you can only use the global
58\texttt{wxTheApp} pointer which is of type \texttt{wxApp *}.
59
a660d684 60
1cbee0b4
VZ
61\subsection{Application shutdown}\label{wxappshutdownoverview}
62
63The application normally shuts down when the last of its top level windows is
64closed. This is normally the expected behaviour and means that it is enough to
65call \helpref{Close()}{wxwindowclose} in response to the {\tt "Exit"} menu
66command if your program has a single top level window. If this behaviour is not
67desirable \helpref{wxApp::SetExitOnFrameDelete}{wxappsetexitonframedelete} can
fc2171bd 68be called to change it. Note that starting from wxWidgets 2.3.3 such logic
1cbee0b4
VZ
69doesn't apply for the windows shown before the program enters the main loop: in
70other words, you can safely show a dialog from
71\helpref{wxApp::OnInit}{wxapponinit} and not be afraid that your application
72terminates when this dialog -- which is the last top level window for the
73moment -- is closed.
74
75
76Another aspect of the application shutdown is the \helpref{OnExit}{wxapponexit}
fc2171bd
JS
77which is called when the application exits but {\it before} wxWidgets cleans up
78its internal structures. Your should delete all wxWidgets object that your
1cbee0b4 79created by the time OnExit finishes. In particular, do {\bf not} destroy them
1e8724e6
VS
80from application class' destructor!
81
82For example, this code may crash:
83
84\begin{verbatim}
85class MyApp : public wxApp
86{
87 public:
88 wxCHMHelpController m_helpCtrl;
89 ...
90};
91\end{verbatim}
92
93The reason for that is that {\tt m\_helpCtrl} is a member object and is
94thus destroyed from MyApp destructor. But MyApp object is deleted after
fc2171bd 95wxWidgets structures that wxCHMHelpController depends on were
1e8724e6
VS
96uninitialized! The solution is to destroy HelpCtrl in {\it OnExit}:
97
98\begin{verbatim}
99class MyApp : public wxApp
100{
101 public:
102 wxCHMHelpController *m_helpCtrl;
103 ...
104};
105
106bool MyApp::OnInit()
107{
108 ...
109 m_helpCtrl = new wxCHMHelpController;
110 ...
111}
112
113int MyApp::OnExit()
114{
115 delete m_helpCtrl;
116 return 0;
117}
118\end{verbatim}