diff options
author | Mitch Curtis <mitch.curtis@qt.io> | 2019-03-11 11:33:06 +0100 |
---|---|---|
committer | Mitch Curtis <mitch.curtis@qt.io> | 2019-03-12 10:40:11 +0000 |
commit | 70d726e91e4ef27002b2271805de19077e25809c (patch) | |
tree | 5eb2bfd6a9a880ce858401342ade14d36b63553c /src/qml/doc | |
parent | a84acc963b6684e4aa91c4dff5acf47e5f6cd8d2 (diff) |
Doc: link to C++ and QML integration flowchart
The chart makes it easier to find the correct way to register a C++
type with the QML type system, so it makes sense to link to it
from these docs.
Task-number: QTBUG-74318
Change-Id: Iba74ce02d200d6609dbb0a508d618226a6fe1e54
Reviewed-by: Paul Wicking <paul.wicking@qt.io>
Diffstat (limited to 'src/qml/doc')
-rw-r--r-- | src/qml/doc/src/cppintegration/definetypes.qdoc | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/src/qml/doc/src/cppintegration/definetypes.qdoc b/src/qml/doc/src/cppintegration/definetypes.qdoc index 0cce1895cb..f6f630c749 100644 --- a/src/qml/doc/src/cppintegration/definetypes.qdoc +++ b/src/qml/doc/src/cppintegration/definetypes.qdoc @@ -66,6 +66,8 @@ this manner, but the type cannot be used instantiated as a QML object type from QML. This is useful, for example, if a type has enums that should be exposed to QML but the type itself should not be instantiable. +For a quick guide to choosing the correct approach to expose C++ types to QML, +see \l {Choosing the Correct Integration Method Between C++ and QML}. \section2 Registering an Instantiable Object Type |