1wxWindowDestroyEvent(3)    Erlang Module Definition    wxWindowDestroyEvent(3)
2
3
4

NAME

6       wxWindowDestroyEvent - Functions for wxWindowDestroyEvent class
7

DESCRIPTION

9       This  event  is sent as early as possible during the window destruction
10       process.
11
12       For the top level windows, as early as possible means that this is done
13       by wxFrame or wxDialog destructor, i.e. after the destructor of the de‐
14       rived class was executed and so any methods  specific  to  the  derived
15       class  can't be called any more from this event handler. If you need to
16       do this, you must call wxWindow::SendDestroyEvent() (not implemented in
17       wx) from your derived class destructor.
18
19       For the child windows, this event is generated just before deleting the
20       window from wxWindow:'Destroy'/1 (which is also called when the  parent
21       window is deleted) or from the window destructor if operator delete was
22       used directly (which is not recommended for this very reason).
23
24       It is usually pointless to handle this event in the window  itself  but
25       it ca be very useful to receive notifications about the window destruc‐
26       tion in the parent window or in any other  object  interested  in  this
27       window.
28
29       See: Overview events, wxWindowCreateEvent
30
31       This  class is derived (and can use functions) from: wxCommandEvent wx‐
32       Event
33
34       wxWidgets docs: wxWindowDestroyEvent
35

DATA TYPES

37       wxWindowDestroyEvent() = wx:wx_object()
38
39       wxWindowDestroy() =
40           #wxWindowDestroy{type =
41                                wxWindowDestroyEvent:wxWindowDestroyEventType()}
42
43       wxWindowDestroyEventType() = destroy
44
45
46
47wxWidgets team.                    wx 2.2.1            wxWindowDestroyEvent(3)