Reply To: FSM Design Issue

[chrisk]

Hi, Gavalakis,
Thanks for your positive feedback. It makes me I want to contribute to NC more and more. ^^

What I mean by PS is this.

I would like to extend FSM state by attaching properties, kind of like “decorator” concept in Behavior Tree.
In this way, for example, when “Any State”(you probably need to change the name) is attached to a “Action State”, it becomes the hanldler to the attached “Action State” and its “Nested Nodes” only.
(If “Any State” is not attached to any state, then, it will function as is right now.)
This way, it will give quite a bit of flexiblity to design FSM and it opens up for many other possiblities.
Attached node is kind of like a interceptor and it needs to have control options I mentioned in the previous message (it can interrupt the state it is attached, pause, go back to previous.. and so on).
On other words, attached node will get first chance to get executed, and then, the state it is attached to will get a chance to get executed next.
And depends on the option attached node has, the attahced state will pause, stop, simulteniously execute when attached node is executing.
“Any State” is just one example of the usecase and we can come up with many other type of attachable nodes in the future.

Hope it makes sense. ^^

Cheers!

-chris