I did this and the result is that the "terminated" event is not even
handled. I get this debug line:
005436 qx.util.fsm.FiniteStateMachine[52-0]: Fsm_1: Cannot listen to
event 'terminated', because the finite state machine is not running.
On 08/03/2016 11:42 μμ, Derrell Lipman wrote:
> So
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
Yeah, I see. That makes sense.
For now, just set your fsm variable to null. This doesn't help you if
you're trying to use the dispose debugging, but at least should ensure that
the memory does actually get garbage collected. At some point, I may try to
work out how to allow the dispose debugging
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
