Capability to set the current state without doing transitions

[JimWuerch]

I'd like the ability to set current without firing off any transitions or checking any conditions.

The reason is for setting the machine state when handling an undo, or loading from a save. Since the state of the world gets reverted during an undo, I'd like to be able to just set the state machine to be in the same state as it was also. Similarly, when loading state from disk, being able to set things as they were would be useful too.

Being able to specify the start state (instead of having to create a new one with how set start works now) would also work, as I could just set the start state to the previous state and start the machine.

[renggli]

Added the possibility to call machine.setState(state, skipBeforeEvent: true, skipAfterEvent: true). Let me know if that solves your issue?

[JimWuerch]

Looks like transition.activate and transition.deactivate still gets called. I think what I'd like is just something like _current = state, as anything a state transition would've caused will already be restored, so I'm looking to just restore _current. For undo, _current is all that matters, and for a restore situation, the rest of the machine data can be restored with the existing members.

[renggli]

Hmm, but that is strange to not call activate() and deactivate(). Some transition types have assertions and break if the two methods are not called in the right order. Maybe you could wrap your handlers with some predicate that checks if they are called from within an undo operation?

[JimWuerch]

Looking at the transitions, I'd guess I'd have to not add callbacks, and just use the before and after events. Given the stream and time based transitions, I can see that it makes sense not to allow setting _current directly. I think I can work with just disabling the events. Thanks for the quick update!

I think I'd only allow states with the simplest transitions inside areas that can be undo'd, which should be good enough, and I can work around the states firing off callbacks during undo.