Hi Voger, wouldn't decoupling the disposal from the event do the magic?
In https://github.com/voger/fsmtest/blob/master/source/class/fsmtest/Application.js#L157 Instead of doing fsm.dispose() console.log("fsm.isDisposed(): "+ fsm.isDisposed()); I'd do qx.event.Timer.once(function() { fsm.dispose(); console.log("fsm.isDisposed(): "+ fsm.isDisposed()); fsm = null; }, this, 0); I mean besides all discussion if dispose is needed at all. Dietrich Am 09.03.2016 um 21:58 schrieb voger: > Thank you. I will just set it null and let GC do it's magic. > Just in case it is of any help I created a simple project with the test > case from the playground example. I posted it in github > https://github.com/voger/fsmtest > > The problem is this line in qx.util.fsm.FiniteStateMachine > > this.__savedStates = this.__states = null; > > When the fsm tries to continue processing the event these arrays are > already set to null. > > BTW I forgot to say thank you for the whole FSM mechanism. It is indeed > a great tool that I recently discovered and it will help me to do things > I considered very difficult. Thank you. :D > > ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785111&iu=/4140 _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
