]> git.saurik.com Git - wxWidgets.git/blame - docs/latex/wx/app.tex
Added a generic wxProgressDialog and made wxPostscriptPrinter use it.
[wxWidgets.git] / docs / latex / wx / app.tex
CommitLineData
a660d684
KB
1\section{\class{wxApp}}\label{wxapp}
2
3The {\bf wxApp} class represents the application itself. It is used
4to:
5
6\begin{itemize}\itemsep=0pt
7\item set and get application-wide properties;
8\item implement the windowing system message or event loop;
9\item initiate application processing via \helpref{wxApp::OnInit}{wxapponinit};
10\item allow default processing of events not handled by other
11objects in the application.
12\end{itemize}
13
14You should use the macro IMPLEMENT\_APP(appClass) in your application implementation
15file to tell wxWindows how to create an instance of your application class.
16
17Use DECLARE\_APP(appClass) in a header file if you want the wxGetApp function (which returns
18a reference to your application object) to be visible to other files.
19
20\wxheading{Derived from}
21
22\helpref{wxEvtHandler}{wxevthandler}\\
23\helpref{wxObject}{wxobject}
24
954b8ae6
JS
25\wxheading{Include files}
26
27<wx/app.h>
28
a660d684
KB
29\wxheading{See also}
30
31\helpref{wxApp overview}{wxappoverview}
32
33\latexignore{\rtfignore{\wxheading{Members}}}
34
35\membersection{wxApp::wxApp}
36
2fd284a4 37\func{void}{wxApp}{\void}
a660d684
KB
38
39Constructor. Called implicitly with a definition of a wxApp object.
40
41The argument is a language identifier; this is an experimental
42feature and will be expanded and documented in future versions.
43
a660d684
KB
44\membersection{wxApp::\destruct{wxApp}}
45
46\func{void}{\destruct{wxApp}}{\void}
47
48Destructor. Will be called implicitly on program exit if the wxApp
49object is created on the stack.
50
51\membersection{wxApp::argc}\label{wxappargc}
52
53\member{int}{argc}
54
55Number of command line arguments (after environment-specific processing).
56
57\membersection{wxApp::argv}\label{wxappargv}
58
59\member{char **}{argv}
60
61Command line arguments (after environment-specific processing).
62
63\membersection{wxApp::CreateLogTarget}\label{wxappcreatelogtarget}
64
65\func{virtual wxLog*}{CreateLogTarget}{\void}
66
67Creates a wxLog class for the application to use for logging errors. The default
68implementation returns a new wxLogGui class.
69
70\wxheading{See also}
71
72\helpref{wxLog}{wxlog}
73
74\membersection{wxApp::Dispatch}\label{wxappdispatch}
75
76\func{void}{Dispatch}{\void}
77
78Dispatches the next event in the windowing system event queue.
79
80This can be used for programming event loops, e.g.
81
82\begin{verbatim}
83 while (app.Pending())
84 Dispatch();
85\end{verbatim}
86
87\wxheading{See also}
88
89\helpref{wxApp::Pending}{wxapppending}
90
91\membersection{wxApp::GetAppName}\label{wxappgetappname}
92
93\constfunc{wxString}{GetAppName}{\void}
94
95Returns the application name.
96
97\wxheading{Remarks}
98
99wxWindows sets this to a reasonable default before
100calling \helpref{wxApp::OnInit}{wxapponinit}, but the application can reset it at will.
101
102\membersection{wxApp::GetAuto3D}\label{wxappgetauto3d}
103
104\constfunc{bool}{GetAuto3D}{\void}
105
106Returns TRUE if 3D control mode is on, FALSE otherwise.
107
108\wxheading{See also}
109
110\helpref{wxApp::SetAuto3D}{wxappsetauto3d}
111
112\membersection{wxApp::GetClassName}\label{wxappgetclassname}
113
114\constfunc{wxString}{GetClassName}{\void}
115
116Gets the class name of the application. The class name may be used in a platform specific
117manner to refer to the application.
118
119\wxheading{See also}
120
121\helpref{wxApp::SetClassName}{wxappsetclassname}
122
123\membersection{wxApp::GetExitOnDelete}\label{wxappgetexitondelete}
124
125\constfunc{bool}{GetExitOnDelete}{\void}
126
127Returns TRUE if the application will exit when the top-level window is deleted, FALSE
128otherwise.
129
130\wxheading{See also}
131
132\helpref{wxApp::SetExitOnDelete}{wxappsetexitondelete}
133
a660d684
KB
134\membersection{wxApp::GetTopWindow}\label{wxappgettopwindow}
135
136\constfunc{wxWindow *}{GetTopWindow}{\void}
137
138Returns a pointer to the top window.
139
2a47d3c1
JS
140\wxheading{Remarks}
141
142If the top window hasn't been set using \helpref{wxApp::SetTopWindow}{wxappsettopwindow}, this
143function will find the first top-level window (frame or dialog) and return that.
144
a660d684
KB
145\wxheading{See also}
146
147\helpref{wxApp::SetTopWindow}{wxappsettopwindow}
148
149\membersection{wxApp::ExitMainLoop}\label{wxappexitmainloop}
150
151\func{void}{ExitMainLoop}{\void}
152
153Call this to explicitly exit the main message (event) loop.
154You should normally exit the main loop (and the application) by deleting
155the top window.
156
157\membersection{wxApp::Initialized}\label{wxappinitialized}
158
159\func{bool}{Initialized}{\void}
160
161Returns TRUE if the application has been initialized (i.e. if\rtfsp
162\helpref{wxApp::OnInit}{wxapponinit} has returned successfully). This can be useful for error
163message routines to determine which method of output is best for the
164current state of the program (some windowing systems may not like
165dialogs to pop up before the main loop has been entered).
166
167\membersection{wxApp::MainLoop}\label{wxappmainloop}
168
169\func{int}{MainLoop}{\void}
170
171Called by wxWindows on creation of the application. Override this if you wish
172to provide your own (environment-dependent) main loop.
173
174\wxheading{Return value}
175
176Returns 0 under X, and the wParam of the WM\_QUIT message under Windows.
177
178\membersection{wxApp::OnActivate}\label{wxapponactivate}
179
180\func{void}{OnActivate}{\param{wxActivateEvent\& }{event}}
181
182Provide this member function to know whether the application is being
183activated or deactivated (Windows only).
184
185\wxheading{See also}
186
187\helpref{wxWindow::OnActivate}{wxwindowonactivate}, \helpref{wxActivateEvent}{wxactivateevent}
188
189\membersection{wxApp::OnExit}\label{wxapponexit}
190
191\func{int}{OnExit}{\void}
192
193Provide this member function for any processing which needs to be done as
194the application is about to exit.
195
196\membersection{wxApp::OnCharHook}\label{wxapponcharhook}
197
198\func{void}{OnCharHook}{\param{wxKeyEvent\&}{ event}}
199
200This event handler function is called (under Windows only) to allow the window to intercept keyboard events
201before they are processed by child windows.
202
203\wxheading{Parameters}
204
205\docparam{event}{The keypress event.}
206
207\wxheading{Remarks}
208
209Use the wxEVT\_CHAR\_HOOK macro in your event table.
210
211If you use this member, you can selectively consume keypress events by calling\rtfsp
212\helpref{wxEvent::Skip}{wxeventskip} for characters the application is not interested in.
213
214\wxheading{See also}
215
216\helpref{wxKeyEvent}{wxkeyevent}, \helpref{wxWindow::OnChar}{wxwindowonchar},\rtfsp
217\helpref{wxWindow::OnCharHook}{wxwindowoncharhook}, \helpref{wxDialog::OnCharHook}{wxdialogoncharhook}
218
219\membersection{wxApp::OnIdle}\label{wxapponidle}
220
221\func{void}{OnIdle}{\param{wxIdleEvent\& }{event}}
222
223Override this member function for any processing which needs to be done
224when the application is idle. You should call wxApp::OnIdle from your own function,
225since this forwards OnIdle events to windows and also performs garbage collection for
226windows whose destruction has been delayed.
227
228wxWindows' strategy for OnIdle processing is as follows. After pending user interface events for an
229application have all been processed, wxWindows sends an OnIdle event to the application object. wxApp::OnIdle itself
230sends an OnIdle event to each application window, allowing windows to do idle processing such as updating
231their appearance. If either wxApp::OnIdle or a window OnIdle function requested more time, by
232caling \helpref{wxIdleEvent::ReqestMore}{wxidleeventrequestmore}, wxWindows will send another OnIdle
8a2c6ef8 233event to the application object. This will occur in a loop until either a user event is found to be
a660d684
KB
234pending, or OnIdle requests no more time. Then all pending user events are processed until the system
235goes idle again, when OnIdle is called, and so on.
236
237\wxheading{See also}
238
239\helpref{wxWindow::OnIdle}{wxwindowonidle}, \helpref{wxIdleEvent}{wxidleevent},\rtfsp
240\helpref{wxWindow::SendIdleEvents}{wxappsendidleevents}
241
387a3b02
JS
242\membersection{wxApp::OnEndSession}\label{wxapponendsession}
243
244\func{void}{OnEndSession}{\param{wxCloseEvent\& }{event}}
245
246This is an event handler function called when the operating system or GUI session is
247about to close down. The application has a chance to silently save information,
248and can optionally close itself.
249
250Use the EVT\_END\_SESSION event table macro to handle query end session events.
251
252The default handler calls \helpref{wxWindow::Close}{wxwindowclose} with a TRUE argument
253(forcing the application to close itself silently).
254
255\wxheading{Remarks}
256
257Under X, OnEndSession is called in response to the 'die' event.
258
259Under Windows, OnEndSession is called in response to the WM\_ENDSESSION message.
260
261\wxheading{See also}
262
263\helpref{wxWindow::Close}{wxwindowclose},\rtfsp
264\helpref{wxWindow::OnCloseWindow}{wxwindowonclosewindow},\rtfsp
265\helpref{wxCloseEvent}{wxcloseevent},\rtfsp
da36f544 266\helpref{wxApp::OnQueryEndSession}{wxapponqueryendsession}
387a3b02 267
a660d684
KB
268\membersection{wxApp::OnInit}\label{wxapponinit}
269
270\func{bool}{OnInit}{\void}
271
272This must be provided by the application, and will usually create the
2a47d3c1 273application's main window, optionally calling \helpref{wxApp::SetTopWindow}{wxappsettopwindow}.
a660d684
KB
274
275Return TRUE to continue processing, FALSE to exit the application.
276
387a3b02 277\membersection{wxApp::OnQueryEndSession}\label{wxapponqueryendsession}
a660d684 278
387a3b02 279\func{void}{OnQueryEndSession}{\param{wxCloseEvent\& }{event}}
a660d684 280
387a3b02
JS
281This is an event handler function called when the operating system or GUI session is
282about to close down. Typically, an application will try to save unsaved documents
283at this point.
284
285If \helpref{wxCloseEvent::CanVeto}{wxcloseeventcanveto} returns TRUE, the application
286is allowed to veto the shutdown by calling \helpref{wxCloseEvent::Veto}{wxcloseeventveto}.
287The application might veto the shutdown after prompting for documents to be saved, and the
288user has cancelled the save.
289
290Use the EVT\_QUERY\_END\_SESSION event table macro to handle query end session events.
291
292You should check whether the application is forcing the deletion of the window
293using \helpref{wxCloseEvent::GetForce}{wxcloseeventgetforce}. If this is TRUE,
294destroy the window using \helpref{wxWindow::Destroy}{wxwindowdestroy}.
295If not, it is up to you whether you respond by destroying the window.
296
297The default handler calls \helpref{wxWindow::Close}{wxwindowclose} on the top-level window,
298and vetoes the shutdown if Close returns FALSE. This will be sufficient for many applications.
299
300\wxheading{Remarks}
301
302Under X, OnQueryEndSession is called in response to the 'save session' event.
303
304Under Windows, OnQueryEndSession is called in response to the WM\_QUERYENDSESSION message.
a660d684
KB
305
306\wxheading{See also}
307
387a3b02
JS
308\helpref{wxWindow::Close}{wxwindowclose},\rtfsp
309\helpref{wxWindow::OnCloseWindow}{wxwindowonclosewindow},\rtfsp
310\helpref{wxCloseEvent}{wxcloseevent},\rtfsp
311\helpref{wxApp::OnEndSession}{wxapponendsession}
312
a660d684
KB
313\membersection{wxApp::ProcessMessage}\label{wxappprocessmessage}
314
315\func{bool}{ProcessMessage}{\param{MSG *}{msg}}
316
317Windows-only function for processing a message. This function
318is called from the main message loop, checking for windows that
319may wish to process it. The function returns TRUE if the message
320was processed, FALSE otherwise. If you use wxWindows with another class
321library with its own message loop, you should make sure that this
322function is called to allow wxWindows to receive messages. For example,
323to allow co-existance with the Microsoft Foundation Classes, override
324the PreTranslateMessage function:
325
326\begin{verbatim}
327// Provide wxWindows message loop compatibility
328BOOL CTheApp::PreTranslateMessage(MSG *msg)
329{
330 if (wxTheApp && wxTheApp->ProcessMessage(msg))
331 return TRUE;
332 else
333 return CWinApp::PreTranslateMessage(msg);
334}
335\end{verbatim}
336
387a3b02
JS
337\membersection{wxApp::Pending}\label{wxapppending}
338
339\func{bool}{Pending}{\void}
340
341Returns TRUE if unprocessed events are in the window system event queue
342(MS Windows and Motif).
343
344\wxheading{See also}
345
346\helpref{wxApp::Dispatch}{wxappdispatch}
347
a660d684
KB
348\membersection{wxApp::SendIdleEvents}\label{wxappsendidleevents}
349
350\func{bool}{SendIdleEvents}{\void}
351
352Sends idle events to all top-level windows.
353
354\func{bool}{SendIdleEvents}{\param{wxWindow*}{ win}}
355
356Sends idle events to a window and its children.
357
358\wxheading{Remarks}
359
360These functions poll the top-level windows, and their children, for idle event processing.
361If TRUE is returned, more OnIdle processing is requested by one or more window.
362
363\wxheading{See also}
364
365\helpref{wxApp::OnIdle}{wxapponidle}, \helpref{wxWindow::OnIdle}{wxwindowonidle}, \helpref{wxIdleEvent}{wxidleevent}
366
367\membersection{wxApp::SetAppName}\label{wxappsetappname}
368
369\func{void}{SetAppName}{\param{const wxString\& }{name}}
370
371Sets the name of the application. The name may be used in dialogs
372(for example by the document/view framework). A default name is set by
373wxWindows.
374
375\wxheading{See also}
376
377\helpref{wxApp::GetAppName}{wxappgetappname}
378
379\membersection{wxApp::SetAuto3D}\label{wxappsetauto3d}
380
381\func{void}{SetAuto3D}{\param{const bool}{ auto3D}}
382
383Switches automatic 3D controls on or off.
384
385\wxheading{Parameters}
386
387\docparam{auto3D}{If TRUE, all controls will be created with 3D appearances unless
388overridden for a control or dialog. The default is TRUE}
389
390\wxheading{Remarks}
391
392This has an effect on Windows only.
393
394\wxheading{See also}
395
396\helpref{wxApp::GetAuto3D}{wxappgetauto3d}
397
398\membersection{wxApp::SetClassName}\label{wxappsetclassname}
399
400\func{void}{SetClassName}{\param{const wxString\& }{name}}
401
402Sets the class name of the application. This may be used in a platform specific
403manner to refer to the application.
404
405\wxheading{See also}
406
407\helpref{wxApp::GetClassName}{wxappgetclassname}
408
409\membersection{wxApp::SetExitOnDelete}\label{wxappsetexitondelete}
410
411\func{void}{SetExitOnDelete}{\param{bool}{ flag}}
412
413Allows the programmer to specify whether the application will exit when the
414top-level frame is deleted.
415
416\wxheading{Parameters}
417
418\docparam{flag}{If TRUE (the default), the application will exit when the top-level frame is
419deleted. If FALSE, the application will continue to run.}
420
421\wxheading{Remarks}
422
423Currently, setting this to FALSE only has an effect under Windows.
424
a660d684
KB
425\membersection{wxApp::SetTopWindow}\label{wxappsettopwindow}
426
427\func{void}{SetTopWindow}{\param{wxWindow* }{window}}
428
2a47d3c1
JS
429Sets the `top' window. You can call this from within \helpref{wxApp::OnInit}{wxapponinit} to
430let wxWindows know which is the main window. You don't have to set the top window;
431it's only a convenience so that (for example) certain dialogs without parents can use a
432specific window as the top window. If no top window is specified by the application,
433wxWindows just uses the first frame or dialog in its top-level window list, when it
434needs to use the top window.
a660d684
KB
435
436\wxheading{Parameters}
437
438\docparam{window}{The new top window.}
439
440\wxheading{See also}
441
442\helpref{wxApp::GetTopWindow}{wxappgettopwindow}, \helpref{wxApp::OnInit}{wxapponinit}
443