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

merged 2.2 branch

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@7748 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Bryan Petty
2000-07-15 19:51:35 +00:00
parent 8a693e6e04
commit f6bcfd974e
1835 changed files with 237729 additions and 67990 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -17,7 +17,7 @@ decide whether or not to destroy the window.
If the application is for some reason forcing the application to close
(\helpref{wxCloseEvent::CanVeto}{wxcloseeventcanveto} returns FALSE), the window should always be destroyed, otherwise there is the option to
ignore the request, or maybe wait until the user has answered a question
before deciding whether it's safe to close. The handler for EVT\_CLOSE should
before deciding whether it is safe to close. The handler for EVT\_CLOSE should
signal to the calling code if it does not destroy the window, by calling
\helpref{wxCloseEvent::Veto}{wxcloseeventveto}. Calling this provides useful information
to the calling code.
@@ -70,7 +70,7 @@ 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 signalled
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
or not delete the window.