Firing two events (alternatively) from a single action

[rhaschke]

Firing two events (alternatively) from a single action

[uyha]

I had the same problem with sml::back::process, I get around that by observing the state of the state machine from outside to decide what event to emit appropriately, and have sml::process directly in the make_transition_table call. In your case, to fix it, you can have a dummy transition to introduce the quit type to the state machine, otherwise it doesn't know about the quit type, hence the compilation error. https://godbolt.org/z/Pz1fsTrr8

[uyha]

An even "cleaner" workaround https://godbolt.org/z/T35ed6Ka9

[rhaschke]

Thanks a lot for this helpful trick to declare an otherwise unknown event.

[lisean789]

An even "cleaner" workaround https://godbolt.org/z/T35ed6Ka9

@uyha It looks like although there are no compile error for your work around, the "quit" event isn't propagated to the parent state. The only type of work around I know for now involves working from outside the state machine.