Hi all,
Just a code question here, and how best to manipulate Actions from external code. On our team we have a couple of designers who are building FSMs and as a programmer, I can just facilitate them by adding new Actions when needed. A rather nice arrangement so far!
However, as some of these new actions have dependencies on some of our systems, I'm looking into ways of setting the required data/pointers/etc on the actions via code, so that the designers don't have to drag a bunch of random game objects onto the action every time they use them. I'd like to avoid the use of singletons and just have their dependencies set externally if possible (i.e. dependency injection).
As such, would it be considered misuse of PlayMaker to do the following in a 'manager' class:
- find all FSMs in the scene
- iterate across all states in each fsm
- for each state, iterate across all actions
- if an action is a custom one with dependencies, set them via a property
Obviously it's a very expensive call, but it would only be called once on initialisation. I'd be interested to hear if anyone else has done something similar or has a better idea on how to do it.
Thanks!
