feedc0de/qt-creator
1
0
Fork 0
forked from qt-creator/qt-creator
Code Pull Requests Activity

QmlDebug: Fix typo

Browse Source 
Change-Id: I5e316ada7d03c465a7f60246e2c04e1a89078689
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
This commit is contained in:
Ulf Hermann
2014-09-12 15:44:30 +02:00
parent 84d5afcbf4
commit 0234148249
1 changed files with 7 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
src/libs/qmldebug/qmlenginecontrolclient.cpp
View File

@@ -38,12 +38,13 @@ QmlEngineControlClient::QmlEngineControlClient(QmlDebugConnection *client)
}
/*!
* Block the staring or stopping of the engine with id \a engineId for now. By calling releaseEngine
* later the block can be lifted again. In the debugged application the engine control server waits
* until a message is received before continuing. So by not sending a message here we delay the
* process. Blocks add up. You have to call releaseEngine() as often as you've called blockEngine
* before. The intention of that is to allow different debug clients to use the same engine control
* and communicate with their respective counterparts before the QML engine starts or shuts down.
* Block the starting or stopping of the engine with id \a engineId for now. By calling
* releaseEngine later the block can be lifted again. In the debugged application the engine control
* server waits until a message is received before continuing. So by not sending a message here we
* delay the process. Blocks add up. You have to call releaseEngine() as often as you've called
* blockEngine before. The intention of that is to allow different debug clients to use the same
* engine control and communicate with their respective counterparts before the QML engine starts or
* shuts down.
*/
void QmlEngineControlClient::blockEngine(int engineId)
{