Frame has a single enter and exit event for each state, which can be handled to perform work when the state is entered or exited, respectively. However, state charts allow multiple entry/exit actions to be defined.
If we solve #59, then this functionality could be recovered with "internal events" by writing something like:
$Foo
|>|
action1 ()
action2 ()Where action1 and action2 are two different entry actions (represented in Frame as internal events) for state Foo.
However, there is still the challenge of how to show these entry actions in visualizations. A visualization of the above state Foo should include a label like entry/ action1, action2 (for example, see the description of action notation here).
As a special case, we could list all internal events called from enter/exit event handler as entry/exit actions in visualizations.
Another possible (but more complex) solution would be to provide direct support for registering multiple enter/exit events to be triggered for a given state.
Frame has a single enter and exit event for each state, which can be handled to perform work when the state is entered or exited, respectively. However, state charts allow multiple entry/exit actions to be defined.
If we solve #59, then this functionality could be recovered with "internal events" by writing something like:
Where
action1andaction2are two different entry actions (represented in Frame as internal events) for stateFoo.However, there is still the challenge of how to show these entry actions in visualizations. A visualization of the above state
Fooshould include a label likeentry/ action1, action2(for example, see the description of action notation here).As a special case, we could list all internal events called from enter/exit event handler as entry/exit actions in visualizations.
Another possible (but more complex) solution would be to provide direct support for registering multiple enter/exit events to be triggered for a given state.