aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Update dependencies on '6.4.2' in qt/qtdeclarativev6.4.26.4.2Qt Submodule Update Bot2022-12-121-5/+5
| | | | | Change-Id: I61bf0bdd9193cb8db9dac2f82136ccf944cf909b Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
* Update dependencies on '6.4.2' in qt/qtdeclarativeQt Submodule Update Bot2022-12-091-5/+5
| | | | | Change-Id: I220d86396f801db9cebb69afc0399840f01414d3 Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
* Update dependencies on '6.4.2' in qt/qtdeclarativeQt Submodule Update Bot2022-12-071-5/+5
| | | | | Change-Id: Ia13b963fd6337195505f4442fcdec3a5c80d63c9 Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
* Revert "Build: install the metatypes inside Qt's own arch-specific data dir"Friedemann Kleint2022-12-051-1/+1
| | | | | | | | | | | | The change does not qualify for a patch release. This reverts commit ec57a5763dc5d60aab45b4a861f19c1df108175c. Change-Id: I7ef0a0b347cc313da8f379b6f044189be0f29e50 Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io> Reviewed-by: Thiago Macieira <thiago.macieira@intel.com> (cherry picked from commit 9451f5a8aed07236d618c7946ebbb6275013eaa1) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
* Update dependencies on '6.4.2' in qt/qtdeclarativeQt Submodule Update Bot2022-12-051-5/+5
| | | | | Change-Id: I77ea7f5df316780ab20912232e5c9dcf12381da8 Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
* Update dependencies on '6.4' in qt/qtdeclarativeQt Submodule Update Bot2022-12-011-5/+5
| | | | | Change-Id: Ic96ac9e37635d9708805a2938938da7bd2924ae4 Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
* doc: Add note to PinchHandler.translation property about macOS trackpadShawn Rutledge2022-12-011-0/+3
| | | | | | | | | | Translation doesn't happen with trackpad native gestures. Fixes: QTBUG-109002 Change-Id: I7d42b0d737d45405732a389560a6c77624831c9e Reviewed-by: Paul Wicking <paul.wicking@qt.io> (cherry picked from commit 786e1748d4469c135a922a221024f3f9c421c0de) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
* Remove signal index mismatch in aot-compiled codeSami Shalayel2022-11-304-2/+68
| | | | | | | | | | | | | | | | | | | | | There are multiple types of signal indexes, one of them belongs to QMetaMethod::signalIndex and another one to QObjectPrivate::signalIndex. Stop mixing them up in aot-compiled code when capturing properties as this leads to weird and hard to debug bugs. Add a smaller version of the drag and drop example as test to make sure that the bug does not appear again, without any visual elements. Fixes: QTBUG-104047 Fixes: QTBUG-104716 Change-Id: I4f64ba237e824ff0ba1624c29ddcf5371d03d69e Reviewed-by: Ulf Hermann <ulf.hermann@qt.io> Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org> Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io> (cherry picked from commit d9d247746423f6a9f1f36aa9be14fad1edcd6616)
* Fix build error in top level buildsFabian Kosmale2022-11-301-0/+1
| | | | | | | | | | | We need to set up autogen tools not onlyfor the main library but also for the plugin. Fixes: QTBUG-109010 Change-Id: I72b64c3803eb1de5f07e8dde05b87d95bc5dc7f2 Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io> (cherry picked from commit 1cae237329be3badbe75a42d061757ed2345817e) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
* Doc: Normalize page namesKai Köhne2022-11-3014-22/+22
| | | | | | | | | | | | | | qdoc does enforce lowercase file names for .html pages, and also replace underscore with a dash. Make sure that the original \page name already is normalized, so that it's easier to search. This was done by find . -name "*.qdoc" -exec perl -p -i -E "s/\\\page (.*)/\\\page \L\1/ && s/_/-/g" {} ; Change-Id: Ic67c9295741ff0ab0d3adb1d39e2927327c326d1 Reviewed-by: Paul Wicking <paul.wicking@qt.io> Reviewed-by: Luca Di Sera <luca.disera@qt.io> (cherry picked from commit 9cd445b25ff9cf9d4071664fa875642842f26981)
* Update dependencies on '6.4' in qt/qtdeclarativeQt Submodule Update Bot2022-11-291-1/+1
| | | | | Change-Id: I4207c9deafaa77b07b3da202596fe0f934f53749 Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
* Connections: Don't crash when target is deletedFabian Kosmale2022-11-283-8/+57
| | | | | | | | | Fixes: QTBUG-108697 Change-Id: I019edf3a0a702ad1dca340473265933e4d131e99 Reviewed-by: Ulf Hermann <ulf.hermann@qt.io> Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io> (cherry picked from commit 6cd8d209ec472a658a330f25b84f92cd61e0d4cf) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
* Suppress ES-compiler warnings against the ES-262 test-suiteEdward Welbourne2022-11-281-1/+43
| | | | | | | | | | | | | | | | | | V4's ES-compiler warns about assorted variables in the ES-262 test-suite being used before declaration. We aren't about to fix that test-suite, so the warnings are just noise to us. As there are many of them, they overflow the QTestLib logger's -maxwarnings threshold, causing actually relevant messages (like test failures) to be lost in the output. Install a trivial QLoggingCategory::CategoryFilter to filter out warnings and debug for the qt.qml.compiler category (and all sub-categories of it). Condition this on a define so that someone who actually wants to see those warnings can turn them on. Change-Id: If7decc241b407e816f5d7979b32f31a9f614d30f Reviewed-by: Ulf Hermann <ulf.hermann@qt.io> (cherry picked from commit c9377cd6499e86ee147c3644fb9271a19a199443)
* Split two long lines for the sake of readabilityEdward Welbourne2022-11-281-2/+8
| | | | | | | | | It's easier to see which flags are being set this way. Change-Id: I5ed7e9bcedacde19cb751512d404a872981f6eb0 Reviewed-by: Ulf Hermann <ulf.hermann@qt.io> (cherry picked from commit 6670a8b09a3d3ef92b73fbc0593f21e66020d94e) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
* qmllint: document new behavior of --jsonSami Shalayel2022-11-282-3/+4
| | | | | | | | | | | | | | | | Amends 5c04d174282a9a36ce12b26e1807d3d5051a7f33. The behavior of qmllint changed in the above-mentioned commit, as it started expecting a file argument for the --json option. Before, it was not expecting any and always writing to stdout. Document the new behavior in the docs and in the --help command, especially the part about using '-' to restore the old behavior. Fixes: QTBUG-108913 Change-Id: I3a69a794a5362a575437d3d832d6e038c7a0755a Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io> (cherry picked from commit e11c1eda4fbd1910f9089dae60e4d22bfe3bb595) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
* Debugger: Initialize scoped context correctlySemih Yavuz2022-11-265-4/+97
| | | | | | | | | | | | Initialize scopedContext with valid qmlContext. Otherwise debugger crashes on attempt to lookup an object that includes a v4Function property Fixes: QTBUG-107607 Change-Id: Iea59bdf9d379a5415abe1767f76f851978b1be3f Reviewed-by: Ulf Hermann <ulf.hermann@qt.io> (cherry picked from commit fe32f58008f89b7174e9f41a781e6fba5799c026) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
* Build: install the metatypes inside Qt's own arch-specific data dirThiago Macieira2022-11-251-1/+1
| | | | | | | | We don't want it in /lib64/metatypes, but instead /lib64/qt6/metatypes Change-Id: Id8e48e8f498c4a029619fffd17293602d7fd8bd8 Reviewed-by: Jörg Bornemann <joerg.bornemann@qt.io> (cherry picked from commit d9dfe91417e87db59825500d7b2791ad4d7516b6)
* ShaderEffect: call derefWindow from the proper sourceInho Lee2022-11-251-1/+2
| | | | | | | | | It was fixed with commit 9a3f40c45098056662cac4af5daa4e29d7476991 but 6.4 still has the same issue. Fixes: QTBUG-108683 Change-Id: I8e885e4e9aa6a2cff99ce6a7fd29aa9baa666c89 Reviewed-by: Laszlo Agocs <laszlo.agocs@qt.io>
* Revert "masm: Treat Android as generic Posix regarding mmap and friends"Ulf Hermann2022-11-252-17/+8
| | | | | | | | | | | | | | | | | | This reverts commit ffecc122d785de9c4c5defd8724526b8dd4982dc. It turns out that madvise() only fails when given MADV_WILLNEED as argument on the affected devices. MADV_WILLNEED is indeed optional. Since commit 2034e10c9378364ecc7aa1af27505562d86688de we do not crash on a failed MADV_WILLNEED anymore. Therefore, we can re-enable the linux code path for android. Task-number: QTBUG-107774 Task-number: QTBUG-106864 Task-number: QTBUG-106269 Change-Id: If67a38e4fc206bd5d5ed0ef8bf66ededd09d8f59 Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io> (cherry picked from commit ac4fea75379467dde9065825d3f15da3b86e9ad8) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
* QtQml: Recognize JavaScript null as equivalent to nullptr QObject*Ulf Hermann2022-11-243-1/+41
| | | | | | | | | | Otherwise we can go into infinite recursion there. Fixes: QTBUG-108651 Change-Id: I73a7c524b28d0eacb151f2090e3dce6afbc029d1 Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org> Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io> (cherry picked from commit c58d2e5229c39e8007ce5b93822c66af5e765a50)
* QmlCompiler: Fix comparison of null and undefinedUlf Hermann2022-11-244-11/+64
| | | | | | | | | | | | Those are not stored. If we compare null to null or undefined to undefined, we do not have to generate a comparison at all. the result is statically known. Fixes: QTBUG-108634 Change-Id: I6a5323c2e0c023838609aec90d7ecc15b885dc08 Reviewed-by: Sami Shalayel <sami.shalayel@qt.io> Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io> (cherry picked from commit bce216d5c086a5aa8f88d13933eeccebca316359)
* QmlCompiler: Generate correct code for non-double constantsUlf Hermann2022-11-242-9/+33
| | | | | | | | | | | This can actually not happen because we only use this instruction for doubles. However, it's clearly intended to be compatible with other types. Fixes: QTBUG-108820 Change-Id: I50618913373560eee6be2aeb2a9be387ff8ba753 Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io> (cherry picked from commit ed3da31fd0248d48d960de566293cd9e8d12b9f4)
* Doc: Fix import statement in QML code exampleAndreas Eliasson2022-11-231-1/+1
| | | | | | | | Fixes: QTBUG-108388 Change-Id: Iec1cae2761129c5d64afadaebabc9e4bddc4ebe4 Reviewed-by: Topi Reiniö <topi.reinio@qt.io> (cherry picked from commit 57f98b1e5c7751e84816fb8e6be7827b2c11474a) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
* QQuickItemView: Fix max(X/Y)Extent()David Redondo2022-11-236-27/+136
| | | | | | | | | | | | | | | QQuickFlickable maxXExtent() and maxYExtent() return the amount of space that is not shown when inside a ScrollView. QQuickItemView however just returned width() if vertical and height() if horizontal. In these cases just defer to the QQuickFlickable base implementation like minXExtent() and minYExtent() already do. Fixes: QTBUG-83890 Change-Id: I7f4060c2f46ae07611bedceca0d322c5f7f6affb Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io> Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io> (cherry picked from commit 99047ae219ff6689da38cc988a25030fece655da) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
* Don't crash on QQmlGadgetPtrWrapper instances in debug serviceUlf Hermann2022-11-233-2/+37
| | | | | | | | | | | They have the confusing property of being a QObject but having a QMetaObject that says it's a Q_GADGET. Fixes: QTBUG-108646 Change-Id: I6df34c2004918cd89691f4b5eb4b6267dabcd7ff Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io> (cherry picked from commit deda185ba95ffb99b1500364e2eba774e9dbc1e6) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
* QML: Check for stack overflows when creating objectsUlf Hermann2022-11-225-3/+42
| | | | | | | | Fixes: QTBUG-106875 Change-Id: I3b0abda6948b79a9e3cf263f27885037fff1804c Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io> Reviewed-by: Sami Shalayel <sami.shalayel@qt.io> (cherry picked from commit edc01fbfa430d6f0ce66f1871ab28e0f691ee252)
* Remove broken assert in QQmlPropertyData::setOverrideIndexSami Shalayel2022-11-221-1/+0
| | | | | | | | | | | | | | | The assert leads to strange crashes, as it compares if an overriding and an overridden property share the same m_coreIndex and asserts when equal. This leads to crashes when overriding a function with a property and vice-versa, as those can have an equal m_coreIndex but still is a valid override. Fixes: QTBUG-108627 Change-Id: I67f91d5fdb93603ef95b9a4557fd064edc24721d Reviewed-by: Ulf Hermann <ulf.hermann@qt.io> (cherry picked from commit d6961c09de36e15c57f29109edf5fbfef53ef4d4) Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
* Update dependencies on '6.4' in qt/qtdeclarativeQt Submodule Update Bot2022-11-211-5/+5
| | | | | Change-Id: Ibfdf3c976701068dac2fff098096ea401a42539f Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
* Port from qAsConst() to std::as_const()Marc Mutz2022-11-18170-443/+443
| | | | | | | | | | | | | | | | We've been requiring C++17 since Qt 6.0, and our qAsConst use finally starts to bother us (QTBUG-99313), so time to port away from it now. Since qAsConst has exactly the same semantics as std::as_const (down to rvalue treatment, constexpr'ness and noexcept'ness), there's really nothing more to it than a global search-and-replace. This is a 6.4 re-run of the script we ran in dev, in order to avoid conflicts between the branches when cherry-picking. Change-Id: I5eca3df3179dfb2b2682c75a479ba9a4259cc703 Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io>
* Port from container::count() and length() to size() - V5Marc Mutz2022-11-18400-4146/+4146
| | | | | | | | | | This is a the same semantic patch (qt-port-to-std-compatible-api V5 with config Scope: 'Container') as in dev. I've re-ran it in 6.4 to avoid cherry-pick conflicts. Change-Id: I9621dee5ed328b47e78919a34c307105e4311903 Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io> Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
* Don't clearPassiveGrabbers() after MouseEventSynthesizedBySystemShawn Rutledge2022-11-184-2/+95
| | | | | | | | | | | | | | | | | Windows sends synth mouse events after touch events. We avoid delivery of them in QQuickDeliveryAgentPrivate::handleMouseEvent(), but we need to avoid reacting to them here too. If the touchpoint already had a passive grabber, and the mouse event comes from the same device, then clearing the mouse passive grabbers is identical to clearing the touchpoint's passive grabbers, which we don't want to do. Amends 48b1c59b65332b773eb51d25c422b53dbd3d6762 Fixes: QTBUG-104890 Change-Id: I4c3e18fc834c7bfcba7037548c7e42627e319bda Reviewed-by: Mitch Curtis <mitch.curtis@qt.io> (cherry picked from commit 0b7ee7a48f5f32fc916cc1914b110bdf68e37486) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
* Update dependencies on '6.4' in qt/qtdeclarativeQt Submodule Update Bot2022-11-181-5/+5
| | | | | Change-Id: Ib0f29f9253232b549acfd409a32c41d0e7a284ef Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
* Doc: Add missing QQuickWindow constructorHatem ElKharashy2022-11-171-1/+5
| | | | | | | | | | | | | QQuickWindow::QQuickWindow(QQuickRenderControl *control) should be part of the public API. The user can use QQuickRenderControl with QQuickWindow to control the scenegraph rendering. This constructor is used in the QQuickRenderControl example. Change-Id: I1bb38d64173c24ba835137897ef915dfde83b1f3 Reviewed-by: Laszlo Agocs <laszlo.agocs@qt.io> (cherry picked from commit 7454d3b612eab92b8e91741fc1c51311cf80c3a2) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
* PinchHandler null target: remember accumulated scale between pinchesShawn Rutledge2022-11-174-5/+133
| | | | | | | | | | | | | | | | | | | | | This restores behavior from b4d31c9ff5f0c5821ea127c663532d9fc2cae43e which got broken in fc636af3a723ee8b4ee42cf71864ae0df5ca4621. As documented, PinchHandler.scale is the accumulated scale that would be applied to the target item (even if there is no target), whereas activeScale is the scale during one pinch gesture. After the first gesture, these two values are supposed to diverge, even if there is no target; that way you can bind scale to some property, to scale something else in the same way that PinchHandler would normally scale its target. Fixes: QTBUG-108549 Task-number: QTBUG-68941 Task-number: QTBUG-92064 Change-Id: I32ff37e394fd8466128603eddd5697ba1cc1a0ed Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org> Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io> (cherry picked from commit 3046fe153dd2c5679479eb512dcee6bdc80bd1cf) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
* Make tst_QQuickPinchHandler::scale easier to maintainShawn Rutledge2022-11-172-75/+86
| | | | | | | | | | | | | | | | | | | | | | | | | I kept forgetting why there were odd indented blocks, why it was letting the QTouchEventSequence go out of scope and making a new one, and why that resulted in an out-of-bounds pinch. It works well enough to just drag the second touchpoint all the way down into the lower-right corner: without maximumScale being set, it goes to 5.75, so we can verify that setting maximumScale limits it to 4. While we're at it: - use QQuickTest::showView() - better comments - loop instead of copy-pasting blocks of code - show the touchpoints - slow it down enough to see them when cat. logging is turned on - get rid of that weird opacity hack - check pinchHandler's own scale() and activeScale() properties Amends f289141524d9331bdafd9f88d95e0fa9b29ccdee Change-Id: I799c256286f4408f89c0502db33c9f676a2ce1b1 Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io> (cherry picked from commit b0a3a07a68d64fb8f32969e1dc88923fd58c0adf) Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
* tst_qquickpinchhandler: rename root.scale property to pinchScaleShawn Rutledge2022-11-172-13/+13
| | | | | | | | | | | | | It doesn't look sensible to hide the existing Item.scale property. PinchArea's properties are directly accessible in test code, but maybe there's some sense in testing the onActiveChanged and onUpdated signals. Amends f289141524d9331bdafd9f88d95e0fa9b29ccdee which copied code from tst_qquickpincharea. Change-Id: I108fffc9b99b4eebc949fe11c9b7dd649d98f59a Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io> (cherry picked from commit 3d9ece8e578e0f6abcff1484669444355ad218c6) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
* tooling: silence -Wmissing-variable-declarationsTim Blechmann2022-11-161-3/+6
| | | | | | | | | silence clang's -Wmissing-variable-declarations Change-Id: I40189c219bfeaeba103a56a08e489b019e2905bd Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org> Reviewed-by: Ulf Hermann <ulf.hermann@qt.io> (cherry picked from commit 6b03bc92739d7ae5f38093162ec9d2ca25ff8906)
* tooling: silence -Wextra-semi-stmtTim Blechmann2022-11-164-14/+14
| | | | | | | | silence clang's -Wextra-semi-stmt Change-Id: I5dee9ec46b44076f0fc0590399131b1b267e1ad2 Reviewed-by: Ulf Hermann <ulf.hermann@qt.io> (cherry picked from commit aadf0243c693d6bfd9009278b883e1d5b1015097)
* qml: silence -Wextra-semiTim Blechmann2022-11-1623-28/+28
| | | | | | | | | | silence gcc's -Wextra-semi. the private headers are pulled in via the type compiler Change-Id: I5291d007c379f522c2dae9d814c4f4cc6a7d118a Reviewed-by: Ulf Hermann <ulf.hermann@qt.io> (cherry picked from commit 6b9c5f6ed7b768dc918feac76bf40cdffb72bfe7) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
* QQuickTableView: do a relayout whenever the view is resizedRichard Moe Gustavsen2022-11-153-3/+69
| | | | | | | | | | | | | | | | | | | | | | | If you place a TableView in e.g a StackLayout, it will have a zero size until it becomes the active view the layout. If the delegate then has a binding that e.g looks like: implicitWidth: TableView.view.width it will fail, since the width of the view is zero at time of creation, but at the same time, never updated again once the view becomes visible (and resized). This patch will therefore ensure that we do a relayout each time the view is resized, since having such a dependency in the delegate (or in the columnWidthProvider) must be expected to be quite common. Change-Id: I92f4f51f6b6c634c2627716c41ea4971fb8d1653 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io> (cherry picked from commit 3cacdf288fa70e6f108b79a5752682329babf4c6) Reviewed-by: Samuel Ghinet <samuel.ghinet@qt.io>
* Doc: Fix \brief for color QML value typeTopi Reinio2022-11-151-1/+1
| | | | | | | | | | | | The following \target line was interpreted as being part of the brief statement. Replace the \target with a \keyword which is better for linking to a topic (instead of a subsection) and move the command up in order not to clash with \brief. Change-Id: I37c1058955f94ba3f9d36fbb078810b9ffdfcf40 Reviewed-by: Paul Wicking <paul.wicking@qt.io> (cherry picked from commit 27d5f1b1335b31b4b26e882d853032fbf2b2df30) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
* Update dependencies on '6.4' in qt/qtdeclarativeQt Submodule Update Bot2022-11-141-5/+5
| | | | | Change-Id: I7b6bedee1bfe0de808a0e17efa921cb745f0bc45 Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
* Stabilize tst_TouchMouse::strayTouchDoesntAutograbShawn Rutledge2022-11-121-0/+9
| | | | | | | | | | | | | | Apparently GrabMonitor sees all grab transitions in prior autotests up until strayTouchDoesntAutograb() runs; so it's surprising that it ever passed. Now we reset its state to initial conditions at the beginning. Amends 5ced8ec177fd730676eb854aea559a5f324a39b6 Fixes: QTBUG-108352 Change-Id: I31c398f9cd08b2281ea82054b667437f1151f0bd Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io> Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org> (cherry picked from commit 195dcc11c7fbb69e78264398fcfa09c63089b606) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
* QQuickTableView: detect if syncView topLeft has changedRichard Moe Gustavsen2022-11-113-2/+56
| | | | | | | | | | | | | | | | | It can happen that the top left cell in syncView changes after a normal relayout. This is especially prone to happen if the cells used to be large, but are suddenly made much smaller, such that the top left cell ends up outside the viewport. This patch will detect this case, and ensure that the top left is being recalculated when they are no longer in sync. Change-Id: I80cad2859a35e0f3bc58f101696112be7c084175 Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io> (cherry picked from commit f15528407033057fb5c6e6ba5bbe8e5936fe346b) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
* Send ObjectShow event for visible components after initializedFushan Wen2022-11-111-0/+7
| | | | | | | | | | | | | | | Currently ObjectShow event is only sent when the visible property changes from false to true, but for items with the notification accessible role, a screen reader like Orca needs to receive an ObjectShow event to read the notification, so also send the event after a component is initialized. See also: https://gitlab.gnome.org/GNOME/orca/-/merge_requests/134 Change-Id: I626594b65ffe4d0582dcee9f489df0c2c63e53b7 Reviewed-by: Jan Arve Sæther <jan-arve.saether@qt.io> (cherry picked from commit 9a4f2d23ecec2c7ff19f83cff28df6b97e3fda98) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
* Handle missing stops gracefully in Shape gradientsLaszlo Agocs2022-11-111-3/+5
| | | | | | | | Fixes: QTBUG-108298 Change-Id: Ib6e004a1518aec4c786c3aeebcd74e6cb11f45ef Reviewed-by: Andy Nichols <andy.nichols@qt.io> (cherry picked from commit e52efc3defe102a55b45b013764ba1bae1fe5a1b) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
* Bump version to 6.4.2Jani Heikkinen2022-11-111-1/+1
| | | | | Change-Id: I88181af8a19a43e9ac303fcf04b97c904497dcd9 Reviewed-by: Jani Heikkinen <jani.heikkinen@qt.io>
* Update dependencies on '6.4' in qt/qtdeclarativeQt Submodule Update Bot2022-11-111-5/+5
| | | | | Change-Id: I4f638522c4aac3af70b52a0ac98b51d71ec033dc Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
* Document dangers with parentChanged and visibleChangedVolker Hilsheimer2022-11-111-0/+12
| | | | | | | | | | | | | | | | | | | | | | | | These signals get emitted by the QQuickItem destructor for the item under destruction, but also for the visual child items, as they get removed from the parent. Connected code that references parent objects might crash. We can't block those signal emissions as code relies on them to remove pointers from data structures, and for items that are not also QObject- children we have to emit the signals anyway as they will not get destroyed, and their properties do change. The best we can do is to document that it's potentially dangerous to operate on visual parent objects in code connected to those signals. Note that the visibleChanged signal does not get reliably emitted when a parent in the visual hierarchy gets destroyed. Task-number: QTBUG-107850 Change-Id: I87913658818ec9491a4c4e799d9c553de44ea9c2 Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io> (cherry picked from commit a142f8efd0cb6938f697375ee7cfc240722d7215) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
* Fix the popup position of a MenuInho Lee2022-11-101-1/+2
| | | | | | | | | | | | QPA code should operate in native coord. Treat QWidgetPlatformMenu::showPopup's input as native coord. Fixes: QTBUG-94619 Fixes: QTBUG-94783 Change-Id: Iaa030c96d84e4a588e625fe191e4324f70be961f Reviewed-by: Morten Johan Sørvig <morten.sorvig@qt.io> (cherry picked from commit f8cf17166c9af147f0b8fea72f5b4a8a6098a5d7) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-09 02:50:43 +0000