Reusing is not necessary in this case, as I don't want to maintain all the windows in memory after being closed.
I have sometimes some widgets that are 'global' and are not attached to a particular parent, that's why he can dispose itself when it's not needed. Well it works almost like you said. Component A opens a window with component B in it. Component A forgets about component B, as doesn't have to care about it. Component B has a button "close/done" and when is clicked, is fired the 'close' event. Instead of doing this I would prefer the "close/done" action to auto-destroy itself and this could dispatch an event that has been destroyed. In this way the window-frame knows that it's content it's gone and can destroy itself too. But I could also continue doing with the 'close' event. thanks anyway -- View this message in context: http://qooxdoo.678.n2.nabble.com/What-event-if-any-is-dispatched-when-a-widget-is-destroyed-How-might-I-know-when-it-s-destroyed-tp7580745p7580777.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
