qt-creator/tests/manual/qml/testprojects/modulemapping/README.txt

This is a test for the module mapping feature used by Qt for MCUs.

Please add this source directory to the QML_IMPORT_PATH! A Qt for MCUs kit will do this automatically, but other kits
won't.

You can check that it works by going to test.qml, and "myproperty" should not be underligned as error. Without mapping,
the use of Button would resolve to QtQuick.Control's Button, which doesn't have that property. With the mapping, it
redirects to MyControls's Button which does have the property. You can verify this by control/command-clicking on the
property. This should take you to MyControls/Button.qml.
Support for QML module mapping QUL uses module mapping for theming of QtQuick.Controls: during code-generation the compiler is pointed to the Controls implementation it should use. This is done by rewriting any import of QtQuick.Controls with the given module name. The CMake build scripts will write a file for each target to the directory "qml_module_mappings" in the build dir, and those files will contain the mappings used. Fixes: QTCREATORBUG-25356 Change-Id: I3f74897836dde7717b03bd6dffa46dcc0689ffdd Reviewed-by: Fawzi Mohamed <fawzi.mohamed@qt.io> 2021-03-17 11:38:33 +01:00			`This is a test for the module mapping feature used by Qt for MCUs.`

			`Please add this source directory to the QML_IMPORT_PATH! A Qt for MCUs kit will do this automatically, but other kits`
			`won't.`

			`You can check that it works by going to test.qml, and "myproperty" should not be underligned as error. Without mapping,`
			`the use of Button would resolve to QtQuick.Control's Button, which doesn't have that property. With the mapping, it`
			`redirects to MyControls's Button which does have the property. You can verify this by control/command-clicking on the`
			`property. This should take you to MyControls/Button.qml.`