Hi! Correct! The magic is that the new operator is overloaded for all wxObject/wxWindow derived classes. So the framework knows which object have to be destroyed. Writing a destructor doesn't harm this process since I believe that the framework itself calls the destructors of the objects. Still, there are some objects you'd have to delete yourself, like when you create a wxString on the heap etc..
upCASE ----------------------------------- If it was hard to write, it should be hard to read!- Do. Or do not. There is no try! |