]> git.saurik.com Git - wxWidgets.git/blob - docs/latex/wx/app.tex
1. wxStaticLine implemented (generic (ugly) and MSW versions)
[wxWidgets.git] / docs / latex / wx / app.tex
1 \section{\class{wxApp}}\label{wxapp}
2
3 The {\bf wxApp} class represents the application itself. It is used
4 to:
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
11 objects in the application.
12 \end{itemize}
13
14 You should use the macro IMPLEMENT\_APP(appClass) in your application implementation
15 file to tell wxWindows how to create an instance of your application class.
16
17 Use DECLARE\_APP(appClass) in a header file if you want the wxGetApp function (which returns
18 a 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
25 \wxheading{Include files}
26
27 <wx/app.h>
28
29 \wxheading{See also}
30
31 \helpref{wxApp overview}{wxappoverview}
32
33 \latexignore{\rtfignore{\wxheading{Members}}}
34
35 \membersection{wxApp::wxApp}
36
37 \func{void}{wxApp}{\void}
38
39 Constructor. Called implicitly with a definition of a wxApp object.
40
41 The argument is a language identifier; this is an experimental
42 feature and will be expanded and documented in future versions.
43
44 \membersection{wxApp::\destruct{wxApp}}
45
46 \func{void}{\destruct{wxApp}}{\void}
47
48 Destructor. Will be called implicitly on program exit if the wxApp
49 object is created on the stack.
50
51 \membersection{wxApp::argc}\label{wxappargc}
52
53 \member{int}{argc}
54
55 Number of command line arguments (after environment-specific processing).
56
57 \membersection{wxApp::argv}\label{wxappargv}
58
59 \member{char **}{argv}
60
61 Command line arguments (after environment-specific processing).
62
63 \membersection{wxApp::CreateLogTarget}\label{wxappcreatelogtarget}
64
65 \func{virtual wxLog*}{CreateLogTarget}{\void}
66
67 Creates a wxLog class for the application to use for logging errors. The default
68 implementation 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
78 Dispatches the next event in the windowing system event queue.
79
80 This 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
95 Returns the application name.
96
97 \wxheading{Remarks}
98
99 wxWindows sets this to a reasonable default before
100 calling \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
106 Returns 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
116 Gets the class name of the application. The class name may be used in a platform specific
117 manner 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
127 Returns TRUE if the application will exit when the top-level window is deleted, FALSE
128 otherwise.
129
130 \wxheading{See also}
131
132 \helpref{wxApp::SetExitOnDelete}{wxappsetexitondelete}
133
134 \membersection{wxApp::GetTopWindow}\label{wxappgettopwindow}
135
136 \constfunc{wxWindow *}{GetTopWindow}{\void}
137
138 Returns a pointer to the top window.
139
140 \wxheading{Remarks}
141
142 If the top window hasn't been set using \helpref{wxApp::SetTopWindow}{wxappsettopwindow}, this
143 function will find the first top-level window (frame or dialog) and return that.
144
145 \wxheading{See also}
146
147 \helpref{wxApp::SetTopWindow}{wxappsettopwindow}
148
149 \membersection{wxApp::ExitMainLoop}\label{wxappexitmainloop}
150
151 \func{void}{ExitMainLoop}{\void}
152
153 Call this to explicitly exit the main message (event) loop.
154 You should normally exit the main loop (and the application) by deleting
155 the top window.
156
157 \membersection{wxApp::Initialized}\label{wxappinitialized}
158
159 \func{bool}{Initialized}{\void}
160
161 Returns 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
163 message routines to determine which method of output is best for the
164 current state of the program (some windowing systems may not like
165 dialogs to pop up before the main loop has been entered).
166
167 \membersection{wxApp::MainLoop}\label{wxappmainloop}
168
169 \func{int}{MainLoop}{\void}
170
171 Called by wxWindows on creation of the application. Override this if you wish
172 to provide your own (environment-dependent) main loop.
173
174 \wxheading{Return value}
175
176 Returns 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
182 Provide this member function to know whether the application is being
183 activated 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
193 Provide this member function for any processing which needs to be done as
194 the application is about to exit.
195
196 \membersection{wxApp::OnCharHook}\label{wxapponcharhook}
197
198 \func{void}{OnCharHook}{\param{wxKeyEvent\&}{ event}}
199
200 This event handler function is called (under Windows only) to allow the window to intercept keyboard events
201 before they are processed by child windows.
202
203 \wxheading{Parameters}
204
205 \docparam{event}{The keypress event.}
206
207 \wxheading{Remarks}
208
209 Use the wxEVT\_CHAR\_HOOK macro in your event table.
210
211 If 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
223 Override this member function for any processing which needs to be done
224 when the application is idle. You should call wxApp::OnIdle from your own function,
225 since this forwards OnIdle events to windows and also performs garbage collection for
226 windows whose destruction has been delayed.
227
228 wxWindows' strategy for OnIdle processing is as follows. After pending user interface events for an
229 application have all been processed, wxWindows sends an OnIdle event to the application object. wxApp::OnIdle itself
230 sends an OnIdle event to each application window, allowing windows to do idle processing such as updating
231 their appearance. If either wxApp::OnIdle or a window OnIdle function requested more time, by
232 caling \helpref{wxIdleEvent::ReqestMore}{wxidleeventrequestmore}, wxWindows will send another OnIdle
233 event to the application object. This will occur in a loop until either a user event is found to be
234 pending, or OnIdle requests no more time. Then all pending user events are processed until the system
235 goes 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
242 \membersection{wxApp::OnEndSession}\label{wxapponendsession}
243
244 \func{void}{OnEndSession}{\param{wxCloseEvent\& }{event}}
245
246 This is an event handler function called when the operating system or GUI session is
247 about to close down. The application has a chance to silently save information,
248 and can optionally close itself.
249
250 Use the EVT\_END\_SESSION event table macro to handle query end session events.
251
252 The default handler calls \helpref{wxWindow::Close}{wxwindowclose} with a TRUE argument
253 (forcing the application to close itself silently).
254
255 \wxheading{Remarks}
256
257 Under X, OnEndSession is called in response to the 'die' event.
258
259 Under 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
266 \helpref{wxApp::OnQueryEndSession}{wxapponqueryendsession}
267
268 \membersection{wxApp::OnInit}\label{wxapponinit}
269
270 \func{bool}{OnInit}{\void}
271
272 This must be provided by the application, and will usually create the
273 application's main window, optionally calling \helpref{wxApp::SetTopWindow}{wxappsettopwindow}.
274
275 Return TRUE to continue processing, FALSE to exit the application.
276
277 \membersection{wxApp::OnQueryEndSession}\label{wxapponqueryendsession}
278
279 \func{void}{OnQueryEndSession}{\param{wxCloseEvent\& }{event}}
280
281 This is an event handler function called when the operating system or GUI session is
282 about to close down. Typically, an application will try to save unsaved documents
283 at this point.
284
285 If \helpref{wxCloseEvent::CanVeto}{wxcloseeventcanveto} returns TRUE, the application
286 is allowed to veto the shutdown by calling \helpref{wxCloseEvent::Veto}{wxcloseeventveto}.
287 The application might veto the shutdown after prompting for documents to be saved, and the
288 user has cancelled the save.
289
290 Use the EVT\_QUERY\_END\_SESSION event table macro to handle query end session events.
291
292 You should check whether the application is forcing the deletion of the window
293 using \helpref{wxCloseEvent::GetForce}{wxcloseeventgetforce}. If this is TRUE,
294 destroy the window using \helpref{wxWindow::Destroy}{wxwindowdestroy}.
295 If not, it is up to you whether you respond by destroying the window.
296
297 The default handler calls \helpref{wxWindow::Close}{wxwindowclose} on the top-level window,
298 and vetoes the shutdown if Close returns FALSE. This will be sufficient for many applications.
299
300 \wxheading{Remarks}
301
302 Under X, OnQueryEndSession is called in response to the 'save session' event.
303
304 Under Windows, OnQueryEndSession is called in response to the WM\_QUERYENDSESSION message.
305
306 \wxheading{See also}
307
308 \helpref{wxWindow::Close}{wxwindowclose},\rtfsp
309 \helpref{wxWindow::OnCloseWindow}{wxwindowonclosewindow},\rtfsp
310 \helpref{wxCloseEvent}{wxcloseevent},\rtfsp
311 \helpref{wxApp::OnEndSession}{wxapponendsession}
312
313 \membersection{wxApp::ProcessMessage}\label{wxappprocessmessage}
314
315 \func{bool}{ProcessMessage}{\param{MSG *}{msg}}
316
317 Windows-only function for processing a message. This function
318 is called from the main message loop, checking for windows that
319 may wish to process it. The function returns TRUE if the message
320 was processed, FALSE otherwise. If you use wxWindows with another class
321 library with its own message loop, you should make sure that this
322 function is called to allow wxWindows to receive messages. For example,
323 to allow co-existance with the Microsoft Foundation Classes, override
324 the PreTranslateMessage function:
325
326 \begin{verbatim}
327 // Provide wxWindows message loop compatibility
328 BOOL 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
337 \membersection{wxApp::Pending}\label{wxapppending}
338
339 \func{bool}{Pending}{\void}
340
341 Returns 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
348 \membersection{wxApp::SendIdleEvents}\label{wxappsendidleevents}
349
350 \func{bool}{SendIdleEvents}{\void}
351
352 Sends idle events to all top-level windows.
353
354 \func{bool}{SendIdleEvents}{\param{wxWindow*}{ win}}
355
356 Sends idle events to a window and its children.
357
358 \wxheading{Remarks}
359
360 These functions poll the top-level windows, and their children, for idle event processing.
361 If 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
371 Sets 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
373 wxWindows.
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
383 Switches 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
388 overridden for a control or dialog. The default is TRUE}
389
390 \wxheading{Remarks}
391
392 This 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
402 Sets the class name of the application. This may be used in a platform specific
403 manner 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
413 Allows the programmer to specify whether the application will exit when the
414 top-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
419 deleted. If FALSE, the application will continue to run.}
420
421 \wxheading{Remarks}
422
423 Currently, setting this to FALSE only has an effect under Windows.
424
425 \membersection{wxApp::SetTopWindow}\label{wxappsettopwindow}
426
427 \func{void}{SetTopWindow}{\param{wxWindow* }{window}}
428
429 Sets the `top' window. You can call this from within \helpref{wxApp::OnInit}{wxapponinit} to
430 let wxWindows know which is the main window. You don't have to set the top window;
431 it's only a convenience so that (for example) certain dialogs without parents can use a
432 specific window as the top window. If no top window is specified by the application,
433 wxWindows just uses the first frame or dialog in its top-level window list, when it
434 needs to use the top window.
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