diff options
| author | Kent Hansen <khansen@trolltech.com> | 2009-04-22 17:20:19 +0200 |
|---|---|---|
| committer | Kent Hansen <khansen@trolltech.com> | 2009-04-22 17:20:19 +0200 |
| commit | f87641584424deed25e2abdadea08c3be94b9ce1 (patch) | |
| tree | a185687744e724a8db896970416f23d20f5cad38 /src/corelib/statemachine/qfinalstate.h | |
| parent | 31f5348ea1691a7664b6abc04cf425dd02637b33 (diff) | |
kill the stateactions api
It just didn't give us that much.
Typically you just reimplement onEntry/onExit/onTransition
when you want to do something.
We go back to the signals-and-slots approach: states have
entered() and exited() signals that you can connect to.
It's still possible to have an action-based API, but then
you build it on top of the core API, which is OK.
Replacing 4 public classes (and one layer in the hierarchy)
with 2 signals feels good.
Diffstat (limited to 'src/corelib/statemachine/qfinalstate.h')
| -rw-r--r-- | src/corelib/statemachine/qfinalstate.h | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/src/corelib/statemachine/qfinalstate.h b/src/corelib/statemachine/qfinalstate.h index 36813f502b..726a399589 100644 --- a/src/corelib/statemachine/qfinalstate.h +++ b/src/corelib/statemachine/qfinalstate.h @@ -43,9 +43,9 @@ #define QFINALSTATE_H #ifndef QT_STATEMACHINE_SOLUTION -#include <QtCore/qactionstate.h> +#include <QtCore/qabstractstate.h> #else -#include "qactionstate.h" +#include "qabstractstate.h" #endif QT_BEGIN_HEADER @@ -55,7 +55,7 @@ QT_BEGIN_NAMESPACE QT_MODULE(Core) class QFinalStatePrivate; -class Q_CORE_EXPORT QFinalState : public QActionState +class Q_CORE_EXPORT QFinalState : public QAbstractState { Q_OBJECT public: |