[Qt-interest] Qt State machine framework

[Sean Harmer]

Hi Kent,

On Thursday 25 March 2010 10:08:31 Kent Hansen wrote:
> Mandeep Sandhu wrote:
> > I think it'll be helpful for the app developer to know where the SM
> > transitioned from, especially since we can can land up in the same
> > state from 2 different source states (obviously on 2 diff events at
> > different times). Some of these events are generated internally (from
> > an app's point of view). Just knowing the current state might not
> > suffice. OR it might, if we assume that it's the apps responsibility
> > to keep track of state transitions (I just tell it whenever a new
> > transition happens and the new state).
> 
> Would it help if QStateMachine had a configurationChanged() signal? That
> way you would have a central place to monitor state changes, and could
> record the configuration at each step if desired (a "trace" of the
> machine execution).

In principal yes, this would be useful. Would you envisage emitting this at 
the end of a complete SM step or after each micro-step?

Cheers,

Sean