diff options
| author |  Tomaz Canabrava <tcanabrava@kde.org> | 2014-02-06 15:38:32 -0200 |
|---|---|---|
| committer |  Dirk Hohndel <dirk@hohndel.org> | 2014-02-06 11:32:44 -0800 |
| commit | 677e75fbe4be9d0d283be5859409a1f4f75e4444 (patch) | |
| tree | 090d1384ae06b9f2ea8b64fc869b848a38438c73 | |
| parent | 49f8456ce8772e1a4a0cc3eed5786db13ff0ece7 (diff) | |
| download | subsurface-677e75fbe4be9d0d283be5859409a1f4f75e4444.tar.gz | |
Process events just after starting the StateMachine
This is needed because of a braindead issue on the Qt event
loop:
http://stackoverflow.com/questions/10059721/qt-qstatemachine-sync-problems-initial-state-not-set-on-started-signali
For the "event 1" to be received, the machine must already be
in a state that react to that signal. Even it was a queued
connection, the slot would be queued but only after the signal
was received, which it isn't since there is no connection
yet at that point.
To solve your problem, you can wait for the machine is in
"state A" before emitting the signal:
machine->start();
qApp->processEvents();
Signed-off-by: Tomaz Canabrava <tcanabrava@kde.org>
Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
| -rw-r--r-- | qt-ui/profile/profilewidget2.cpp | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/qt-ui/profile/profilewidget2.cpp b/qt-ui/profile/profilewidget2.cpp index 3f6be0389..4ebc8c3ee 100644 --- a/qt-ui/profile/profilewidget2.cpp +++ b/qt-ui/profile/profilewidget2.cpp @@ -292,6 +292,7 @@ ProfileWidget2::ProfileWidget2(QWidget *parent) : // Starting the transitions: stateMachine->start(); + qApp->processEvents(); scene()->installEventFilter(this); #ifndef QT_NO_DEBUG QTableView *diveDepthTableView = new QTableView(); |