Lines Matching refs:to
6 to help make it clear when and how you delete windows, or respond to user requests
7 to close windows.
15 It is the duty of the application to define a suitable event handler, and
16 decide whether or not to destroy the window.
17 If the application is for some reason forcing the application to close
18 (\helpref{wxCloseEvent::CanVeto}{wxcloseeventcanveto} returns false), the window should always be destroyed, otherwise there is the option to
20 before deciding whether it is safe to close. The handler for EVT\_CLOSE should
21 signal to the calling code if it does not destroy the window, by calling
23 to the calling code.
25 The wxCloseEvent handler should only call \helpref{wxWindow::Destroy}{wxwindowdestroy} to
28 since otherwise there is the danger that events will be sent to a non-existent window.
31 will be destroyed. Call \helpref{wxWindow::Destroy}{wxwindowdestroy} if you want to be
38 If using Close(), you can pass a true argument to this function to tell the event handler
39 that we definitely want to delete the frame and it cannot be vetoed.
62 You can do checking to see if your application can be safely exited at this point,
64 handler. For example, you may wish to check that all files have been saved.
65 Give the user a chance to save and quit, to not save but quit anyway, or to cancel
68 \wxheading{What should I do to upgrade my 1.xx OnClose to 2.0?}
71 to the calling function (either {\bf Close}, or the wxWidgets framework) to delete
121 that are themselves frames or dialogs, so you may wish to close these child frame or dialog windows
129 continue to use the \helpref{wxWindow::Destroy}{wxwindowdestroy} function instead