Amebis/wxWidgets
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Name change replacements

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@27090 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Julian Smart
2004-05-04 08:27:20 +00:00
parent e119d0498a
commit fc2171bd4c
268 changed files with 1372 additions and 1366 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
docs/latex/wx/tdelwin.tex
View File

@@ -9,7 +9,7 @@ to close windows.
\wxheading{What is the sequence of events in a window deletion?}
When the user clicks on the system close button or system close command,
in a frame or a dialog, wxWindows calls \helpref{wxWindow::Close}{wxwindowclose}. This
in a frame or a dialog, wxWidgets calls \helpref{wxWindow::Close}{wxwindowclose}. This
in turn generates an EVT\_CLOSE event: see \helpref{wxCloseEvent}{wxcloseevent}.
It is the duty of the application to define a suitable event handler, and
@@ -24,7 +24,7 @@ to the calling code.
The wxCloseEvent handler should only call \helpref{wxWindow::Destroy}{wxwindowdestroy} to
delete the window, and not use the {\bf delete} operator. This is because
for some window classes, wxWindows delays actual deletion of the window until all events have been processed,
for some window classes, wxWidgets delays actual deletion of the window until all events have been processed,
since otherwise there is the danger that events will be sent to a non-existent window.
As reinforced in the next section, calling Close does not guarantee that the window
@@ -70,8 +70,8 @@ the exit command altogether.
\wxheading{What should I do to upgrade my 1.xx OnClose to 2.0?}
In wxWindows 1.xx, the {\bf OnClose} function did not actually delete 'this', but signaled
to the calling function (either {\bf Close}, or the wxWindows framework) to delete
In wxWidgets 1.xx, the {\bf OnClose} function did not actually delete 'this', but signaled
to the calling function (either {\bf Close}, or the wxWidgets framework) to delete
or not delete the window.
To update your code, you should provide an event table entry in your frame or
@@ -113,7 +113,7 @@ dialog, using the EVT\_CLOSE macro. The event handler function might look like t
\wxheading{How do I exit the application gracefully?}
A wxWindows application automatically exits when the designated top window, or the
A wxWidgets application automatically exits when the designated top window, or the
last frame or dialog, is destroyed. Put any application-wide cleanup code in \helpref{wxApp::OnExit}{wxapponexit} (this
is a virtual function, not an event handler).