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

Move QmlConsole to Debugger

Browse Source 
Now it is closer to its only user and possibly reusable for no-QML uses
there.  We also drop the QML/JS syntax checker. The application being
debugged can already tell us about syntax errors. There is no need to
duplicate that functionality.

Change-Id: I2ba151f9f4c854c6119ba5462c21be40bddcebf9
Reviewed-by: Ulf Hermann <ulf.hermann@theqtcompany.com>
Reviewed-by: hjk <hjk@theqtcompany.com>
This commit is contained in:
hjk
2015-11-10 16:59:02 +01:00
committed by Ulf Hermann
parent 0e76b99108
commit 33651877d8
41 changed files with 381 additions and 804 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
doc/src/debugger/qtquick-debugging.qdoc
View File

@@ -158,17 +158,17 @@
\section1 Executing JavaScript Expressions
When the application is interrupted by a breakpoint, you can use the
\uicontrol {QML/JS Console} to execute JavaScript expressions in the current
\uicontrol {Debugger Console} to execute JavaScript expressions in the current
context. To open it, choose \uicontrol Window > \uicontrol {Output Panes}
> \uicontrol {QML/JS Console}.
> \uicontrol {Debugger Console}.
\image qml-script-console.png "QML/JS Console"
\image qml-script-console.png "Debugger Console"
For more information about using the console, see \l{QML/JS Console}.
For more information about using the console, see \l{Debugger Console}.
\section1 Applying QML Changes at Runtime
When you change property values in the \uicontrol {QML/JS Console} or in the
When you change property values in the \uicontrol {Debugger Console} or in the
\uicontrol {Locals and Expressions} view, they are immediately updated in the running
application, but not in the source code.