fixed all warnings for topic overviews (letters a,h)
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@52096 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
@@ -10,9 +10,17 @@
|
||||
|
||||
@page overview_app wxApp overview
|
||||
|
||||
Classes: #wxApp
|
||||
Classes: wxApp
|
||||
|
||||
|
||||
@li @ref overview_app_shutdown
|
||||
|
||||
|
||||
<hr>
|
||||
|
||||
|
||||
A wxWidgets application does not have a @e main procedure; the equivalent is the
|
||||
#OnInit member defined for a class derived from wxApp.
|
||||
wxApp::OnInit member defined for a class derived from wxApp.
|
||||
|
||||
@e OnInit will usually create a top window as a bare minimum.
|
||||
Unlike in earlier versions of wxWidgets, OnInit does not return a frame. Instead it
|
||||
@@ -26,10 +34,10 @@
|
||||
be destroyed for the application to exit, it is advisable to use parent
|
||||
frames wherever possible when creating new frames, so that deleting the
|
||||
top level frame will automatically delete child frames. The alternative
|
||||
is to explicitly delete child frames in the top-level frame's #wxCloseEvent
|
||||
is to explicitly delete child frames in the top-level frame's wxCloseEvent
|
||||
handler.
|
||||
|
||||
In emergencies the #wxExit function can be called to kill the
|
||||
In emergencies the wxExit function can be called to kill the
|
||||
application however normally the application shuts down automatically,
|
||||
see @ref overview_app_shutdown.
|
||||
|
||||
@@ -71,16 +79,16 @@
|
||||
|
||||
The application normally shuts down when the last of its top level windows is
|
||||
closed. This is normally the expected behaviour and means that it is enough to
|
||||
call #Close() in response to the @c "Exit" menu command if your program has a single
|
||||
top level window. If this behaviour is not desirable wxApp::SetExitOnFrameDelete can
|
||||
be called to change it.
|
||||
call wxWindow::Close() in response to the @c "Exit" menu command if your program has a
|
||||
single top level window. If this behaviour is not desirable wxApp::SetExitOnFrameDelete
|
||||
can be called to change it.
|
||||
|
||||
Note that starting from wxWidgets 2.3.3 such logic doesn't apply for the windows shown
|
||||
before the program enters the main loop: in other words, you can safely show a dialog from
|
||||
wxApp::OnInit and not be afraid that your application terminates when this dialog --
|
||||
which is the last top level window for the moment -- is closed.
|
||||
Note that such logic doesn't apply for the windows shown before the program enters the
|
||||
main loop: in other words, you can safely show a dialog from wxApp::OnInit and not be
|
||||
afraid that your application terminates when this dialog -- which is the last top level
|
||||
window for the moment -- is closed.
|
||||
|
||||
Another aspect of the application shutdown is #OnExit
|
||||
Another aspect of the application shutdown is wxApp::OnExit
|
||||
which is called when the application exits but @e before wxWidgets cleans up
|
||||
its internal structures. You should delete all wxWidgets object that you
|
||||
created by the time OnExit finishes.
|
||||
|
Reference in New Issue
Block a user