Hello Dietrich, > One solution remains: > > myWindowInstance.destory() > qx.ui.core.queue.Dispose.flush(); > > But this feels somehow "inelegant". > > Any help from the qooxdoo staff would be great.
We recommend to use destroy for all widgets. Its the best way to make sure every code part we have written to get rid of the widget is executed. But as you said, its async and if you need it to be sync, you can take that „inelegant“ way, where I agree on the term of inelegant in that case. ;) I also agree on the rules peter mentioned in a common case. In the particular case its a bit more complicated because our HTML element usually takes care of removing the listener and the widget itself takes care of removing itself from its parent. This brings some convenience but on the other hand we loos some clarity of what needs to be disposed and what does the system automatically clean up. So I guess I won’t be happy with either of the two alternatives. ;) Regards, Martin ------------------------------------------------------------------------------ Sponsored by Intel(R) XDK Develop, test and display web and hybrid apps with a single code base. Download it for free now! http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
