make history state constructible

Decided in API review. The intention of QHistoryState not being
constructible was so that people wouldn't subclass it and reimplement
onEntry()/onExit(), thinking that those functions would actually get
called (which they won't). However, we recently added the entered()
signal to QAbstractState, so people are going to connect to it and
ask why they never get the signal for a QHistoryState. We might as
well make QHistoryState constructible and just document that it
doesn't make sense to subclass it.

1 files changed, 1 insertions, 1 deletions

diff --git a/examples/statemachine/pauseandresume/main.cpp b/examples/statemachine/pauseandresume/main.cpp
index e0ebbff..5bacb41 100644
--- a/examples/statemachine/pauseandresume/main.cpp
+++ b/examples/statemachine/pauseandresume/main.cpp
@@ -73,7 +73,7 @@ public:
         s1->addTransition(pb, SIGNAL(clicked()), s2);
         s2->addTransition(pb, SIGNAL(clicked()), s1);
 
-        QHistoryState *h = process->addHistoryState();
+        QHistoryState *h = new QHistoryState(process);
         h->setDefaultState(s1);
 
         QState *interrupted = new QState(machine->rootState());