When trying to animate several statemachines in the same machine, switching between statemachines (e.g. to fire a transition) causes a 'resource has changed, reload?' message and a subsequent exception in the animation listener.
This is due to the editors 'deactivation' listener (which is listening to all parts in the page) not being selective about responding to only its parent editor.
However, even if this is fixed, the deactivation triggered when the animation is started causes an exception because, for some statemachines, it tries to save an animating diagram and the animation attributes are not persisted correctly (perhaps they should be transient). The diagrams that it tries to save are ones that have no active states or enabled operations at animation startup (e.g. a lifted statemachine). A fix would be to attach an 'animating' attribute to the statemachine when the animation is started.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is due to the editors 'deactivation' listener (which is listening to all parts in the page) not being selective about responding to only its parent editor.
However, even if this is fixed, the deactivation triggered when the animation is started causes an exception because, for some statemachines, it tries to save an animating diagram and the animation attributes are not persisted correctly (perhaps they should be transient). The diagrams that it tries to save are ones that have no active states or enabled operations at animation startup (e.g. a lifted statemachine). A fix would be to attach an 'animating' attribute to the statemachine when the animation is started.
fixed for next release:
deactivation listener improved,
improvements to animation