Debugger: Disable re-run from application output pane

... for QML engine, which currently does not handle state
transitions in that case.

The normal debug button (or <F5>) of course still work for
starting to debug the current project, which is in most
cases effectively the same.

Change-Id: I02ebf989030a6eb7ff919add6ccc20e7230d9cc1
Reviewed-by: David Schulz <david.schulz@theqtcompany.com>
This commit is contained in:
hjk
2016-04-13 11:11:03 +02:00
parent 7e56c2e09a
commit 641b511430
2 changed files with 7 additions and 0 deletions

View File

@@ -139,6 +139,12 @@ QString DebuggerRunControl::displayName() const
return m_engine->runParameters().displayName; return m_engine->runParameters().displayName;
} }
bool DebuggerRunControl::supportsReRunning() const
{
// QML and/or mixed are not prepared for it.
return m_engine && !(m_engine->runParameters().languages & QmlLanguage);
}
void DebuggerRunControl::start() void DebuggerRunControl::start()
{ {
Debugger::Internal::saveModeToRestore(); Debugger::Internal::saveModeToRestore();

View File

@@ -60,6 +60,7 @@ public:
StopResult stop() override; // Called from SnapshotWindow. StopResult stop() override; // Called from SnapshotWindow.
bool isRunning() const override; bool isRunning() const override;
QString displayName() const override; QString displayName() const override;
bool supportsReRunning() const override;
void startFailed(); void startFailed();
void notifyEngineRemoteServerRunning(const QByteArray &msg, int pid); void notifyEngineRemoteServerRunning(const QByteArray &msg, int pid);