Hello,
I'm not sure i understand how this would work. If i use the serialization library, then i could serialize the current state (by inspecting the current state configuration as you said). But what would happen to all the members of the parent class (for example "simple_state" ) since they don't support serialization ? Unless you meant to use some other serialization method ?
As for the "special transitions", i suppose i would need a sort of "initial transition" per state that would allow me to go to it directly, right ? Also, if i have (and i sure will) state local storage, then i would need some way to restore its values, which i don't quite see how it would work using this approach (since i'm not re-creating the object using the one that was restored but rather using the transition).
Thanks,
Lukasz K.
Andreas Huber-3 wrote:
For non-orthogonal machines, saving the state is relatively easily done by
inspecting the current state configuration with the public interface
(state_machine<>.state_begin() & state_machine<>.state_end()). Loading is more
cumbersome as you need to be able to go to the previously stored state after
initiation. The only way to do this at the moment is to introduce special
transitions.
