qt/qtdeclarative.git, branch v6.8.3 Qt Declarative (Quick 2) Doc: Fix issues with \fn signatures 2025-03-18T15:11:25+00:00 Topi Reinio topi.reinio@qt.io 2025-03-06T13:15:17+00:00 2ec235a2235a119887683e55787b93f99dc5f12f Move QQmlSA::LoggerWarningId function documentation out of the QQmlJS namespace, as that causes match failures with QDoc. Qualify QQmlSA::Method and Element \fn signatures with the correct scope to help QDoc match them. Task-number: QTBUG-134250 Change-Id: I89407afe251158d99a93f44c25bb6db1a83a6024 Reviewed-by: Paul Wicking <paul.wicking@qt.io> Reviewed-by: Olivier De Cannière <olivier.decanniere@qt.io> (cherry picked from commit f1862814b0c6f7bdd304119270fc7554411ff598) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org> (cherry picked from commit 6cf992796781ad3060196e6229b547019a97ab4e) (cherry picked from commit 83eda05c84a7ee878afbbb610028ae0d1a04a57f) Reviewed-by: Topi Reiniö <topi.reinio@qt.io> 
Move QQmlSA::LoggerWarningId function documentation out of the
QQmlJS namespace, as that causes match failures with QDoc.

Qualify QQmlSA::Method and Element \fn signatures with the correct
scope to help QDoc match them.

Task-number: QTBUG-134250
Change-Id: I89407afe251158d99a93f44c25bb6db1a83a6024
Reviewed-by: Paul Wicking <paul.wicking@qt.io>
Reviewed-by: Olivier De Cannière <olivier.decanniere@qt.io>
(cherry picked from commit f1862814b0c6f7bdd304119270fc7554411ff598)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit 6cf992796781ad3060196e6229b547019a97ab4e)
(cherry picked from commit 83eda05c84a7ee878afbbb610028ae0d1a04a57f)
Reviewed-by: Topi Reiniö <topi.reinio@qt.io>
Update dependencies on '6.8.3' in qt/qtdeclarative 2025-03-18T15:11:22+00:00 Qt Submodule Update Bot qt_submodule_update_bot@qt-project.org 2025-03-18T04:08:21+00:00 e27f5a0b8ddb89055550b6be189f3058989f6ecd Change-Id: Ic6d701ba83dfeeb087c703ec0d1df9225b9409d1 Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org> 
Change-Id: Ic6d701ba83dfeeb087c703ec0d1df9225b9409d1
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
Update dependencies on '6.8.3' in qt/qtdeclarative 2025-03-15T17:04:16+00:00 Qt Submodule Update Bot qt_submodule_update_bot@qt-project.org 2025-03-14T20:04:17+00:00 0cbe3db1762a359c5d0eb0cfeb2a2f60b0d09cd4 Change-Id: I974e598247a0f89555bc3eb4a7934877d147373a Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org> 
Change-Id: I974e598247a0f89555bc3eb4a7934877d147373a
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
doc: update qmlls limitations section 2025-03-13T19:50:46+00:00 Sami Shalayel sami.shalayel@qt.io 2025-03-07T15:33:54+00:00 2da27d828afac70b839e44ebe8528a49b6a17d8f Update the qmlls limitations section to 6.8. Task-number: QTCREATORBUG-32591 Change-Id: I4725d384de7f89f92c461105232c5bb684b1a058 Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io> Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io> (cherry picked from commit e598fc4786df03fe2b0a70daa528b484c7b6c731) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org> (cherry picked from commit 1d113b5fe9b836178622b47e0fceded2d6d29a2b) (cherry picked from commit 9a2ebc4dd3e03e936e92577155ab7eac792ad6d5) 
Update the qmlls limitations section to 6.8.

Task-number: QTCREATORBUG-32591
Change-Id: I4725d384de7f89f92c461105232c5bb684b1a058
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io>
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
(cherry picked from commit e598fc4786df03fe2b0a70daa528b484c7b6c731)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit 1d113b5fe9b836178622b47e0fceded2d6d29a2b)
(cherry picked from commit 9a2ebc4dd3e03e936e92577155ab7eac792ad6d5)
QQuickItemView: Disconnect forgotten model signal on model change 2025-03-13T19:50:25+00:00 Ulf Hermann ulf.hermann@qt.io 2025-03-04T14:40:46+00:00 76188bc343622c1cf8d9b01465e92b666f70c6a4 If we connect it, we also need to disconnect it. Otherwise the old model may still interact with the item view after being replaced. Fixes: QTBUG-134320 Change-Id: I918a77f1dde2a474e6ea9cfd40c0a7ed775e0f3c Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io> Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io> (cherry picked from commit a1d6b83cfed7eb0c5427bbf4ad3397411ebc4a7f) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org> (cherry picked from commit 5cbf77bd46ea74a90b731902038ff525a2e6cecd) (cherry picked from commit 426227a92b0bd4d3b7b1e8f225354e5de56081b2) 
If we connect it, we also need to disconnect it. Otherwise the old
model may still interact with the item view after being replaced.

Fixes: QTBUG-134320
Change-Id: I918a77f1dde2a474e6ea9cfd40c0a7ed775e0f3c
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
(cherry picked from commit a1d6b83cfed7eb0c5427bbf4ad3397411ebc4a7f)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit 5cbf77bd46ea74a90b731902038ff525a2e6cecd)
(cherry picked from commit 426227a92b0bd4d3b7b1e8f225354e5de56081b2)
test: Improve robustness of tst_QQuickText::baselineOffset() 2025-03-13T05:32:03+00:00 Eskil Abrahamsen Blomfeldt eskil.abrahamsen-blomfeldt@qt.io 2025-03-04T16:35:42+00:00 aeafeb092250a038a073fd4e8e436dc38dd7fc9d The scaled data sets for the baselineOffset test basically implements another version of the font-fitting algorithm and then checks that the one in Qt Quick gives the same results as this. But there was one crucial difference: The algorithm that provides the expected value has the maximum font size at 10000, so it will try to find the best fit between 10000 and 0. But the maximum size in the "actual" result was set to 64, so it would try to find a match between 0 and 65. Therefore the two algorithms might end up with different fitting values that were within the margin of 0.01. In one particular case, on macOS, it seems that the point size of 64 just happened to fit exactly inside the width of 200. Due to some change in Harfbuzz 10.3.0 (most likely the AAT optimizations), it became possible to find a better match, but this appears to have been a ticking time bomb. Change-Id: I87188cbfd9070edc7b9c036f18d005ab9dd24026 Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io> (cherry picked from commit 4c3584e22563e268e7beb97d592612d8254cfb87) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org> (cherry picked from commit e5327ff188d4692078429fd4516b9d2479192b44) (cherry picked from commit 1ec4344467aae4ed90cf9708431c16f59afd1729) Reviewed-by: Mitch Curtis <mitch.curtis@qt.io> 
The scaled data sets for the baselineOffset test basically
implements another version of the font-fitting algorithm and then
checks that the one in Qt Quick gives the same results as this.

But there was one crucial difference: The algorithm that provides
the expected value has the maximum font size at 10000, so it will
try to find the best fit between 10000 and 0. But the maximum
size in the "actual" result was set to 64, so it would try to
find a match between 0 and 65.

Therefore the two algorithms might end up with different fitting
values that were within the margin of 0.01.

In one particular case, on macOS, it seems that the point size
of 64 just happened to fit exactly inside the width of 200.
Due to some change in Harfbuzz 10.3.0 (most likely the AAT
optimizations), it became possible to find a better match, but
this appears to have been a ticking time bomb.

Change-Id: I87188cbfd9070edc7b9c036f18d005ab9dd24026
Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io>
(cherry picked from commit 4c3584e22563e268e7beb97d592612d8254cfb87)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit e5327ff188d4692078429fd4516b9d2479192b44)
(cherry picked from commit 1ec4344467aae4ed90cf9708431c16f59afd1729)
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
Update dependencies on '6.8.3' in qt/qtdeclarative 2025-03-13T05:31:59+00:00 Qt Submodule Update Bot qt_submodule_update_bot@qt-project.org 2025-03-12T16:01:00+00:00 60237f8a3e7da898b64e5e4b1b668d291e31a979 Change-Id: Id533ad7fa1f95af6523dc8154177652e090f1188 Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org> 
Change-Id: Id533ad7fa1f95af6523dc8154177652e090f1188
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
QtQml: Always load from existing compilation units first 2025-03-11T12:20:41+00:00 Ulf Hermann ulf.hermann@qt.io 2025-03-03T18:12:01+00:00 c1cd57d65162655859f8e64e30a08f12ff6b8d63 If a compilation unit for the given URL already exists in the type registry, we can safely use it since anything in the type registry is shareable. An exception to this are requests with explicit inline source code. Those cannot be cached at all. Conversely, if we were to re-compile, that's not only wasteful but we may end up with diverging type hierarchies and mismatched types. Revert commit d0e16e3f614d73f6694863d2cfb1fbd661c34e3f since it has become counter-productive now. We really want to have exactly one base compilation unit for each type, and that should be universally accessible. When d0e16e3f614d73f6694863d2cfb1fbd661c34e3f was written we had separate base CUs for each engine, and we didn't want those to accidentally find each other. Realize that composite types have to be indexed by url(), not finalUrl(), since url() includes any file selectors while finalUrl() does not. Fixes: QTBUG-134398 Change-Id: I130cdc27ebd8a2814e194478a27eef5bb7f79eb7 Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io> (cherry picked from commit 6468df7657f6af4de8727363c7f7d97b680b1867) (cherry picked from commit d599310ae9142a76196ac5968a5639ad66c5de06) Reviewed-by: Ulf Hermann <ulf.hermann@qt.io> 
If a compilation unit for the given URL already exists in the type
registry, we can safely use it since anything in the type registry is
shareable. An exception to this are requests with explicit inline source
code. Those cannot be cached at all.

Conversely, if we were to re-compile, that's not only wasteful but we
may end up with diverging type hierarchies and mismatched types.

Revert commit d0e16e3f614d73f6694863d2cfb1fbd661c34e3f since it has
become counter-productive now. We really want to have exactly one base
compilation unit for each type, and that should be universally
accessible. When d0e16e3f614d73f6694863d2cfb1fbd661c34e3f was written we
had separate base CUs for each engine, and we didn't want those to
accidentally find each other.

Realize that composite types have to be indexed by url(), not
finalUrl(), since url() includes any file selectors while finalUrl()
does not.

Fixes: QTBUG-134398
Change-Id: I130cdc27ebd8a2814e194478a27eef5bb7f79eb7
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
(cherry picked from commit 6468df7657f6af4de8727363c7f7d97b680b1867)
(cherry picked from commit d599310ae9142a76196ac5968a5639ad66c5de06)
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
doc: add links to "Port QML Modules to CMake" page 2025-03-10T05:52:28+00:00 Sami Shalayel sami.shalayel@qt.io 2025-02-28T08:58:29+00:00 ff0352cdefdde86f344a6fe742c1c8658fae867c Add links to "Port QML modules to CMake" page so people know that they shouldn't write QML Modules and qmldir files by hand when they use CMake. Its only required for QMake. Also link the "Modern QML module" and "Port QML modules to CMake" pages as \sa to the documentation about QML modules. Task-number: QTBUG-133547 Change-Id: I36298cd58b6206c59d6a6545cb55fb2f97c47153 Reviewed-by: Ulf Hermann <ulf.hermann@qt.io> Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io> (cherry picked from commit cd38ca407654c7b5ebd497185faadd76012fa9a8) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org> (cherry picked from commit d9f471395e9b6b5bdf91d925d2f7c4751b60cd36) (cherry picked from commit 6520709bb873786111dd818210c6f27ff0c84e7d) 
Add links to "Port QML modules to CMake" page so people know that they
shouldn't write QML Modules and qmldir files by hand when they use CMake.
Its only required for QMake.
Also link the "Modern QML module" and "Port QML modules to CMake" pages
as \sa to the documentation about QML modules.

Task-number: QTBUG-133547
Change-Id: I36298cd58b6206c59d6a6545cb55fb2f97c47153
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io>
(cherry picked from commit cd38ca407654c7b5ebd497185faadd76012fa9a8)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit d9f471395e9b6b5bdf91d925d2f7c4751b60cd36)
(cherry picked from commit 6520709bb873786111dd818210c6f27ff0c84e7d)
doc: document how to write modern QML Modules 2025-03-07T14:24:58+00:00 Sami Shalayel sami.shalayel@qt.io 2025-02-18T15:34:19+00:00 3d18d15d382d1f020920236c9370789e6ccf1f39 Add two documents on how to write modern QML Modules, one for porting to qt_add_qml_module and one for modernizing QML Modules created with qt_add_qml_module. Fixes: QTBUG-133547 Change-Id: Ieb1f23d6600b17bfa8a949633e1e9192004804d0 Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io> Reviewed-by: Olivier De Cannière <olivier.decanniere@qt.io> (cherry picked from commit 45f024c54086eed57851725932168dc8cd7bd633) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org> (cherry picked from commit 16296160b2663d2d167374ff219aa499272886b1) (cherry picked from commit 36375f88409bcf839efa6fdf66ee3f586342ad54) Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io> 
Add two documents on how to write modern QML Modules, one for porting to
qt_add_qml_module and one for modernizing QML Modules created with
qt_add_qml_module.

Fixes: QTBUG-133547
Change-Id: Ieb1f23d6600b17bfa8a949633e1e9192004804d0
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io>
Reviewed-by: Olivier De Cannière <olivier.decanniere@qt.io>
(cherry picked from commit 45f024c54086eed57851725932168dc8cd7bd633)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit 16296160b2663d2d167374ff219aa499272886b1)
(cherry picked from commit 36375f88409bcf839efa6fdf66ee3f586342ad54)
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>