diff options
| author | Alan Alpert <alan.alpert@nokia.com> | 2011-01-13 06:21:58 (GMT) |
|---|---|---|
| committer | Alan Alpert <alan.alpert@nokia.com> | 2011-01-13 06:21:58 (GMT) |
| commit | b034416ab293a71fcedd744d503a30365b664049 (patch) | |
| tree | a6cd86990d38f9d6b7287e9349281784674a2a6f /doc | |
| parent | 7b8c7462dde454c25e92e401292e973da04f2189 (diff) | |
| download | Qt-b034416ab293a71fcedd744d503a30365b664049.zip Qt-b034416ab293a71fcedd744d503a30365b664049.tar.gz Qt-b034416ab293a71fcedd744d503a30365b664049.tar.bz2 | |
Fix doc typo
Tidy up that section a little, while I'm at it.
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/src/declarative/qtbinding.qdoc | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/src/declarative/qtbinding.qdoc b/doc/src/declarative/qtbinding.qdoc index b1de3e4..03290aa 100644 --- a/doc/src/declarative/qtbinding.qdoc +++ b/doc/src/declarative/qtbinding.qdoc @@ -255,8 +255,8 @@ Then, any QML code loaded by your C++ application or \l{QDeclarativeExtensionPlu It is advised that you avoid using QGraphicsItem functionality beyond the properties documented in QDeclarativeItem. -This is because the GraphicsView backend is an implementation detail for QML, so the QtQuick items can be moved to faster backends as they become available with no change from a QML perspective. -To minimize any porting requirements for custom visual items, try to stick to the documented properties in QDeclarative item where possible as properties it inherits but doesn't document are classed as implementation details and may disappear. +This is because the GraphicsView backend is intended to be an implementation detail for QML, so the QtQuick items can be moved to faster backends as they become available with no change from a QML perspective. +To minimize any porting requirements for custom visual items, try to stick to the documented properties in QDeclarativeItem where possible. Properties QDeclarativeItem inherits but doesn't document are classed as implementation details; they are not officially supported and may disappear between releases. Note that custom C++ types do not have to inherit from QDeclarativeItem; this is only necessary if it is a displayable item. If the item is not displayable, it can simply inherit from QObject. |