panghy@d7a2438
Even though the generated visualization of the FSM suggests that entering a parent state will automatically also activate its child state (prescribed by initialState<S>()). In reality, the automated activation of child initialState() only works on initial load of the FSM.
Perhaps there could have been a different way to indicate that subsequent entry of the parent state should also trigger transition to a child state (perhaps instead of initialState<S>(), one could imagine declaring activateChild<S>(), with the bonus of coregions automatically activating multiple children on entry, without the need for onFork()).
panghy@d7a2438
Even though the generated visualization of the FSM suggests that entering a parent state will automatically also activate its child state (prescribed by
initialState<S>()). In reality, the automated activation of childinitialState()only works on initial load of the FSM.Perhaps there could have been a different way to indicate that subsequent entry of the parent state should also trigger transition to a child state (perhaps instead of
initialState<S>(), one could imagine declaringactivateChild<S>(), with the bonus of coregions automatically activating multiple children on entry, without the need foronFork()).