Hi,
Following my last post, I have to expand on this:
State actions really make State versatile ( obviously... ), they can be instant, synched, waiting, animating, accessing other fsm somehow, etc etc, it's currently impossible to make sure about the behavior of a State on that level just at a glance.
Her is a list of things that could be identified as actions "properties" are added and that I think should be presented visually in the fsm.
-- number of actions:
-- instant or not:
it's important to see if State is just a one time thing that will then straight away transit, or if it will last in time ( if everyframe is checked or not for example).
-- access variable:
It's really important to glance through state and know that a particular one is accessing ( setting or getting ) any variable at all.
-- other fsm access:
Equally important to know when the fsm talk to other
-- Script access:
same as above.
I am sure other properties like that can be listed here, but you get the point I think.
I played in photoshop to demonstrate visually one humble possible way. Just some simple icons or visual elements representing each something specific about the State.
Oh and while we are at it, if from the script api we could tweak that, say we want to add a custom icon somewhere. It could actually be simply a matter of doing it like that, each action can set certain flags that triggers the visual clues in that State . Fsm.State.FlagFsmAccess, Fsm.State.FlagAsTimeSpan etc etc That could be a simple way to do this.
Bye,
Jean