summaryrefslogtreecommitdiffstats
path: root/doc/src/declarative/extending.qdoc
diff options
context:
space:
mode:
authorJerome Pasion <jerome.pasion@nokia.com>2010-12-13 15:03:20 (GMT)
committerJerome Pasion <jerome.pasion@nokia.com>2010-12-13 15:03:20 (GMT)
commit177d6865c65719c7c6ffdb6c8fd1e7c3e049e1e1 (patch)
treed5eeceb7e6f9b4d2f99bbb63eba8bac46f15601d /doc/src/declarative/extending.qdoc
parentad3783ecd1308d357eb0451fe5b4fc24b49ed15a (diff)
downloadQt-177d6865c65719c7c6ffdb6c8fd1e7c3e049e1e1.zip
Qt-177d6865c65719c7c6ffdb6c8fd1e7c3e049e1e1.tar.gz
Qt-177d6865c65719c7c6ffdb6c8fd1e7c3e049e1e1.tar.bz2
Added \ingroup for the overview pages and \group page.
Diffstat (limited to 'doc/src/declarative/extending.qdoc')
-rw-r--r--doc/src/declarative/extending.qdoc25
1 files changed, 14 insertions, 11 deletions
diff --git a/doc/src/declarative/extending.qdoc b/doc/src/declarative/extending.qdoc
index e23ca91..e61447a 100644
--- a/doc/src/declarative/extending.qdoc
+++ b/doc/src/declarative/extending.qdoc
@@ -27,6 +27,8 @@
/*!
\page qml-extending.html
+\ingroup qml-features
+\contentspage QML Features
\title Extending QML in C++
The QML syntax declaratively describes how to construct an in-memory object
@@ -360,28 +362,28 @@ pointers to invalid objects. QML makes the following guarentees:
\list
\o An object assigned to a QObject (or QObject-derived) pointer property will be
-valid at the time of assignment.
+valid at the time of assignment.
-Following assignment, it is the responsibility of the class to subsequently guard
+Following assignment, it is the responsibility of the class to subsequently guard
this pointer, either through a class specific method or the generic QPointer class.
-\o An object assigned to a QVariant will be valid at the time of assignment.
+\o An object assigned to a QVariant will be valid at the time of assignment.
-When assigning an object to a QVariant property, QML will always use a QMetaType::QObjectStar
-typed QVariant. It is the responsibility of the class to guard the pointer. A
-general rule when writing a class that uses QVariant properties is to check the
-type of the QVariant when it is set and if the type is not handled by your class,
+When assigning an object to a QVariant property, QML will always use a QMetaType::QObjectStar
+typed QVariant. It is the responsibility of the class to guard the pointer. A
+general rule when writing a class that uses QVariant properties is to check the
+type of the QVariant when it is set and if the type is not handled by your class,
reset it to an invalid variant.
-\o An object assigned to a QObject (or QObject-derived) list property will be
-valid at the time of assignment.
+\o An object assigned to a QObject (or QObject-derived) list property will be
+valid at the time of assignment.
-Following assignment, it is the responsibility of the class to subsequently guard
+Following assignment, it is the responsibility of the class to subsequently guard
this pointer, either through a class specific method or the generic QPointer class.
\endlist
Elements should assume that any QML assigned object can be deleted at any time, and
-respond accordingly. If documented as such an element need not continue to work in
+respond accordingly. If documented as such an element need not continue to work in
this situation, but it must not crash.
\section1 Signal Support
@@ -637,6 +639,7 @@ public:
/*!
\page qml-extending-types.html
+\ingroup qml-features
\title Writing QML Components: Properties, Methods and Signals
One of the key concepts in QML is the ability to define your own QML components that suit