Mustafa, thanks for your answer. But why should I dispose menu buttons if they are disposed automatically as children widgets? If the problem is in subwidgets and commands disposal order, how should I organize the Menu class to accurately dispose all the created commands? But before developing this direction of thoughts...
A want to ask developers: why menuButton doesn't unbound a coupled Command on destruction? As deep as I managed to dig out, my problem arise from the fact that in the destructor of the menuButton (actually, MExecutable mixin) there is no this.setCommand(null); but only this._applyCommand(null, this.getCommand()); When I replace the latter operator with the former one, my error dissappears. I dare to assume that the problem is that after MExecutable.destruct() a situation comes when _applyCommand(null, ...) is called but the property "command" is still not null. -- View this message in context: http://qooxdoo.678.n2.nabble.com/Disposing-Commands-in-menu-destructor-tp7585184p7585187.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
