summaryrefslogtreecommitdiff
path: root/src/scripttools/debugging/qscriptenginedebugger.cpp
diff options
context:
space:
mode:
Diffstat (limited to 'src/scripttools/debugging/qscriptenginedebugger.cpp')
-rw-r--r--src/scripttools/debugging/qscriptenginedebugger.cpp18
1 files changed, 9 insertions, 9 deletions
diff --git a/src/scripttools/debugging/qscriptenginedebugger.cpp b/src/scripttools/debugging/qscriptenginedebugger.cpp
index b6df016..0a4ae85 100644
--- a/src/scripttools/debugging/qscriptenginedebugger.cpp
+++ b/src/scripttools/debugging/qscriptenginedebugger.cpp
@@ -1,6 +1,6 @@
/****************************************************************************
**
-** Copyright (C) 2012 Digia Plc and/or its subsidiary(-ies).
+** Copyright (C) 2013 Digia Plc and/or its subsidiary(-ies).
** Contact: http://www.qt-project.org/legal
**
** This file is part of the QtSCriptTools module of the Qt Toolkit.
@@ -70,12 +70,12 @@ public:
};
/*!
- \since 4.5
- \class QScriptEngineDebugger
+ \since 4.5
+ \class QScriptEngineDebugger
+ \inmodule QtScriptTools
+ \brief The QScriptEngineDebugger class provides a QScriptEngine debugger.
- \brief The QScriptEngineDebugger class provides a QScriptEngine debugger.
-
- \ingroup script
+ \ingroup script
The QScriptEngineDebugger class provides a debugger that can be
@@ -86,7 +86,7 @@ public:
To attach the debugger to a script engine, call the attachTo()
function.
- \snippet code/src.scripttools.qscriptenginedebugger.cpp 0
+ \snippet 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
@@ -140,7 +140,7 @@ public:
the function call does not return until the user has finished
interacting with the debugger.
- \snippet code/src.scripttools.qscriptenginedebugger.cpp 1
+ \snippet 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
@@ -166,7 +166,7 @@ public:
currently not supported. If you need to debug painting-related
script code, that code should be evaluated outside of the C++
paintEvent(), e.g. by rendering to an image, like the Context2D and
- Tetrix QtScript examples do. This will make the code safe for
+ Tetrix Qt Script examples do. This will make the code safe for
debugging.
The debugger adds some special properties to the script engine: