Hi,
This is simple:
have a state that sends an event. That event has a "FINISH" transition, and lead to another state that sends your second event. Done.
What happens is that the first state sends that event, and straight away transit to the next state because it's finished ( assuming you are only using a send event action, no "every frame" actions, otherwise the "finish event doesn't trigger automatically).
So infact you could have a whole bunch of states doing a particular job in one go with no latency. I use that very much. for example I send an event, then for clarity I move to another state to set variables, then move to another state to do some checks and so on. All of them or instant actions as if part of the same "function" in normal scripting.
Splut up your tasks, It's perfectly acceptable to have one little thin to do per state, nothing wrong with that, don't try to be more "efficient" by stacking actions into one state, it will be better to organize and divide. it will pay off big time and really help you in the long run to debug, and come back to this fsm and understand what it does by just glancing, instead of opening each state and look at whyt actions does. This is something I try to avoid at all cost, I should not have to open a state to understand what it does, the state label should be enough ( with a description for more clarity).
Hope this helps,
Jean
