ENTER and EXIT are limited due to a lack of context. Perhaps a callback for every EXIT->ENTER combination, which also enables catching illegal state transitions if not defined.
Each would need to be contributed from that respective State though, which needs an API. Ex: For an A->B transition, Exit State A removes certain sprites from the screen and cleans up A, followed by Enter State B doing the reverse. A->C may do something else. No ideas for what this looks like yet.
ENTER and EXIT are limited due to a lack of context. Perhaps a callback for every EXIT->ENTER combination, which also enables catching illegal state transitions if not defined.
Each would need to be contributed from that respective State though, which needs an API. Ex: For an A->B transition, Exit State A removes certain sprites from the screen and cleans up A, followed by Enter State B doing the reverse. A->C may do something else. No ideas for what this looks like yet.