qt/qtdeclarative.git/tests/auto/qml/qqmllanguage/testhelper/declarativelyregistered.h, branch dev Qt Declarative (Quick 2) Correct license tag for qqmllanguage testhelper 2024-06-27T07:17:10+00:00 Lucie Gérard lucie.gerard@qt.io 2024-06-26T10:52:36+00:00 f98a356646a2f9f444152d5ab1d6779741c3dbe2 According to QUIP-18 [1], all tests file should be LicenseRef-Qt-Commercial OR GPL-3.0-only [1]: https://contribute.qt-project.org/quips/18 Task-number: QTBUG-121787 Change-Id: I8a5bf02efb41933b8e89fe2c372831c1b0e5eb0b Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io> 
According to QUIP-18 [1], all tests file should be
LicenseRef-Qt-Commercial OR GPL-3.0-only

[1]: https://contribute.qt-project.org/quips/18

Task-number: QTBUG-121787
Change-Id: I8a5bf02efb41933b8e89fe2c372831c1b0e5eb0b
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
qmlTypeId: Import unregistered modules 2024-06-17T15:36:03+00:00 Fabian Kosmale fabian.kosmale@qt.io 2023-10-17T10:23:15+00:00 336efa68a3624d2c8e1d28ec445bcf261318acc0 When using the imperative registration API, one could first register all types and then query the engine for their id via qmlTypeId. With the declarative API, there is no such "safe point" (short of creating a QML engine, and importing the module there). We can't really avoid the creation of an engine (something has to import the module before it becomes available), but we can hide it in the implementation of qmlTypeId, so that the function "just works™". This uses the same logic as QQmlComponent::loadFromModule behind the scenes, but stops short of creating the object, as we only need the QQmlType for its id. Pick-to: 6.8 6.7 6.5 Fixes: QTBUG-118165 Change-Id: Iec456140c32c036ae91db62be5a598ffc8b34607 Reviewed-by: Ulf Hermann <ulf.hermann@qt.io> 
When using the imperative registration API, one could first register all
types and then query the engine for their id via qmlTypeId. With the
declarative API, there is no such "safe point" (short of creating a QML
engine, and importing the module there).

We can't really avoid the creation of an engine (something has to import
the module before it becomes available), but we can hide it in the
implementation of qmlTypeId, so that the function "just works™".
This uses the same logic as QQmlComponent::loadFromModule behind the
scenes, but stops short of creating the object, as we only need the
QQmlType for its id.

Pick-to: 6.8 6.7 6.5
Fixes: QTBUG-118165
Change-Id: Iec456140c32c036ae91db62be5a598ffc8b34607
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>