aboutsummaryrefslogtreecommitdiffstats
path: root/src/qml/doc/src/cppintegration/warning.qdocinc
diff options
context:
space:
mode:
Diffstat (limited to 'src/qml/doc/src/cppintegration/warning.qdocinc')
-rw-r--r--src/qml/doc/src/cppintegration/warning.qdocinc6
1 files changed, 6 insertions, 0 deletions
diff --git a/src/qml/doc/src/cppintegration/warning.qdocinc b/src/qml/doc/src/cppintegration/warning.qdocinc
new file mode 100644
index 0000000000..a5da22b2a7
--- /dev/null
+++ b/src/qml/doc/src/cppintegration/warning.qdocinc
@@ -0,0 +1,6 @@
+\warning Although it is possible to access QML objects from C++ and manipulate
+them, it is not the recommended approach, except for testing and prototyping
+purposes. One of the strengths of QML and C++ integration is the ability to
+implement UIs in QML separate from the C++ logic and dataset backend, and this
+fails if the C++ side starts manipulating QML directly. Such an approach also
+makes changing the QML UI difficult without affecting its C++ counterpart.