Doc: Fix link issues
Change-Id: I738b9da5335afb048d2eda2edf2be5095a91d7e5 Reviewed-by: Topi Reiniö <topi.reinio@qt.io>
This commit is contained in:
parent
c57681bc37
commit
0e33ba5116
|
@ -33,7 +33,7 @@ qhp.QtQml.subprojects.qmltypes.sortPages = true
|
|||
|
||||
tagfile = ../../../doc/qtqml/qtqml.tags
|
||||
|
||||
depends += qtcore qtgui qtquick qtdoc qtlinguist qmake qtscript qtwidgets
|
||||
depends += qtcore qtgui qtquick qtdoc qtlinguist qmake qtscript qtwidgets qtxmlpatterns qtquickcontrols
|
||||
|
||||
headerdirs += .. \
|
||||
../../imports/models
|
||||
|
|
|
@ -52,8 +52,8 @@ object, the object definition should declare a signal handler named
|
|||
letter capitalized. The signal handler should contain the JavaScript code to be
|
||||
executed when the signal handler is invoked.
|
||||
|
||||
For example, the \l [QtQuick.Controls2]{Button} type from the
|
||||
\l{Qt Quick Controls 2}{Qt Quick Controls} module has a \c clicked signal, which
|
||||
For example, the \l [QtQuickControls]{Button} type from the
|
||||
\l{Qt Quick Controls} module has a \c clicked signal, which
|
||||
is emitted whenever the button is clicked. In this case, the signal handler for
|
||||
receiving this signal should be \c onClicked. In the example below, whenever
|
||||
the button is clicked, the \c onClicked handler is invoked, applying a random
|
||||
|
|
|
@ -350,7 +350,7 @@ void QQmlDelegateModel::componentComplete()
|
|||
{QAbstractItemModel} subclass or a simple list.
|
||||
|
||||
Models can also be created directly in QML, using a \l{ListModel} or
|
||||
\l{XmlListModel}.
|
||||
\l{QtQuick.XmlListModel::XmlListModel}{XmlListModel}.
|
||||
|
||||
\sa {qml-data-models}{Data Models}
|
||||
*/
|
||||
|
|
|
@ -37,7 +37,7 @@ qhp.QtQuick.subprojects.examples.selectors = fake:example
|
|||
|
||||
tagfile = ../../../doc/qtquick/qtquick.tags
|
||||
|
||||
depends += qtcore qtqml qtqmltest qtgui qtlinguist qtquickcontrols qtquickcontrols2 qtdoc qtquickdialogs qtsensors qtwidgets qmake qtmultimedia qtgraphicaleffects qtsql
|
||||
depends += qtcore qtqml qtqmltest qtgui qtlinguist qtquickcontrols1 qtquickcontrols qtdoc qtquickdialogs qtsensors qtwidgets qmake qtmultimedia qtgraphicaleffects qtsql qtxmlpatterns
|
||||
|
||||
headerdirs += ..\
|
||||
../../quickwidgets
|
||||
|
|
|
@ -331,9 +331,7 @@ signal after saving the changes.
|
|||
|
||||
Unlike the C++ item views such as QListView or QTableView, the \c setData()
|
||||
method must be explicitly invoked from QML delegates whenever appropriate. This is done
|
||||
by simply assigning a new value to the corresponding model property. For example,
|
||||
on the \l[QML]{TextField::}{editingFinished}() or \l[QML]{TextField::}{accepted}()
|
||||
signal of \l[QtQuickControls]{TextField}.
|
||||
by simply assigning a new value to the corresponding model property.
|
||||
|
||||
\qml
|
||||
ListView {
|
||||
|
|
|
@ -226,7 +226,7 @@ To visualize data, bind the view's \c model property to a model and the
|
|||
\section2 XML Model
|
||||
|
||||
XmlListModel allows construction of a model from an XML data source. The roles
|
||||
are specified via the \l XmlRole type. The type needs to be imported.
|
||||
are specified via the \l [QML]{XmlRole} type. The type needs to be imported.
|
||||
|
||||
\code
|
||||
import QtQuick.XmlListModel 2.0
|
||||
|
|
|
@ -77,9 +77,7 @@ steps such as use cases and introductory material. For more information about Qt
|
|||
\b{Development Environment}
|
||||
\list
|
||||
\li \l{Qt Creator: Creating Qt Quick Projects}{Creating Qt Quick Projects}
|
||||
\li \l{Qt Creator: Using Qt Quick Designer}{Using Qt Quick Designer}
|
||||
\li \l{Qt Creator: Creating Components}{Creating Components}
|
||||
\li \l{Qt Creator: Creating Screens}{Creating Screens}
|
||||
\li \l{Qt Creator: Exporting Designs from Graphics Software}{Exporting Designs from Graphics Software}
|
||||
\li \l{Qt Creator: Using QML Modules with Plugins}{Using QML Modules with Plugins}
|
||||
\endlist
|
||||
|
|
|
@ -108,6 +108,5 @@ integrating 3rd party tools such as QmlLive and GammaRay.
|
|||
\section2 Related Information
|
||||
\list
|
||||
\li \l{Qt Creator Manual}
|
||||
\li \l{Qt Creator: Integrating 3rd Party Tools}
|
||||
\endlist
|
||||
*/
|
||||
|
|
|
@ -49,7 +49,7 @@ information about the concepts which are central to \c QtQuick.
|
|||
Qt Quick includes several submodules which contain additional types.
|
||||
|
||||
\list
|
||||
\li \l{Qt Quick XmlListModel QML Types}{XML List Model} - contains types
|
||||
\li \l{Qt Quick XmlListModel QML Types}{Xml List Model} - contains types
|
||||
for creating models from XML data
|
||||
\li \l{Qt Quick Local Storage QML Types}{Local Storage} - a submodule
|
||||
containing a JavaScript interface for an SQLite database
|
||||
|
|
|
@ -82,7 +82,7 @@ Q_LOGGING_CATEGORY(lcDragHandler, "qt.quick.handler.drag")
|
|||
and thus can be used to adjust some other feature independently of the
|
||||
usual pinch behavior: for example adjust a tilt transformation, or adjust
|
||||
some other numeric value, if the \c target is set to null. But if the
|
||||
\l target is an Item, \l centroid is the point at which the drag begins and
|
||||
\c target is an Item, \c centroid is the point at which the drag begins and
|
||||
to which the \c target will be moved (subject to constraints).
|
||||
|
||||
At this time, drag-and-drop is not yet supported.
|
||||
|
|
|
@ -282,8 +282,6 @@ void QQuickHandlerPoint::reset(const QVector<QQuickHandlerPoint> &points)
|
|||
|
||||
This property holds the keyboard modifiers that were pressed at the time
|
||||
the event occurred.
|
||||
|
||||
\sa MouseArea::modifiers
|
||||
*/
|
||||
|
||||
/*!
|
||||
|
|
|
@ -59,7 +59,7 @@ QT_BEGIN_NAMESPACE
|
|||
occurs within the bounds of the \l {PointerHandler::parent}, and
|
||||
no sibling PointHandler within the same \l {PointerHandler::parent}
|
||||
has yet acquired a passive grab on that point, and if the other
|
||||
constraints such as \l {SinglePointHandler::acceptedButtons},
|
||||
constraints such as \l[QML]{SinglePointHandler::acceptedButtons},
|
||||
\l {PointerDeviceHandler::acceptedDevices} etc. are satisfied, it's
|
||||
eligible, and the PointHandler then acquires a passive grab. In
|
||||
this way, the \l {PointerHandler::parent} acts like an exclusive
|
||||
|
|
Loading…
Reference in New Issue