31 May
2014
31 May
'14
5:18 p.m.
I can do (with msm.euml):
... SomeState + SomeEvent / SomeAction ...
But actually I want 'SomeState' to decide what it does on 'SomeEvent'.
Wouldn't it make sense to call, for example,
SomeState::operator()(SomeEvent const&)
(or a templated form of that) in that case ? Or maybe 'SomeState::on_internal(...)' ?
Any thoughts?
Regards, Stefan --
Hi Stefan, you can achieve the same with a transition table internal to a state, with the added bonus that you can have guards and therefore several possible actions depending on them. HTH, Christophe