On Sunday 06 July 2014 23:55:14 BogDan wrote:
[..]
I presume that changing the semantics here (i.e. triggering
QAbstractState::onExited when the machine is stopped) isn't appropriate,
as it may break existing applications, but I'm not exactly sure.
I think it would be far less risk of
[..]
I presume that changing the semantics here (i.e. triggering
QAbstractState::onExited when the machine is stopped) isn't appropriate,
as it may break existing applications, but I'm not exactly sure.
I think it would be far less risk of breaking existing applications to simply
set active
Kevin Funk wrote:
I presume that changing the semantics here (i.e. triggering
QAbstractState::onExited when the machine is stopped) isn't appropriate,
as it may break existing applications, but I'm not exactly sure.
I think it would be far less risk of breaking existing applications to
Hey there,
We are currently making the QStateMachine QML-ready by amending all the QSM-
related classes (derived from QAbstractState, QAbstractTransition) and adding
Q_PROPERTYs macro where needed. You can see a list of already merged changes
here [1].
All of this work in qtbase is supposed to
