Hi,
ok, sorry for the delay, was relaxing a bit last week...
so, I think I have something for you, which is basically how I did it for XmlMaker.
- you create a class that extends FsmStateAction class and you maintain your list of fsmVar
- you use this class as a public property inside your action
-- I have modified the custom action editor to edit this class and populate fsmVar inside this class.
This technic requires PlayMaker Utils set of tools, this removes a lot of the boiler plates needed to work with complex action editors. so I recommend you keep using these utils. Else you'll need to extract the various tools.
Let me know if this all make sense to you ok?
the major constraint as before is that the fsm var can only be the one from the fsm where the action is, not from the FsmOwnerDefault, in that case you'll need to use strings as the reference to the variable name on other fsms.
Bye,
Jean