1\section{\class{wxWindowDestroyEvent}}\label{wxwindowdestroyevent} 2 3% Note: the original description is still here commented out in case those 4% semantics are restored to this event. 5 6%This event is sent just before the actual window associated with a wxWindow object 7%is destroyed. Since it is derived from wxCommandEvent, the event propagates up 8%the window hierarchy. 9 10This event is sent from the wxWindow destructor wxWindow::~wxWindow() when a 11window is destroyed. 12 13When a class derived from wxWindow is destroyed its destructor will have 14already run by the time this event is sent. Therefore this event will not 15usually be received at all. 16 17To receive this event \helpref{wxEvtHandler::Connect}{wxevthandlerconnect} 18must be used (using an event table macro will not work). Since it is 19received after the destructor has run, an object should not handle its 20own wxWindowDestroyEvent, but it can be used to get notification of the 21destruction of another window. 22 23\wxheading{Derived from} 24 25\helpref{wxCommandEvent}{wxevent}\\ 26\helpref{wxEvent}{wxevent}\\ 27\helpref{wxObject}{wxobject} 28 29\wxheading{Include files} 30 31<wx/event.h> 32 33\wxheading{Event table macros} 34 35%To process a window destruction event, use this event handler macro to direct input to a member 36%function that takes a wxWindowDestroyEvent argument. 37% 38%\twocolwidtha{7cm} 39%\begin{twocollist}\itemsep=0pt 40%\twocolitem{{\bf EVT\_WINDOW\_DESTROY(func)}}{Process a wxEVT\_DESTROY event.} 41%\end{twocollist}% 42 43It is not possible to receive this event using an event table macro. 44 45\wxheading{See also} 46 47\helpref{Event handling overview}{eventhandlingoverview},\rtfsp 48\helpref{wxWindowCreateEvent}{wxwindowcreateevent} 49 50\latexignore{\rtfignore{\wxheading{Members}}} 51 52\membersection{wxWindowDestroyEvent::wxWindowDestroyEvent}\label{wxwindowdestroyeventctor} 53 54\func{}{wxWindowDestroyEvent}{\param{wxWindow* }{win = NULL}} 55 56Constructor. 57 58