Applied patch [ 587450 ] Scoped Smart pointers and docs

[wxWidgets.git] / docs / latex / wx / tdelwin.tex

diff --git a/docs/latex/wx/tdelwin.tex b/docs/latex/wx/tdelwin.tex
index 7d7b02a1b1c8d9a0fa43ad9384a7e10012e1b99b..d425e42ae424d0084eb2112dfd7d00dadcb601a6 100644 (file)
--- a/docs/latex/wx/tdelwin.tex
+++ b/docs/latex/wx/tdelwin.tex
@@ -10,7 +10,7 @@ to close windows.
 
 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
 
 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 turn generates an EVT\_CLOSE event: see \helpref{wxWindow::OnCloseWindow}{wxwindowonclosewindow}.
+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
 decide whether or not to destroy the window.
 
 It is the duty of the application to define a suitable event handler, and
 decide whether or not to destroy the window.


@@ -53,9 +53,9 @@ In other words, by default, the dialog {\it is not destroyed} (it might have bee
 on the stack, so the assumption of dynamic creation cannot be made).
 
 The default close event handler for wxFrame destroys the frame using Destroy().
 on the stack, so the assumption of dynamic creation cannot be made).
 
 The default close event handler for wxFrame destroys the frame using Destroy().

-
-Under Windows, wxDialog defines a handler for \helpref{wxWindow::OnCharHook}{wxwindowoncharhook} that
-generates a Cancel event if the Escape key has been pressed.
+%
+%Under Windows, wxDialog defines a handler for \helpref{wxWindow::OnCharHook}{wxwindowoncharhook} that
+%generates a Cancel event if the Escape key has been pressed.

 
 \wxheading{What should I do when the user calls up Exit from a menu?}
 
 
 \wxheading{What should I do when the user calls up Exit from a menu?}