1 \section{wxApp overview
}\label{wxappoverview
}
3 Classes:
\helpref{wxApp
}{wxapp
}
5 A 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.
9 Unlike in earlier versions of wxWindows, OnInit does not return a frame. Instead it
10 returns a boolean value which indicates whether processing should continue (true) or not (false).
11 You call
\helpref{wxApp::SetTopWindow
}{wxappsettopwindow
} to let wxWindows know
14 Note that the program's command line arguments, represented by
{\it argc
}
15 and
{\it argv
}, are available from within wxApp member functions.
17 An application closes by destroying all windows. Because all frames must
18 be destroyed for the application to exit, it is advisable to use parent
19 frames wherever possible when creating new frames, so that deleting the
20 top level frame will automatically delete child frames. The alternative
21 is to explicitly delete child frames in the top-level frame's
\helpref{wxCloseEvent
}{wxcloseevent
}\rtfsp
24 In emergencies the
\helpref{wxExit
}{wxexit
} function can be called to kill the
25 application however normally the applications shuts down automatically,
26 \helpref{see below
}{wxappshutdownoverview
}.
28 An example of defining an application follows:
31 class DerivedApp : public wxApp
34 virtual bool OnInit();
37 IMPLEMENT_APP(DerivedApp)
39 bool DerivedApp::OnInit()
41 wxFrame *the_frame = new wxFrame(NULL, ID_MYFRAME, argv
[0]);
43 the_frame->Show(true);
44 SetTopWindow(the_frame);
50 Note the use of IMPLEMENT
\_APP(appClass), which allows wxWindows to dynamically create an instance of the application object
51 at the appropriate point in wxWindows initialization. Previous versions of wxWindows used
52 to rely on the creation of a global application object, but this is no longer recommended,
53 because required global initialization may not have been performed at application object
56 You can also use DECLARE
\_APP(appClass) in a header file to declare the wxGetApp function which returns
57 a reference to the application object.
59 \subsection{Application shutdown
}\label{wxappshutdownoverview
}
61 The application normally shuts down when the last of its top level windows is
62 closed. This is normally the expected behaviour and means that it is enough to
63 call
\helpref{Close()
}{wxwindowclose
} in response to the
{\tt "Exit"
} menu
64 command if your program has a single top level window. If this behaviour is not
65 desirable
\helpref{wxApp::SetExitOnFrameDelete
}{wxappsetexitonframedelete
} can
66 be called to change it. Note that starting from wxWindows
2.3.3 such logic
67 doesn't apply for the windows shown before the program enters the main loop: in
68 other words, you can safely show a dialog from
69 \helpref{wxApp::OnInit
}{wxapponinit
} and not be afraid that your application
70 terminates when this dialog -- which is the last top level window for the
74 Another aspect of the application shutdown is the
\helpref{OnExit
}{wxapponexit
}
75 which is called when the application exits but
{\it before
} wxWindows cleans up
76 its internal structures. Your should delete all wxWindows object that your
77 created by the time OnExit finishes. In particular, do
{\bf not
} destroy them
78 from application class' destructor!
80 For example, this code may crash:
83 class MyApp : public wxApp
86 wxCHMHelpController m_helpCtrl;
91 The reason for that is that
{\tt m
\_helpCtrl} is a member object and is
92 thus destroyed from MyApp destructor. But MyApp object is deleted after
93 wxWindows structures that wxCHMHelpController depends on were
94 uninitialized! The solution is to destroy HelpCtrl in
{\it OnExit
}:
97 class MyApp : public wxApp
100 wxCHMHelpController *m_helpCtrl;
107 m_helpCtrl = new wxCHMHelpController;