[Qt-interest] Qt State machine framework

[Mandeep Sandhu]

>
> 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).

Yes! That would help provided we get the info about changes in the
"flat" states.

What No'am suggested
(http://doc.trolltech.com/4.6/qabstracttransition.html#triggered)
gives an indication the moment a transition happens. But as I
mentioned before, querying the src/target states might not necessarily
return the "flat" state (in case the target/src was a state group).

>
>> Also, I believe that concepts like history states/ state groups etc
>> are internal to the SM (since it's used only as a way to express the
>> SM). From the outside, even if I transition to state group (using
>> history or default state) I still should be able to find out what
>> child state I'm in, since that really represents the true state. The
>> caller is totally ignorant of the state group concept.
>>
>
> Well, QStateMachine::configuration() gives you a flat set of states.
>  From that you can determine which members of the set are the inner-most
> (child) states.

Ok. I'll check that...I haven't got around to trying this API.

Thanks,
-mandeep

>
> Kent
> _______________________________________________
> Qt-interest mailing list
> Qt-interest at trolltech.com
> http://lists.trolltech.com/mailman/listinfo/qt-interest
>