Right. My suggestion is that you shouldn't need to call fsm.dispose().
Instead, just set
fsm = null;
so it will be garbage collected. I don't believe there is anything here
that needs "help" with disposing.
Here's the modified example: http://tinyurl.com/zxmbrcj
Cheers,
Derrell
On Tue, Mar 8, 2016 at 11:20 AM voger <vogernewslett...@yahoo.gr> wrote:
> I did a simple example of the problem. http://tinyurl.com/zg8nse2
>
> After some investigation with the debugger it seems that the problem is
> the fact that I am trying to dispose the fsm object using it's own event
> handler.
>
> A walk through to explain better what I mean:
>
> 1. In the final state I click the "Terminate" button.
> 2. The fsm object picks the "execute" event and starts processing it
> 3. One of the handlers decides to fsm.dispose()
> 4. The fsm isn't done yet with the "execute" event but the fsm it's gone
> now
> 5. Exception
>
>
> An idea how to terminate and dispose the fsm is to use some other event
> not observed by fsm. Something like this example
> http://tinyurl.com/jj7kfxt .
>
>
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> Transform Data into Opportunity.
> Accelerate data analysis in your applications with
> Intel Data Analytics Acceleration Library.
> Click to learn more.
> http://makebettercode.com/inteldaal-eval
> _______________________________________________
> qooxdoo-devel mailing list
> qooxdoo-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://makebettercode.com/inteldaal-eval
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
