]> git.saurik.com Git - wxWidgets.git/blame - docs/latex/wx/tapp.tex
We surely don't need two debugging sections,
[wxWidgets.git] / docs / latex / wx / tapp.tex
CommitLineData
a660d684
KB
1\section{wxApp overview}\label{wxappoverview}
2
3Classes: \helpref{wxApp}{wxapp}
4
5A wxWindows application does not have a {\it main} procedure; the equivalent is the
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
9Unlike in earlier versions of wxWindows, OnInit does not return a frame. Instead it
cc81d32f 10returns a boolean value which indicates whether processing should continue (true) or not (false).
a660d684
KB
11You call \helpref{wxApp::SetTopWindow}{wxappsettopwindow} to let wxWindows know
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
50Note the use of IMPLEMENT\_APP(appClass), which allows wxWindows to dynamically create an instance of the application object
51at the appropriate point in wxWindows initialization. Previous versions of wxWindows used
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
57a reference to the application object.
58
1cbee0b4
VZ
59\subsection{Application shutdown}\label{wxappshutdownoverview}
60
61The application normally shuts down when the last of its top level windows is
62closed. This is normally the expected behaviour and means that it is enough to
63call \helpref{Close()}{wxwindowclose} in response to the {\tt "Exit"} menu
64command if your program has a single top level window. If this behaviour is not
65desirable \helpref{wxApp::SetExitOnFrameDelete}{wxappsetexitonframedelete} can
66be called to change it. Note that starting from wxWindows 2.3.3 such logic
67doesn't apply for the windows shown before the program enters the main loop: in
68other words, you can safely show a dialog from
69\helpref{wxApp::OnInit}{wxapponinit} and not be afraid that your application
70terminates when this dialog -- which is the last top level window for the
71moment -- is closed.
72
73
74Another aspect of the application shutdown is the \helpref{OnExit}{wxapponexit}
75which is called when the application exits but {\it before} wxWindows cleans up
76its internal structures. Your should delete all wxWindows object that your
77created by the time OnExit finishes. In particular, do {\bf not} destroy them
1e8724e6
VS
78from application class' destructor!
79
80For example, this code may crash:
81
82\begin{verbatim}
83class MyApp : public wxApp
84{
85 public:
86 wxCHMHelpController m_helpCtrl;
87 ...
88};
89\end{verbatim}
90
91The reason for that is that {\tt m\_helpCtrl} is a member object and is
92thus destroyed from MyApp destructor. But MyApp object is deleted after
93wxWindows structures that wxCHMHelpController depends on were
94uninitialized! The solution is to destroy HelpCtrl in {\it OnExit}:
95
96\begin{verbatim}
97class MyApp : public wxApp
98{
99 public:
100 wxCHMHelpController *m_helpCtrl;
101 ...
102};
103
104bool MyApp::OnInit()
105{
106 ...
107 m_helpCtrl = new wxCHMHelpController;
108 ...
109}
110
111int MyApp::OnExit()
112{
113 delete m_helpCtrl;
114 return 0;
115}
116\end{verbatim}