latex/wx/app.tex

3 The {\bf wxApp} class represents the application itself. It is used
48 object is created on the stack.
120 This function is called before processing any event and allows the application
122 is processed normally, otherwise either {\tt true} or {\tt false} should be
124 had been already processed (for the former return value) or that it is not
156 Returns true if the application will exit when the top-level window is deleted, false
170 Usually \texttt{wxTheApp} is usead instead.
227 Returns \true if the application is active, i.e. if one of its windows is
238 Returns \true if the main event loop is currently running, i.e. if the
239 application is inside \helpref{OnRun}{wxapponrun}.
263 %%Provide this member function to know whether the application is being
274 %%This event handler function is called (under Windows only) to allow the window to intercept keyboard events
286 %%\helpref{wxEvent::Skip}{wxeventskip} for characters the application is not interested in.
298 This function is called when an assert failure occurs, i.e. the condition
300 It is only called in debug mode (when {\tt \_\_WXDEBUG\_\_} is defined) as
328 was specified by the user). The default behaviour is to show the program usage
344 The default behaviour is to show the program usage text and abort the program.
377 This function is called if an unhandled exception occurs inside the main
383 The default behaviour of this function is the latter in all ports except under
384 Windows where a dialog is shown to the user which allows him to choose between
388 Finally note that if the exception is rethrown from here, it can be caught in
397 done as the application is about to exit. OnExit is called after
399 wxWidgets cleanup. Note that it is not called at all if
402 The return value of this function is currently ignored, return the same value
416 return. You may attempt to save unsaved data but this is not guaranteed to
430 %%when the application is idle. You should call wxApp::OnIdle from your own function,
434 %%wxWidgets' strategy for OnIdle processing is as follows. After pending user interface events for an
439 %%event to the application object. This will occur in a loop until either a user event is found to be
441 %%goes idle again, when OnIdle is called, and so on.
452 %%This is an event handler function called when the operating system or GUI session is
463 %%Under X, OnEndSession is called in response to the `die' event.
465 %%Under Windows, OnEndSession is called in response to the WM\_ENDSESSION message.
504 This virtual function is where the execution of a program written in wxWidgets
509 \helpref{GetExitOnFrameDelete}{wxappgetexitonframedelete} flag is \true (this
510 is the default).
520 This function is called when an unhandled C++ exception occurs inside
523 Note that the exception type is lost by now, so if you want to really handle
533 is called from the main message loop, checking for windows that
537 function is called to allow wxWidgets to receive messages. For example,
570 Please note that this function is internal to wxWidgets and shouldn't be used
576 If true is returned, more OnIdle processing is requested by one or more window.
588 (for example by the document/view framework). A default name is set by
613 top-level frame is deleted.
617 \docparam{flag}{If true (the default), the application will exit when the top-level frame is
647 let wxWidgets know which is the main window. You don't have to set the top window;
648 it is only a convenience so that (for example) certain dialogs without parents can use a
649 specific window as the top window. If no top window is specified by the application,
668 in registry access. A default name is set by
681 on systems that support several visual on the same display. This is typically the
682 case under Solaris and IRIX, where the default visual is only 8-bit whereas certain
685 If \arg{forceTrueColour} is true then the application will try to force
686 using a TrueColour visual and abort the app if none is found.
724 Note that Yield() will not flush the message logs. This is intentional as
725 calling Yield() is usually done to quickly update the screen and popping up a
730 Calling Yield() recursively is normally an error and an assert failure is
731 raised in debug build if such situation is detected. However if the
732 {\it onlyIfNeeded} parameter is {\tt true}, the method will just silently