summaryrefslogtreecommitdiff
path: root/src/scripttools/debugging
diff options
context:
space:
mode:
authorCasper van Donderen <casper.vandonderen@nokia.com>2012-06-05 12:51:07 +0200
committerQt by Nokia <qt-info@nokia.com>2012-06-05 15:18:03 +0200
commit4629dc71525a638c0bae89ad67990a1ff14ea9c4 (patch)
treeff81b70586896e7b2f1c718e3b5385fae4483cc3 /src/scripttools/debugging
parentf6fdd296d47e1ce44c07aab81098c20a5260f7fd (diff)
downloadqtscript-4629dc71525a638c0bae89ad67990a1ff14ea9c4.tar.gz
Doc: Modularize QtScript documentation.
Change-Id: I042d9bafe4f48a8cd23306f0864b6872776d0153 Reviewed-by: Kent Hansen <kent.hansen@nokia.com>
Diffstat (limited to 'src/scripttools/debugging')
-rw-r--r--src/scripttools/debugging/qscriptenginedebugger.cpp10
1 files changed, 5 insertions, 5 deletions
diff --git a/src/scripttools/debugging/qscriptenginedebugger.cpp b/src/scripttools/debugging/qscriptenginedebugger.cpp
index 3a1333b..b6a8eef 100644
--- a/src/scripttools/debugging/qscriptenginedebugger.cpp
+++ b/src/scripttools/debugging/qscriptenginedebugger.cpp
@@ -86,7 +86,7 @@ public:
To attach the debugger to a script engine, call the attachTo()
function.
- \snippet doc/src/snippets/code/src.scripttools.qscriptenginedebugger.cpp 0
+ \snippet code/src.scripttools.qscriptenginedebugger.cpp 0
Once the debugger has been attached to a script engine, you can
proceed to evaluate scripts as usual, e.g. by calling
@@ -98,7 +98,7 @@ public:
you trigger the action before you begin to \l{QScriptEngine::}{evaluate()}
the script.
- \snippet doc/src/snippets/scriptdebugger.cpp 2
+ \snippet scriptdebugger.cpp 2
By default, the \l{standardWindow()}{standard debugger window} is shown when
evaluation is suspended. This can be changed by calling the
@@ -140,7 +140,7 @@ public:
the function call does not return until the user has finished
interacting with the debugger.
- \snippet doc/src/snippets/code/src.scripttools.qscriptenginedebugger.cpp 1
+ \snippet code/src.scripttools.qscriptenginedebugger.cpp 1
When the Qt Script debugger is running, the C++ application itself
is not "frozen". This means that it is possible that more scripts
@@ -431,7 +431,7 @@ QScriptEngineDebugger::DebuggerState QScriptEngineDebugger::state() const
\l{QScriptEngineDebugger::CodeWidget}{code window} and a
\l{QScriptEngineDebugger::StackWidget}{stack widget}.
- \snippet doc/src/snippets/scriptdebugger.cpp 0
+ \snippet scriptdebugger.cpp 0
Note that you need to set setAutoShowStandardWindow() to false; if
not, the standard window will be shown regardless.
@@ -454,7 +454,7 @@ QWidget *QScriptEngineDebugger::widget(DebuggerWidget widget) const
wish to spice things up with your own groovy icons. The code
example below shows how to add actions to a QToolBar.
- \snippet doc/src/snippets/scriptdebugger.cpp 1
+ \snippet scriptdebugger.cpp 1
Note that QScriptEngineDebugger has already added the actions to
its \l{DebuggerWidget}{standard widgets} and \l{standardWindow()}{standard window}.