aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorSze Howe Koh <szehowe.koh@gmail.com>2013-12-30 12:15:09 +0800
committerThe Qt Project <gerrit-noreply@qt-project.org>2013-12-30 12:13:29 +0100
commitef9f85ad8d2774cb11cbd8cfc5943af2dcf72339 (patch)
tree1409941f61672ee025f2193040cb03bad43fed21
parent4a82ea4a609ecf728e3d5ed2033461e547470103 (diff)
Doc: Fix broken links
Change-Id: I4c4577edde96978a986606bf30fbb925f871bd42 Reviewed-by: Topi Reiniö <topi.reinio@digia.com>
-rw-r--r--examples/qml/qml-i18n/doc/src/i18n.qdoc2
-rw-r--r--src/particles/qquickparticlesystem.cpp2
-rw-r--r--src/qml/doc/qtqml.qdocconf2
-rw-r--r--src/qml/doc/src/cppintegration/exposecppattributes.qdoc2
-rw-r--r--src/qml/doc/src/javascript/qmlglobalobject.qdoc2
-rw-r--r--src/qml/doc/src/qmlfunctions.qdoc5
-rw-r--r--src/qml/doc/src/qmllanguageref/documents/scope.qdoc5
-rw-r--r--src/qml/doc/src/qmllanguageref/documents/structure.qdoc4
-rw-r--r--src/qml/doc/src/qmllanguageref/modules/qmldir.qdoc5
-rw-r--r--src/qml/doc/src/qmllanguageref/modules/topic.qdoc6
-rw-r--r--src/qml/doc/src/qmllanguageref/syntax/imports.qdoc2
-rw-r--r--src/qml/doc/src/qmllanguageref/syntax/signals.qdoc2
-rw-r--r--src/qml/doc/src/whatsnew.qdoc6
-rw-r--r--src/qml/jsapi/qjsvalue.cpp2
-rw-r--r--src/qml/qml/qqmlfileselector.cpp2
-rw-r--r--src/qml/qml/v8/qqmlbuiltinfunctions.cpp4
-rw-r--r--src/quick/doc/qtquick.qdocconf2
-rw-r--r--src/quick/doc/src/advtutorial.qdoc10
-rw-r--r--src/quick/doc/src/concepts/effects/particles.qdoc2
-rw-r--r--src/quick/doc/src/concepts/input/focus.qdoc2
-rw-r--r--src/quick/doc/src/concepts/modelviewsdata/cppmodels.qdoc6
-rw-r--r--src/quick/doc/src/concepts/modelviewsdata/modelview.qdoc3
-rw-r--r--src/quick/doc/src/concepts/modelviewsdata/topic.qdoc2
-rw-r--r--src/quick/doc/src/concepts/positioning/righttoleft.qdoc2
-rw-r--r--src/quick/doc/src/concepts/positioning/topic.qdoc2
-rw-r--r--src/quick/doc/src/concepts/statesanimations/animations.qdoc5
-rw-r--r--src/quick/doc/src/examples.qdoc4
-rw-r--r--src/quick/doc/src/qmltypereference.qdoc4
-rw-r--r--src/quick/doc/src/tutorial.qdoc6
-rw-r--r--src/quick/doc/src/whatsnew.qdoc9
-rw-r--r--src/quick/items/context2d/qquickcanvasitem.cpp2
-rw-r--r--src/quick/items/context2d/qquickcontext2d.cpp3
-rw-r--r--src/quick/items/qquickdrag.cpp2
-rw-r--r--src/quick/items/qquickdroparea.cpp6
-rw-r--r--src/quick/items/qquickfocusscope.cpp2
-rw-r--r--src/quick/items/qquickgridview.cpp2
-rw-r--r--src/quick/items/qquickitem.cpp6
-rw-r--r--src/quick/items/qquickitemanimation.cpp2
-rw-r--r--src/quick/items/qquickitemviewtransition.cpp2
-rw-r--r--src/quick/items/qquicklistview.cpp2
-rw-r--r--src/quick/items/qquickloader.cpp2
-rw-r--r--src/quick/items/qquickscreen.cpp4
-rw-r--r--src/quick/items/qquickwindow.cpp2
-rw-r--r--src/quick/util/qquickanimation.cpp2
44 files changed, 75 insertions, 76 deletions
diff --git a/examples/qml/qml-i18n/doc/src/i18n.qdoc b/examples/qml/qml-i18n/doc/src/i18n.qdoc
index 5a61906497..8257f30ba8 100644
--- a/examples/qml/qml-i18n/doc/src/i18n.qdoc
+++ b/examples/qml/qml-i18n/doc/src/i18n.qdoc
@@ -40,7 +40,7 @@
\endcode
Translations for new languages are created by copying \e i18n/base.ts to \e i18n/qml_<lang>.ts
- The .ts files can then be edited with \l {Qt Linguist}:
+ The .ts files can then be edited with \l{Qt Linguist}:
\code
linguist i18n/qml_fr.ts
diff --git a/src/particles/qquickparticlesystem.cpp b/src/particles/qquickparticlesystem.cpp
index b95b084756..429a423c17 100644
--- a/src/particles/qquickparticlesystem.cpp
+++ b/src/particles/qquickparticlesystem.cpp
@@ -193,7 +193,7 @@ DEFINE_BOOL_CONFIG_OPTION(qmlParticlesDebug, QML_PARTICLES_DEBUG)
Stops the simulation if it is running, and then starts it.
- \sa stop, restart, running
+ \sa start, stop, running
*/
/*!
\qmlmethod QtQuick.Particles::ParticleSystem::reset()
diff --git a/src/qml/doc/qtqml.qdocconf b/src/qml/doc/qtqml.qdocconf
index 74aaae7724..43dbe2525c 100644
--- a/src/qml/doc/qtqml.qdocconf
+++ b/src/qml/doc/qtqml.qdocconf
@@ -34,7 +34,7 @@ qhp.QtQml.subprojects.qmltypes.sortPages = true
tagfile = ../../../doc/qtqml/qtqml.tags
-depends += qtcore qtxmlpatterns qtgui qtquick qtdoc
+depends += qtcore qtxmlpatterns qtgui qtquick qtdoc qtlinguist
headerdirs += .. \
../../imports/models
diff --git a/src/qml/doc/src/cppintegration/exposecppattributes.qdoc b/src/qml/doc/src/cppintegration/exposecppattributes.qdoc
index d3662fb210..5d70cb5174 100644
--- a/src/qml/doc/src/cppintegration/exposecppattributes.qdoc
+++ b/src/qml/doc/src/cppintegration/exposecppattributes.qdoc
@@ -477,7 +477,7 @@ MessageBoard {
As with property values and method parameters, a signal parameter must have a
type that is supported by the QML engine; see
-\l {Semantics of Data Transfer from C++ to QML}. (Using an
+\l {Data Type Conversion Between QML and C++}. (Using an
unregistered type will not generate an error, but the parameter value will
not be accessible from the handler.)
diff --git a/src/qml/doc/src/javascript/qmlglobalobject.qdoc b/src/qml/doc/src/javascript/qmlglobalobject.qdoc
index cbffcddb7b..4329bbb351 100644
--- a/src/qml/doc/src/javascript/qmlglobalobject.qdoc
+++ b/src/qml/doc/src/javascript/qmlglobalobject.qdoc
@@ -38,7 +38,7 @@ additional imports:
\li The \l{QmlGlobalQtObject}{Qt object}: This object is specific to QML, and provides helper methods
and properties specific to the QML environment.
\li qsTr(), qsTranslate(), qsTrId(), QT_TR_NOOP(), QT_TRANSLATE_NOOP(), and QT_TRID_NOOP() functions:
- These functions are specific to QML, and provide \l{Translation}{translation capabilities} to the QML environment.
+ These functions are specific to QML, and provide \l{Overview of the Translation Process}{translation capabilities} to the QML environment.
\li gc() function: This function is specific to QML, and provides a way to manually trigger garbage collection.
\li print() function: This function is specific to QML, and provides a simple way to output information to the console.
\li The \l{Console API}{console object}: This object implements a subset of the \l{http://getfirebug.com/wiki/index.php/Console_API}{FireBug Console API}.
diff --git a/src/qml/doc/src/qmlfunctions.qdoc b/src/qml/doc/src/qmlfunctions.qdoc
index 679f7bac96..19cd3b3f02 100644
--- a/src/qml/doc/src/qmlfunctions.qdoc
+++ b/src/qml/doc/src/qmlfunctions.qdoc
@@ -42,7 +42,8 @@
specified \a Flags.
Current the only supported type info is \c QML_HAS_ATTACHED_PROPERTIES which
- declares that the \a Type supports \l {Attached Properties}.
+ declares that the \a Type supports \l {Attached Properties and Attached Signal Handlers}
+ {attached properties}.
#include <QtQml> to use this macro.
*/
@@ -51,7 +52,7 @@
\fn void qmlClearTypeRegistrations()
\relates QQmlEngine
- Clears all stored type registrations, such as those produced with \l qmlRegisterType.
+ Clears all stored type registrations, such as those produced with \l qmlRegisterType().
Do not call this function while a QQmlEngine exists or behavior will be undefined.
Any existing QQmlEngines must be deleted before calling this function. This function
diff --git a/src/qml/doc/src/qmllanguageref/documents/scope.qdoc b/src/qml/doc/src/qmllanguageref/documents/scope.qdoc
index 870eb21a07..845ca30b4f 100644
--- a/src/qml/doc/src/qmllanguageref/documents/scope.qdoc
+++ b/src/qml/doc/src/qmllanguageref/documents/scope.qdoc
@@ -79,7 +79,7 @@ with local variables declared in another.
\l {QML Documents} include import statements that define the type names
and JavaScript files visible to the document. In addition to their use in the
QML declaration itself, type names are used by JavaScript code when accessing
-\l {Attached Properties} and enumeration values.
+\l {Attached Properties and Attached Signal Handlers}{attached properties} and enumeration values.
The effect of an import applies to every property binding, and JavaScript
function in the QML document, even those in nested inline components. The
@@ -123,7 +123,8 @@ directly, without needing any form of object prefix. QML introduces a more
structured, object-oriented approach to JavaScript, and consequently does not
require the use of the JavaScript \c this property.
-Care must be used when accessing \l {Attached Properties} from bindings due
+Care must be used when accessing \l {Attached Properties and Attached Signal Handlers}
+{attached properties} from bindings due
to their interaction with the scope object. Conceptually attached properties
exist on \e all objects, even if they only have an effect on a subset of those.
Consequently unqualified attached property reads will always resolve to an
diff --git a/src/qml/doc/src/qmllanguageref/documents/structure.qdoc b/src/qml/doc/src/qmllanguageref/documents/structure.qdoc
index c8176f7e0f..e526e47b00 100644
--- a/src/qml/doc/src/qmllanguageref/documents/structure.qdoc
+++ b/src/qml/doc/src/qmllanguageref/documents/structure.qdoc
@@ -57,8 +57,8 @@ presentation to the \l{QQmlEngine}{QML engine}, unlike C or C++.
The \c import statements do not copy and prepend the code in the document, but
instead instruct the QML engine on how to resolve type references found
in the document. Any type reference present in a QML document - such as \c
-Rectangle and \c ListView - including those made within an \l {Inline
-JavaScript}{JavaScript block} or \l {Property Binding}{property
+Rectangle and \c ListView - including those made within a \l {JavaScript
+Expressions in QML Documents}{JavaScript block} or \l {Property Binding}{property
bindings}, are \e resolved based exclusively on the import statements. At least
one \c import statement must be present such as \c{import QtQuick 2.0}.
diff --git a/src/qml/doc/src/qmllanguageref/modules/qmldir.qdoc b/src/qml/doc/src/qmllanguageref/modules/qmldir.qdoc
index 57d54e27e0..c89d4a3c0d 100644
--- a/src/qml/doc/src/qmllanguageref/modules/qmldir.qdoc
+++ b/src/qml/doc/src/qmllanguageref/modules/qmldir.qdoc
@@ -62,7 +62,7 @@ module <ModuleIdentifier>
The <ModuleIdentifier> is the (dotted URI notation) identifier
for the module, which must match the module's install path.
- The \l{qtqml-modules-topic.html#the-module-identifier-directive}
+ The \l{Identified Modules#Semantics of Identified Modules}
{module identifier directive} must be the first line of the file.
Exactly one module identifier directive may exist in the \c qmldir
file.
@@ -113,7 +113,8 @@ internal MyPrivateType MyPrivateType.qml
\endcode
This is necessary if the module may be imported remotely (see
- \l{Remotely Installed Modules}) because if an exported type depends
+ \l{Identified Modules#Remotely Installed Identified Modules}
+ {Remotely Installed Identified Modules}) because if an exported type depends
on an non-exported type within the module, the engine must also
load the non-exported type.
diff --git a/src/qml/doc/src/qmllanguageref/modules/topic.qdoc b/src/qml/doc/src/qmllanguageref/modules/topic.qdoc
index 597e7b7ca3..9d4173a883 100644
--- a/src/qml/doc/src/qmllanguageref/modules/topic.qdoc
+++ b/src/qml/doc/src/qmllanguageref/modules/topic.qdoc
@@ -64,15 +64,15 @@ The directory can then be installed into the
\l{qtqml-syntax-imports.html#qml-import-path}{QML import path} as a module.
Note that defining a module is not the only way to share common QML types
-within a project - a simple \l{qtqml-syntax-imports.html#directory-import}
+within a project - a simple \l{Importing QML Document Directories}
{QML document directory import} may also be used for this purpose.
\section1 Supported QML Module Types
There are two different types of modules supported by QML:
\list
-\li \l{qtqml-modules-identifiedmodules.html}{Identified Modules}
-\li \l{qtqml-modules-legacymodules.html}{Legacy Modules} (deprecated)
+\li \l{Identified Modules}
+\li \l{Legacy Modules} (deprecated)
\endlist
Identified modules explicitly define their identifier and are installed into
diff --git a/src/qml/doc/src/qmllanguageref/syntax/imports.qdoc b/src/qml/doc/src/qmllanguageref/syntax/imports.qdoc
index 1496a1e5c9..0939a460fe 100644
--- a/src/qml/doc/src/qmllanguageref/syntax/imports.qdoc
+++ b/src/qml/doc/src/qmllanguageref/syntax/imports.qdoc
@@ -281,7 +281,7 @@ JavaScript resources, please see the in-depth documentation about
\section1 QML Import Path
-When an \l{qtqml-modules-installedmodules.html}{installed module} is imported,
+When an \l{Identified Modules}{identified module} is imported,
the QML engine searches the \e{import path} for a matching module.
This import path, as returned by QQmlEngine::importPathList(), defines the
diff --git a/src/qml/doc/src/qmllanguageref/syntax/signals.qdoc b/src/qml/doc/src/qmllanguageref/syntax/signals.qdoc
index 6344d16caa..b9f391e4dc 100644
--- a/src/qml/doc/src/qmllanguageref/syntax/signals.qdoc
+++ b/src/qml/doc/src/qmllanguageref/syntax/signals.qdoc
@@ -142,7 +142,7 @@ Rectangle {
\section2 Attached Signal Handlers
-An \l {attached signal handler} is a signal handler that receives a signal from an \e {attaching type} rather than the object within which the handler is declared.
+An \l {Attached Properties and Attached Signal Handlers}{attached signal handler} is a signal handler that receives a signal from an \e {attaching type} rather than the object within which the handler is declared.
For example, \c \l {Component::isCompleted}{Component.isCompleted} is an attached signal handler. This handler is often used to execute some JavaScript code when its creation process has been completed, as in the example below:
diff --git a/src/qml/doc/src/whatsnew.qdoc b/src/qml/doc/src/whatsnew.qdoc
index a0e5202174..f13a4dac1d 100644
--- a/src/qml/doc/src/whatsnew.qdoc
+++ b/src/qml/doc/src/whatsnew.qdoc
@@ -36,10 +36,10 @@ a summary of the new changes:
\list
\li New QQmlApplicationEngine convenience class for QML applications.
\li New Instantiatior type for generic, dynamic object creation.
-\li New properties for \l Qt.application: arguments, name, and version.
+\li New properties for \l {Qt::application}{Qt.application}: arguments, name, and version.
\li The 'with' statement has been deprecated and is slated for removal in a
future version of the language.
-\li New \l Qt.platform object with an os property
+\li New \l {Qt::platform}{Qt.platform} object with an \c os property
\li New \l qmlClearTypeRegistrations() function drops all data from qmlRegisterType() calls
\li New \l qmlRegisterType() function for registering composite types.
\endlist
@@ -48,7 +48,7 @@ a summary of the new changes:
The \l{Qt QML Models QML Types}{Qt QML Models} is a new submodule in Qt 5.1 and
provides several QML types for handling data with models and lists. These types
-replace types such as \l VisualItem, \l VisualDataModel, and \l VisualDataGroup.
+replace types such as \l VisualItemModel, \l VisualDataModel, and \l VisualDataGroup.
\list
\li \l{Qt QML Models QML Types}{Models}
diff --git a/src/qml/jsapi/qjsvalue.cpp b/src/qml/jsapi/qjsvalue.cpp
index d7a1cef3ba..6a0cf0cf6d 100644
--- a/src/qml/jsapi/qjsvalue.cpp
+++ b/src/qml/jsapi/qjsvalue.cpp
@@ -1089,8 +1089,6 @@ QDateTime QJSValue::toDateTime() const
/*!
Returns true if this QJSValue is an object of the Date class;
otherwise returns false.
-
- \sa QJSEngine::newDate()
*/
bool QJSValue::isDate() const
{
diff --git a/src/qml/qml/qqmlfileselector.cpp b/src/qml/qml/qqmlfileselector.cpp
index 6ddc2eb2ff..a18b8327b1 100644
--- a/src/qml/qml/qqmlfileselector.cpp
+++ b/src/qml/qml/qqmlfileselector.cpp
@@ -92,7 +92,7 @@ Q_GLOBAL_STATIC(interceptorSelectorMap, interceptorInstances);
trigger this feature unless you have directories with such names inside your project.
If a new QQmlFileSelector is set on the engine, the old one will be replaced. Use
- \l QQmlFileSelector::get to query or use the existing instance.
+ \l QQmlFileSelector::get() to query or use the existing instance.
*/
/*!
diff --git a/src/qml/qml/v8/qqmlbuiltinfunctions.cpp b/src/qml/qml/v8/qqmlbuiltinfunctions.cpp
index 41d5de0862..0409b92e89 100644
--- a/src/qml/qml/v8/qqmlbuiltinfunctions.cpp
+++ b/src/qml/qml/v8/qqmlbuiltinfunctions.cpp
@@ -1157,7 +1157,7 @@ ReturnedValue QtObject::method_createComponent(CallContext *ctx)
is not present, or is not a valid ISO 3166 code, the most
appropriate country is chosen for the specified language.
- \sa QtQuick::Locale
+ \sa Locale
*/
ReturnedValue QtObject::method_locale(CallContext *ctx)
{
@@ -1801,7 +1801,7 @@ ReturnedValue GlobalExtensions::method_qsTrNoOp(CallContext *ctx)
Creating binary translation (QM) files suitable for use with this function requires passing
the \c -idbased option to the \c lrelease tool.
- \sa QT_TRID_NOOP, {Internationalization and Localization with Qt Quick}
+ \sa QT_TRID_NOOP(), {Internationalization and Localization with Qt Quick}
*/
ReturnedValue GlobalExtensions::method_qsTrId(CallContext *ctx)
{
diff --git a/src/quick/doc/qtquick.qdocconf b/src/quick/doc/qtquick.qdocconf
index 22880c4086..846da64ea4 100644
--- a/src/quick/doc/qtquick.qdocconf
+++ b/src/quick/doc/qtquick.qdocconf
@@ -34,7 +34,7 @@ qhp.QtQuick.subprojects.examples.selectors = fake:example
tagfile = ../../../doc/qtquick/qtquick.tags
-depends += qtcore qtxmlpatterns qtqml qtgui qtlinguist qtquickcontrols qtquicklayouts qtdoc qtquickdialogs
+depends += qtcore qtxmlpatterns qtqml qtgui qtlinguist qtquickcontrols qtquicklayouts qtdoc qtquickdialogs qtsensors qtwidgets
headerdirs += ..
diff --git a/src/quick/doc/src/advtutorial.qdoc b/src/quick/doc/src/advtutorial.qdoc
index be8b397a8e..aa44ef8a85 100644
--- a/src/quick/doc/src/advtutorial.qdoc
+++ b/src/quick/doc/src/advtutorial.qdoc
@@ -90,7 +90,7 @@ is the \l SystemPalette item. This provides access to the Qt system palette
and is used to give the button a more native look-and-feel.
Notice the anchors for the \c Item, \c Button and \c Text types are set using
-\l {qdeclarativeintroduction.html#dot-properties}{group notation} for readability.
+group (dot) notation for readability.
\section2 Adding \c Button and \c Block components
@@ -360,7 +360,7 @@ Finally, we'll add a cool-looking particle effect to the blocks when they are de
\snippet tutorials/samegame/samegame4/content/BoomBlock.qml 3
-To fully understand this you should read the \l Particles documentation, but it's important to note that \c emitRate is set
+To fully understand this you should read \l {Using the Qt Quick Particle System}, but it's important to note that \c emitRate is set
to zero so that particles are not emitted normally.
Also, we extend the \c dying State, which creates a burst of particles by calling the \c burst() method on the particles type. The code for the states now look
like this:
@@ -419,7 +419,7 @@ Here is the \c saveHighScore() function in \c samegame.js:
First we call \c sendHighScore() (explained in the section below) if it is possible to send the high scores to an online database.
-Then, we use the \l{QtQuick.LocalStorage 2}{Local Storage API} to maintain a persistent SQL database unique to this application. We create an offline storage database for the high scores using \c openDatabaseSync() and prepare the data and SQL query that we want to use to save it. The offline storage API uses SQL queries for data manipulation and retrieval, and in the \c db.transaction() call we use three SQL queries to initialize the database (if necessary), and then add to and retrieve high scores. To use the returned data, we turn it into a string with one line per row returned, and show a dialog containing that string.
+Then, we use the \l{QtQuick.LocalStorage}{Local Storage API} to maintain a persistent SQL database unique to this application. We create an offline storage database for the high scores using \c openDatabaseSync() and prepare the data and SQL query that we want to use to save it. The offline storage API uses SQL queries for data manipulation and retrieval, and in the \c db.transaction() call we use three SQL queries to initialize the database (if necessary), and then add to and retrieve high scores. To use the returned data, we turn it into a string with one line per row returned, and show a dialog containing that string.
This is one way of storing and displaying high scores locally, but certainly not the only way. A more complex alternative would be to create a high score dialog component, and pass it the results for processing and display (instead of reusing the \c Dialog). This would allow a more themeable dialog that could better present the high scores. If your QML is the UI for a C++ application, you could also have passed the score to a C++ function to store it locally in a variety of ways, including a simple format without SQL or in another SQL database.
@@ -451,9 +451,9 @@ By following this tutorial you've seen how you can write a fully functional appl
\list
\li Build your application with \l {Qt Quick QML Types}{QML types}
-\li Add application logic \l{Using JavaScript Expressions in QML}{with JavaScript code}
+\li Add application logic \l{JavaScript Expressions in QML Documents}{with JavaScript code}
\li Add animations with \l {Behavior}{Behaviors} and \l{Qt Quick States}{states}
-\li Store persistent application data using, for example, \l{QtQuick.LocalStorage 2}{QtQuick.LocalStorage} or \l XMLHttpRequest
+\li Store persistent application data using, for example, \l QtQuick.LocalStorage or \l XMLHttpRequest
\endlist
There is so much more to learn about QML that we haven't been able to cover in this tutorial. Check out all the
diff --git a/src/quick/doc/src/concepts/effects/particles.qdoc b/src/quick/doc/src/concepts/effects/particles.qdoc
index ec49c6df43..c3262b7082 100644
--- a/src/quick/doc/src/concepts/effects/particles.qdoc
+++ b/src/quick/doc/src/concepts/effects/particles.qdoc
@@ -46,7 +46,7 @@
\page qtquick-effects-particles.html
\title Using the Qt Quick Particle System
- Documentation for all Particle System types can be found on the \l{QtQuick.Particles 2}{QtQuick.Particles} module page.
+ Documentation for all Particle System types can be found on the \l QtQuick.Particles module page.
Note that to use types from the particles module, you will need to import the types with the following line:
\code
diff --git a/src/quick/doc/src/concepts/input/focus.qdoc b/src/quick/doc/src/concepts/input/focus.qdoc
index 827f6d85c8..065651c826 100644
--- a/src/quick/doc/src/concepts/input/focus.qdoc
+++ b/src/quick/doc/src/concepts/input/focus.qdoc
@@ -168,7 +168,7 @@ When a QML \l Item explicitly relinquishes focus (by setting its
system does not automatically select another type to receive focus. That is,
it is possible for there to be no currently active focus.
-See the \l{declarative/keyinteraction/focus}{Keyboard Focus example} for a
+See \l{Qt Quick Examples - Key Interaction} for a
demonstration of moving keyboard focus between multiple areas using FocusScope
types.
diff --git a/src/quick/doc/src/concepts/modelviewsdata/cppmodels.qdoc b/src/quick/doc/src/concepts/modelviewsdata/cppmodels.qdoc
index 28bbbf1cca..abef6b765b 100644
--- a/src/quick/doc/src/concepts/modelviewsdata/cppmodels.qdoc
+++ b/src/quick/doc/src/concepts/modelviewsdata/cppmodels.qdoc
@@ -174,8 +174,8 @@ with list models of QAbstractItemModel type:
The above examples use QQmlContext::setContextProperty() to set
model values directly in QML components. An alternative to this is to
register the C++ model class as a QML type (either
-\l{qtqml-registercpptypes.html}{directly} from a C++ entry-point, or within
-the initialization function of a \l{qtqml-modules-cppplugins.html}
+\l{Defining QML Types from C++}{directly} from a C++ entry-point, or within
+the initialization function of a \l{Creating C++ Plugins for QML}
{QML C++ plugin}, as shown below). This would allow the model classes to be
created directly as types within QML:
@@ -215,7 +215,7 @@ ListView {
\endtable
-See \l {Tutorial: Extending QML with C++} for details on writing QML C++
+See \l {Writing QML Extensions with C++} for details on writing QML C++
plugins.
diff --git a/src/quick/doc/src/concepts/modelviewsdata/modelview.qdoc b/src/quick/doc/src/concepts/modelviewsdata/modelview.qdoc
index b5dd961ea9..1a539f56ed 100644
--- a/src/quick/doc/src/concepts/modelviewsdata/modelview.qdoc
+++ b/src/quick/doc/src/concepts/modelviewsdata/modelview.qdoc
@@ -193,8 +193,7 @@ To visualize data, bind the view's \c model property to a model and the
and \l{qtqml-typesystem-topic.html#qml-object-types}
{creating QML types} articles.
- The use of positioner items to arrange items from a model is covered in
- \l{Generating Items with Repeaters}.
+ Positioning of items from a model can be achieved using a \l{Repeater}.
\section2 ListModel
diff --git a/src/quick/doc/src/concepts/modelviewsdata/topic.qdoc b/src/quick/doc/src/concepts/modelviewsdata/topic.qdoc
index 6939c3131f..21c81f47e5 100644
--- a/src/quick/doc/src/concepts/modelviewsdata/topic.qdoc
+++ b/src/quick/doc/src/concepts/modelviewsdata/topic.qdoc
@@ -49,7 +49,7 @@ see the page titled \l{qtquick-modelviewsdata-modelview.html}
Databases are commonly used to store information in applications. Qt Quick
provides simplified access to relational databases via the
-\l{QtQuick.LocalStorage 2}{Qt Quick local storage module}.
+\l QtQuick.LocalStorage module.
*/
diff --git a/src/quick/doc/src/concepts/positioning/righttoleft.qdoc b/src/quick/doc/src/concepts/positioning/righttoleft.qdoc
index ad8b2f3b63..5d173efedb 100644
--- a/src/quick/doc/src/concepts/positioning/righttoleft.qdoc
+++ b/src/quick/doc/src/concepts/positioning/righttoleft.qdoc
@@ -89,7 +89,7 @@ views that takes the mirroring into account can be read from the \c effectiveLay
The attached property \l LayoutMirroring is provided as a convenience for easily implementing right-to-left
support for existing left-to-right Qt Quick applications. It mirrors the behavior of \l {anchor-layout}
-{Item anchors}, the layout direction of \l{Composing User Interfaces with QML#Positioners}{positioners} and
+{Item anchors}, the layout direction of \l{Item Positioners}{positioners} and
\l{qtquick-modelviewsdata-modelview.html}{model views}, and the explicit text alignment of QML text types.
You can enable layout mirroring for a particular \l Item:
diff --git a/src/quick/doc/src/concepts/positioning/topic.qdoc b/src/quick/doc/src/concepts/positioning/topic.qdoc
index bae6a7f71b..51cb07c51d 100644
--- a/src/quick/doc/src/concepts/positioning/topic.qdoc
+++ b/src/quick/doc/src/concepts/positioning/topic.qdoc
@@ -51,7 +51,7 @@ the position manually than to use the more dynamic positioning methods
documented in proceeding sections.
In Qt Quick, every visual object is positioned within the
-\l{qtquick-visual-coordinates.html}{coordinate system}
+\l{Concepts - Visual Coordinates in Qt Quick}{coordinate system}
provided by the Qt Quick visual canvas. As described in that document, the
x and y coordinates of a visual object are relative to those of its visual
parent, with the top-left corner having the coordinate (0, 0).
diff --git a/src/quick/doc/src/concepts/statesanimations/animations.qdoc b/src/quick/doc/src/concepts/statesanimations/animations.qdoc
index 07f1048bf2..e4e208863b 100644
--- a/src/quick/doc/src/concepts/statesanimations/animations.qdoc
+++ b/src/quick/doc/src/concepts/statesanimations/animations.qdoc
@@ -72,7 +72,7 @@ animations provide timing controls and allows different interpolations through
\snippet qml/animation.qml property animation
-Specialized \l{qml-property-animation-types}{property animation types}
+Specialized property animation types
have more efficient implementations than the \l{PropertyAnimation} type. They
are for setting animations to different QML types such as \c int, \c color, and
rotations. Similarly, the \l{ParentAnimation} can animate parent changes.
@@ -145,8 +145,7 @@ values.
abrupt property changes; animations smooth transitions to produce visually
appealing state changes.
-The \l{Transition} type can contain
-\l{qml-animation-types}{animation types} to interpolate property changes
+The \l{Transition} type can contain animation types to interpolate property changes
caused by state changes. To assign the transition to an object, bind it to the
\c transitions property.
diff --git a/src/quick/doc/src/examples.qdoc b/src/quick/doc/src/examples.qdoc
index ddca973496..4cb1d8ddd4 100644
--- a/src/quick/doc/src/examples.qdoc
+++ b/src/quick/doc/src/examples.qdoc
@@ -44,8 +44,8 @@ To run the sample applications, open them in Qt Creator or use the included
\annotatedlist{qtquickdemos}
-Some of these code samples below have a corresponding \l{qtquick-tutorials}{tutorial}.
-The Qt Quick features are covered in the \l {qtquick-overviews}{main page}.
+Some of these code samples below have a corresponding tutorial.
+The Qt Quick features are covered in the \l {Qt Quick}{main page}.
This set of code samples are part of the collection of \l{Qt Examples}.
\annotatedlist{qtquickexamples}
diff --git a/src/quick/doc/src/qmltypereference.qdoc b/src/quick/doc/src/qmltypereference.qdoc
index 0155ee4e2d..dda06d31e1 100644
--- a/src/quick/doc/src/qmltypereference.qdoc
+++ b/src/quick/doc/src/qmltypereference.qdoc
@@ -85,7 +85,7 @@ In addition, the \c QtQuick module provides the following basic types:
\section1 Object Types
All of the object types provided by \c QtQuick are based on the \l{Item} type,
-which itself derives from \l{QtQml::QtObject}{QtObject}. \l{qtqml-typereference-topic.html#object-types}
+which itself derives from \l{QtQml::QtObject}{QtObject}. \l{Qt QML QML Types#Object Types}
{QML object types} provided by the Qt QML module
(such as \l{QtQml::QtObject}{QtObject} and \l{QtQml::Component}{Component}) are also available when
you import \c QtQuick.
@@ -269,7 +269,7 @@ Views
\list
\li \l {ListView} - Provides a list visualization of a model
\li \l {GridView} - Provides a grid visualization of a model
-\li \l {PathView} - Visualizes a model's contents along a path. See \l {Path Definition}{Path Elements} for more information.
+\li \l {PathView} - Visualizes a model's contents along a path. See \l Path for more information.
\li \l {Package} - Collection that enables sharing of items within different views
\endlist
diff --git a/src/quick/doc/src/tutorial.qdoc b/src/quick/doc/src/tutorial.qdoc
index a4428c5818..e0c05b16a8 100644
--- a/src/quick/doc/src/tutorial.qdoc
+++ b/src/quick/doc/src/tutorial.qdoc
@@ -96,7 +96,7 @@ The \c y property is used to position the text vertically at 30 pixels from the
The \c anchors.horizontalCenter property refers to the horizontal center of an type.
In this case, we specify that our text type should be horizontally centered in the \e page element (see \l{anchor-layout}{Anchor-Based Layout}).
-The \c font.pointSize and \c font.bold properties are related to fonts and use the \l{dot properties}{dot notation}.
+The \c font.pointSize and \c font.bold properties are related to fonts and use the dot notation.
\section2 Viewing the example
@@ -124,7 +124,7 @@ Our color picker is made of six cells with different colors.
To avoid writing the same code multiple times for each cell, we create a new \c Cell component.
A component provides a way of defining a new type that we can re-use in other QML files.
A QML component is like a black-box and interacts with the outside world through properties, signals and functions and is generally
-defined in its own QML file. (For more details, see \l {Defining New Components}).
+defined in its own QML file. (For more details, see the \l Component documentation).
The component's filename must always start with a capital letter.
Here is the QML code for \c Cell.qml:
@@ -145,7 +145,7 @@ An \l Item is the most basic visual type in QML and is often used as a container
We declare a \c cellColor property. This property is accessible from \e outside our component, this allows us
to instantiate the cells with different colors.
This property is just an alias to an existing property - the color of the rectangle that compose the cell
-(see \l{Property Binding in QML}).
+(see \l{Property Binding}).
\snippet tutorials/helloworld/Cell.qml 5
diff --git a/src/quick/doc/src/whatsnew.qdoc b/src/quick/doc/src/whatsnew.qdoc
index 26d88699bc..16df2a6d0d 100644
--- a/src/quick/doc/src/whatsnew.qdoc
+++ b/src/quick/doc/src/whatsnew.qdoc
@@ -431,24 +431,23 @@ to \l {Qt Quick}{Qt Quick 2}; the other functions are all new in \l {Qt Quick}{Q
\section2 QtQuick.Particles
This new module provides particle system support for creating a variety of 2D particle systems. See
-the \l{QtQuick.Particles 2}{QtQuick.Particles} documentation for comprehensive details.
+the \l QtQuick.Particles documentation for comprehensive details.
This obsoletes the experimental \c Qt.labs.particles module.
\section2 QtQuick.Window
This new module contains the \l Window type for creating a basic window and the \l Screen type for
-accessing a screen's resolution and other details. See the \l{QtQuick.Window 2}{QtQuick.Window}
+accessing a screen's resolution and other details. See the \l QtQuick.Window
documentation for comprehensive details.
\section2 QtQuick.XmlListModel
This new module contains XmlListModel and associated types, which were previously in the \c QtQuick
-module. See the \l{QtQuick.XmlListModel 2}{QtQuick.XmlListModel} documentation for details.
+module. See the \l QtQuick.XmlListModel documentation for details.
\section2 QtQuick.LocalStorage
This new module provides access to the SQL Local Storage API that was previously accessible from the
-\l {QML Global Object}. See the \l{QtQuick.LocalStorage 2}{QtQuick.LocalStorage} documentation for details.
-
+\l {QML Global Object}. See the \l QtQuick.LocalStorage documentation for details.
*/
diff --git a/src/quick/items/context2d/qquickcanvasitem.cpp b/src/quick/items/context2d/qquickcanvasitem.cpp
index 19a161a605..b3a2c9f46a 100644
--- a/src/quick/items/context2d/qquickcanvasitem.cpp
+++ b/src/quick/items/context2d/qquickcanvasitem.cpp
@@ -845,7 +845,7 @@ void QQuickCanvasItem::requestPaint()
canvas renderer will redraw it. This will trigger the onPaint signal
handler function.
- \sa paint, requestPaint()
+ \sa onPaint, requestPaint()
*/
void QQuickCanvasItem::markDirty(const QRectF& rect)
diff --git a/src/quick/items/context2d/qquickcontext2d.cpp b/src/quick/items/context2d/qquickcontext2d.cpp
index b6eb2db33d..b6d4f1073c 100644
--- a/src/quick/items/context2d/qquickcontext2d.cpp
+++ b/src/quick/items/context2d/qquickcontext2d.cpp
@@ -1103,7 +1103,8 @@ QV4::ReturnedValue QQuickJSContext2DPrototype::method_scale(QV4::CallContext *ct
rotating, and translating transformations in a single step.
Each point on the canvas is multiplied by the matrix before anything is
- drawn. The \l{HTML5 Canvas API} defines the transformation matrix as:
+ drawn. The \l{http://www.w3.org/TR/2dcontext/#transformations}{HTML Canvas 2D Context specification}
+ defines the transformation matrix as:
\image qml-item-canvas-math.png
where:
diff --git a/src/quick/items/qquickdrag.cpp b/src/quick/items/qquickdrag.cpp
index ed9d1838b8..605c485f6b 100644
--- a/src/quick/items/qquickdrag.cpp
+++ b/src/quick/items/qquickdrag.cpp
@@ -522,7 +522,7 @@ void QQuickDragAttached::setProposedAction(Qt::DropAction action)
\li Drag.Internal (default) - start backwards compatible drags automatically
\endlist
- When using \l Drag.Automatic you should also define \l mimeData and bind the
+ When using \c Drag.Automatic you should also define \l mimeData and bind the
\active property to the active property of \l MouseArea.drag.
*/
diff --git a/src/quick/items/qquickdroparea.cpp b/src/quick/items/qquickdroparea.cpp
index 01166ab121..8d58ffbfae 100644
--- a/src/quick/items/qquickdroparea.cpp
+++ b/src/quick/items/qquickdroparea.cpp
@@ -107,7 +107,7 @@ QQuickDropAreaPrivate::~QQuickDropAreaPrivate()
The \l keys property can be used to filter drag events which don't include
a matching key.
- The \l source property is communicated to the source of a drag event as
+ The \l drag.source property is communicated to the source of a drag event as
the recipient of a drop on the drag target.
The \l delegate property provides a means to specify a component to be
@@ -337,7 +337,7 @@ void QQuickDropArea::dropEvent(QDropEvent *event)
The position of the drag event can be obtained from the \l x and \l y
properties, and the \l keys property identifies the drag keys of the event
- \l source.
+ \l {drag.source}{source}.
The existence of specific drag types can be determined using the \l hasColor,
\l hasHtml, \l hasText, and \l hasUrls properties.
@@ -378,7 +378,7 @@ void QQuickDropArea::dropEvent(QDropEvent *event)
/*!
\qmlproperty enumeration QtQuick::DragEvent::action
- This property holds the action that the \l source is to perform on an accepted drop.
+ This property holds the action that the \l {drag.source}{source} is to perform on an accepted drop.
The drop action may be one of:
diff --git a/src/quick/items/qquickfocusscope.cpp b/src/quick/items/qquickfocusscope.cpp
index f13a8ad3ca..bd8e58af35 100644
--- a/src/quick/items/qquickfocusscope.cpp
+++ b/src/quick/items/qquickfocusscope.cpp
@@ -56,7 +56,7 @@ QT_BEGIN_NAMESPACE
components. All the details are covered in the
\l {Keyboard Focus in Qt Quick}{keyboard focus documentation}.
- \sa {declarative/keyinteraction/focus}{Keyboard focus example}
+ \sa {Qt Quick Examples - Key Interaction}
*/
QQuickFocusScope::QQuickFocusScope(QQuickItem *parent)
: QQuickItem(parent)
diff --git a/src/quick/items/qquickgridview.cpp b/src/quick/items/qquickgridview.cpp
index c9e6d4d7e2..1107425575 100644
--- a/src/quick/items/qquickgridview.cpp
+++ b/src/quick/items/qquickgridview.cpp
@@ -1759,7 +1759,7 @@ void QQuickGridView::setSnapMode(SnapMode mode)
populated, or when the view's \l model changes. (In those cases, the \l populate transition is
applied instead.) Additionally, this transition should \e not animate the height of the new item;
doing so will cause any items beneath the new item to be laid out at the wrong position. Instead,
- the height can be animated within a \l {ListView::onAdd()}{ListView.onAdd} in the delegate.
+ the height can be animated within a \l {ListView::onAdd}{ListView.onAdd} in the delegate.
\sa addDisplaced, populate, ViewTransition
*/
diff --git a/src/quick/items/qquickitem.cpp b/src/quick/items/qquickitem.cpp
index 9ac660d2ac..ecb08c5a7e 100644
--- a/src/quick/items/qquickitem.cpp
+++ b/src/quick/items/qquickitem.cpp
@@ -1819,7 +1819,7 @@ void QQuickItemPrivate::updateSubFocusItem(QQuickItem *scope, bool focus)
\value Bottom The center point of the bottom of the item.
\value BottomRight The bottom-right corner of the item.
- \sa transformOrigin
+ \sa transformOrigin(), setTransformOrigin()
*/
/*!
@@ -2425,7 +2425,7 @@ void QQuickItem::stackAfter(const QQuickItem *sibling)
Returns the window in which this item is rendered.
The item does not have a window until it has been assigned into a scene. The
- \l windowChanged signal provides a notification both when the item is entered
+ \l windowChanged() signal provides a notification both when the item is entered
into a scene and when it is removed from a scene.
*/
QQuickWindow *QQuickItem::window() const
@@ -4575,7 +4575,7 @@ void QQuickItemPrivate::deliverDragEvent(QEvent *e)
QQuickItem::itemChange(change, value);
\endcode
typically at the end of your implementation, to ensure the
- \l windowChanged signal will be emitted.
+ \l windowChanged() signal will be emitted.
*/
void QQuickItem::itemChange(ItemChange change, const ItemChangeData &value)
{
diff --git a/src/quick/items/qquickitemanimation.cpp b/src/quick/items/qquickitemanimation.cpp
index 1d1ea97925..279393b3ba 100644
--- a/src/quick/items/qquickitemanimation.cpp
+++ b/src/quick/items/qquickitemanimation.cpp
@@ -429,7 +429,7 @@ QAbstractAnimationJob* QQuickParentAnimation::transition(QQuickStateActions &act
When an AnchorAnimation is used in a \l Transition, it will
animate any AnchorChanges that have occurred during the state change.
This can be overridden by setting a specific target item using the
- \l target property.
+ \l {AnchorChanges::target}{AnchorChanges.target} property.
\note AnchorAnimation can only be used in a \l Transition and in
conjunction with an AnchorChange. It cannot be used in behaviors and
diff --git a/src/quick/items/qquickitemviewtransition.cpp b/src/quick/items/qquickitemviewtransition.cpp
index 0940fe0d22..4c09b78329 100644
--- a/src/quick/items/qquickitemviewtransition.cpp
+++ b/src/quick/items/qquickitemviewtransition.cpp
@@ -901,7 +901,7 @@ QQuickViewTransitionAttached::QQuickViewTransitionAttached(QObject *parent)
\note The targetIndexes list only contains the indexes of items that are actually
in view, or will be in the view once the relevant operation completes.
- \sa QtQuick::ViewTransition::targetIndexes
+ \sa QtQuick::ViewTransition::targetItems
*/
/*!
diff --git a/src/quick/items/qquicklistview.cpp b/src/quick/items/qquicklistview.cpp
index 77cdbceb8f..9f2f90a2a7 100644
--- a/src/quick/items/qquicklistview.cpp
+++ b/src/quick/items/qquicklistview.cpp
@@ -2460,7 +2460,7 @@ void QQuickListView::setSnapMode(SnapMode mode)
populated, or when the view's \l model changes. (In those cases, the \l populate transition is
applied instead.) Additionally, this transition should \e not animate the height of the new item;
doing so will cause any items beneath the new item to be laid out at the wrong position. Instead,
- the height can be animated within a \l {ListView::onAdd()}{ListView.onAdd} in the delegate.
+ the height can be animated within \l onAdd in the delegate.
\sa addDisplaced, populate, ViewTransition
*/
diff --git a/src/quick/items/qquickloader.cpp b/src/quick/items/qquickloader.cpp
index b83c21428c..debe4b7497 100644
--- a/src/quick/items/qquickloader.cpp
+++ b/src/quick/items/qquickloader.cpp
@@ -271,7 +271,7 @@ qreal QQuickLoaderPrivate::getImplicitHeight() const
In some cases you may wish to use a Loader within a view delegate to improve delegate
loading performance. This works well in most cases, but there is one important issue to
- be aware of related to the \l{QtQuick::Component#creation-context}{creation context} of a Component.
+ be aware of related to the \l{QtQml::Component#Creation Context}{creation context} of a Component.
In the following example, the \c index context property inserted by the ListView into \c delegateComponent's
context will be inaccessible to Text, as the Loader will use the creation context of \c myComponent as the parent
diff --git a/src/quick/items/qquickscreen.cpp b/src/quick/items/qquickscreen.cpp
index 48c0f8e084..410f18e767 100644
--- a/src/quick/items/qquickscreen.cpp
+++ b/src/quick/items/qquickscreen.cpp
@@ -177,8 +177,8 @@ QT_BEGIN_NAMESPACE
automatically rotates all content which is displayed, depending on how you
hold it. But if orientation changes while primaryOrientation does NOT
change, then probably you are using a device which does not rotate its own
- display. In that case you may need to use \l Item.rotation or
- \l Item.transform to rotate your content.
+ display. In that case you may need to use \l {Item::rotation}{Item.rotation} or
+ \l {Item::transform}{Item.transform} to rotate your content.
*/
/*!
\qmlattachedmethod int Screen::angleBetween(Qt::ScreenOrientation a, Qt::ScreenOrientation b)
diff --git a/src/quick/items/qquickwindow.cpp b/src/quick/items/qquickwindow.cpp
index f355afcea5..d286ccff0c 100644
--- a/src/quick/items/qquickwindow.cpp
+++ b/src/quick/items/qquickwindow.cpp
@@ -3299,7 +3299,7 @@ void QQuickWindow::resetOpenGLState()
additional content like popups, dialogs, status bars, or similar
in relation to the window.
- The recommended orientation is \l Screen.orientation, but
+ The recommended orientation is \l {Screen::orientation}{Screen.orientation}, but
an application doesn't have to support all possible orientations,
and thus can opt to ignore the current screen orientation.
diff --git a/src/quick/util/qquickanimation.cpp b/src/quick/util/qquickanimation.cpp
index ad9cf06d5c..36316e27c0 100644
--- a/src/quick/util/qquickanimation.cpp
+++ b/src/quick/util/qquickanimation.cpp
@@ -1461,7 +1461,7 @@ void QQuickVector3dAnimation::setTo(QVector3D t)
\snippet qml/rotationanimation.qml 0
- Notice the RotationAnimation did not need to set a \l target
+ Notice the RotationAnimation did not need to set a \c target
value. As a convenience, when used in a transition, RotationAnimation will rotate all
properties named "rotation" or "angle". You can override this by providing
your own properties via \l {PropertyAnimation::properties}{properties} or