From e50eeaf3a2cb1ec8d4d96b695245b86782284d81 Mon Sep 17 00:00:00 2001 From: Mitch Curtis Date: Tue, 8 May 2018 09:16:57 +0200 Subject: Doc: link to integration flowchart in "Interacting with QML from C++" Replace the link to the more specific "Integrating QML and C++" page with a link to "Choosing the Correct Integration Method Between C++ and QML", as the flowchart is a much quicker way for users to determine the correct approach for their use case. Change-Id: Ia2c269f9149d801644407bba7388624d69a75564 Reviewed-by: Venugopal Shivashankar --- src/quick/doc/src/guidelines/qtquick-bestpractices.qdoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/quick/doc/src/guidelines/qtquick-bestpractices.qdoc b/src/quick/doc/src/guidelines/qtquick-bestpractices.qdoc index b22b013684..30aca38678 100644 --- a/src/quick/doc/src/guidelines/qtquick-bestpractices.qdoc +++ b/src/quick/doc/src/guidelines/qtquick-bestpractices.qdoc @@ -318,8 +318,8 @@ component loaded by the engine. Context properties are useful for objects that must be available as soon as the QML is loaded and cannot be instantiated in QML. -\l {Integrating QML and C++} demonstrates an alternative approach where QML is -made aware of a C++ type so that it can instantiate it itself. +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 Related Information \list -- cgit v1.2.3