| Commit message (Collapse) | Author | Age | Files | Lines |
| |\
| |
| |
| | |
Qt 6.5.8-lts-lgpl release
|
| | |\
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Qt 6.5.8-lts release
Conflicts solved:
dependencies.yaml
Change-Id: Id2eeb915139bdd1943ffc498173db540f22ca2f3
|
| | | |
| | |
| | |
| | |
| | | |
Change-Id: I88dc363651c09d5243eb1b8d6e79a0762394b9cb
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Overlays are positioned so that they are centered over the content item
within the window. If the window has a null-size when this is computed,
then the overlay ends up being misplaced, and overlay-provided services,
such as modality or closing popups, stops working for parts of the UI.
Fix this by resizing the offscreen window before resizing the content
item.
Add a second test case that verifies that the overlay geometry is as it
should be, both after the initial show, and after resizing the widget.
The existing resizeOverlay test doesn't use a proper QQuickOverlay, so
it doesn't cover all the relevant code.
Adjustment for 6.5: the test case fails for SizeViewToRootObject in 6.5
as the overlay does not follow the size of the content item in that
version. Mark that as an expected failure.
Fixes: QTBUG-125135
Task-number: QTBUG-115536
Change-Id: I682d87f07051d213d3bd58c1c2533c84b50a3139
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
(cherry picked from commit f71ef0d8b8d25b80833228fe4e4bfa716bceb398)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit 9c0aa4cbb7fb50804ce4d1fd1841c49b2866a7af)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This comes up often online, so let's document the official advice.
Change-Id: I926326bc3b033d38746a508e5c448b5b055effeb
Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
(cherry picked from commit e7286e3f5fcabc921fc794f7099c9da4e8ceb01b)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit c4d8cbe292d3662067b959861c14f3cf8bdfa454)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is mentioned in a couple of places, so add a dedicated section
and link to it.
Also add a section to the Qt Quick best practices page.
Change-Id: I0ba528e6c37b0c9c82ca1847817251f176b7f978
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
(cherry picked from commit 473fc5005e2811347f00679e56e90ec0915f8041)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit 5da227d5681f7d0e4e0ca6f0c3f626487c191e98)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Fixes: QTBUG-128577
Change-Id: Ib6d97450e8aa6e55531ff5a20d86105e4f2db565
Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
(cherry picked from commit c36c6881c703639ada2342b160b405474b7f57c6)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit ef1dc2a9ca1997b01acc4f5c70756cef6d3db1ab)
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
|
| | | |
| | |
| | |
| | |
| | | |
Change-Id: I8ccad92c82419b626a53b6e8bd1329fb14a23fb9
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
| | | |
| | |
| | |
| | |
| | | |
Change-Id: I2b58e6322ff25ae9b64e0a4d5c1ecabaea55c5af
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Probably has not been updated for a while now, copy pasting and running
the example leads to unqualified access warnings.
https://doc.qt.io/qt-6/qtquick-modelviewsdata-modelview.html
"In most cases you should use required properties to pass model data
into your delegates."
Fix the snippet by using required properties.
Change-Id: I4a46f1ff29712238dd22bf4455a6674d8bdc0f49
Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
Reviewed-by: Juha Vuolle <juha.vuolle@qt.io>
(cherry picked from commit 13da0d8133fefba2564dfa014020dd1c968bf0f5)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit 926993500dc7d07dc65f194d02c6b52304189b08)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Otherwise the linker may omit the testhelper library, and the test that
looks for a type from that library may fail.
Amends commit 336efa68a3624d2c8e1d28ec445bcf261318acc0
Fixes: QTBUG-131263
Change-Id: I7efb58c71307f76db0edca943027b55c494cc6af
Reviewed-by: Olivier De Cannière <olivier.decanniere@qt.io>
(cherry picked from commit 6a4430f41364975f374afacac4f5628cc13c8eeb)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit a37a3db0633f6fbfb4c442c869fdf60e1cbc69d3)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We have to match the next capture one character past the last one, not
at the same place. Otherwise we match the same thing again.
Fixes: QTBUG-130974
Change-Id: Ifc1cf7c95c7777ba7140f141b26455e155db73db
Reviewed-by: Sami Shalayel <sami.shalayel@qt.io>
(cherry picked from commit 9d9413f3d3983b1d24fd878da14eed153e83cbaa)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit 9156754ab226934f248dea90d7b256e1abf8c2f4)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
MouseArea didn't emit pointChanged when entering mouseArea.
Now tst_QQuickMouseArea::hoverPosition() expects mouseX, mouseY and
pointChanged signals to be emitted when the mouse enters. Also stopped
depending on root properties in the test: there's nothing wrong with
checking MouseArea using its own API, in its own autotest where we have
the #include.
Fixes: QTBUG-127122
Change-Id: I76ee3160ebc2970f8ddd20a4fc531a4d6a16a50b
Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
(cherry picked from commit 49308d5d048a8d7bcf1557db0fd6ccf1460fa042)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit d6c5a31136d4d0d213ac6a3a4fa069ab410b523b)
|
| | | |
| | |
| | |
| | |
| | | |
Change-Id: I031e95a6a5841382cc52d412c5f9804657bf28b5
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
90a0d4023206cfeed1bec43cb11e026ff0379d3d changed the height calculation
of ComboBox's popup, but forgot to update the customization docs.
This fixes the popup not being scrollable when it exceeds the height of
the window.
Change-Id: I822888c3d979d06c21cd7ca081dae48115bb375e
Reviewed-by: Doris Verria <doris.verria@qt.io>
Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
(cherry picked from commit 9c72d7f3dcf5179975edf759173bca5d46f566c9)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit e81d4be523eaca2f3ad075a61d00f94d21cdf17b)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The function would ignore the depth and read memory that it shouldn't,
which can cause hard-to-diagnose failures, and heap-buffer-overflows
when ASAN is enabled.
Mismatches in depth can happen when optimizing images with optipng,
for example, which may convert color images to grayscale.
compareImages was added in 7ffea4048321b86402a9ded5255ad16ac74d0518.
Change-Id: Id83dcd79ae94088996ff770d90b2c1add910fb1b
Reviewed-by: Eirik Aavitsland <eirik.aavitsland@qt.io>
(cherry picked from commit a5412bece857c5e2742a9cc2dc2e65539416a17b)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit 978213a20472911ff77eac71dd4748ee09943754)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If we have an import namespace, QQmlTypeNameCache::isValid will always
return true; what we want to check instead is whether the type is valid,
or whether we need to query the namespace.
Amends a363aa3df44da399d2aeb8785608501eae50e600.
Fixes: QTBUG-118879
Change-Id: Iaa9db015979c9454662c6fbcd691dbfb03a3d053
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
(cherry picked from commit cfd7198d167b1208cb351ec907e59fa85ca59ba4)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit 45d532b788fd0df2c462fed110f50158d8b7a3fb)
Reviewed-by: Sami Shalayel <sami.shalayel@qt.io>
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The detailed text background was hardcoded to a light color. This of
course didn't work well in Dark mode, and caused text (light foreground
color) to be unreadable on the light background color.
Task-number: QTBUG-123764
Change-Id: I95801d865de880e62059be37cfaad0cf8efa6ab5
Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
(cherry picked from commit 2aed62bd272295985b77103992669b1c5406e03e)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit d49fde914956c575a87ea616f283c763eb7e16b9)
|
| | | |
| | |
| | |
| | |
| | | |
Change-Id: Ie530d00e373b131ee85dfa3cfe87c2cb1fbcaf75
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When trying to position items above an active popup, users will
typically have to reparent those items to the overlay. But doing so, can
break input handling when using modal popups. Since
childMouseEventFilter will cause the overlay to filter events, sent to
it's children, and modal popups assumes it's unsafe to not block those
events if the target item doesn't belong to itself.
It appears the assumption is that only popup items (and dimmers) will be
parented to the overlay, but in reality, any item can, by assigning the
parent to be `Overlay.overlay`. If the item is rendered above a modal
popup, then maybe that popup shouldn't filter the event, similar to the
exception it makes for its own child items.
Task-number: QTBUG-129520
Fixes: QTBUG-130331
Change-Id: Id7b69570eb6598d1ef030e0b7230489046444e45
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
(cherry picked from commit 01de98703916ef485f8934485270478b90a524f6)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit de48b440c5fd078f4a680b9d3c7074769235d2d0)
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Setting the cursorShape property to undefined, the MouseArea will
not change the cursor from its existing shape when entering it.
Let users know about this.
Fixes: QTBUG-124533
Pick-to: 6.2
Change-Id: I78cb3f8a7ffdfdd9f9504314bced20b46ec319c0
Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
(cherry picked from commit 555fda57e479672cde07d22622ce4d79d2292c19)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit f7aceb6ee9e33312a29360cafe1ca1d7e8ad1e57)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
QQuickWindow's data is backed by its content item's data and QQuickItem
does not support replace() because it's not actually a list.
Amends commit 7e1988539983531ecce589d76479f5bbe9bdb9b6.
Fixes: QTBUG-130856
Change-Id: I27dbf3666d9c40389ebf5b0259ee343868194c89
Reviewed-by: Semih Yavuz <semih.yavuz@qt.io>
Reviewed-by: Olivier De Cannière <olivier.decanniere@qt.io>
(cherry picked from commit e156157dddd7166bc3d367d1c262256351377056)
(cherry picked from commit 8f41e206856520671cc92e77b67c3ca42e03953b)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We need to set any initial properties before we call
componentComplete() and we should assign a context to the object even if
it's loaded from a C++-based type. It can be the engine's root context
in that case.
Amends commit fa0be265e4c6a8528778a41fdd376b26cb70db74.
[ChangeLog][QtQml] The QQmlParserStatus callbacks are invoked on objects
loaded using QQmlComponent::loadFromModule() at appropriate times now.
You can rely on any initial properties having been set before
componentComplete() is called and you can rely on the object having a
valid QML context.
Fixes: QTBUG-130867
Change-Id: I3485a4305a583ce3cab7d83d8305503025004f44
Reviewed-by: Olivier De Cannière <olivier.decanniere@qt.io>
(cherry picked from commit 595abf24a2c9d8a3679a2c6c4e941c0e301b8ea0)
(cherry picked from commit 3c162c592a815dd57405327888a2f27cc28ce498)
Reviewed-by: Semih Yavuz <semih.yavuz@qt.io>
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The patch e4a159632ec39542ec23567963191162f9dcdfef fixes propagating
mouse events by not allowing it to the underlying items beneath the
overlay.
It still can cause an issue when the menu is nested within the popup.
This is because the menu doesn't block the input, which allows the
overlay to pass on the events to the next child item.
This patch enables the menu to consume the mouse press event (as
similar to the drawer), further causing overlay not to pass on the
events to the other child items.
Fixes: QTBUG-130536
Change-Id: I1014c692a4a5aed22e096a79c06e27cb26fea70d
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
(cherry picked from commit 9fd43c27d19e675a0f5efdda4ea53fa97f61f852)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit a5a54c083bbe8506a2f16ab8a411d3c8689c31d6)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Fixes: QTBUG-130820
Change-Id: I5f1bba26024cc7f8d81b04147751f8e30feefc6c
Reviewed-by: Andreas Eliasson <andreas.eliasson@qt.io>
(cherry picked from commit 07ebdaf11dbb39a02b271501bf1a5a0f91991c5a)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit 3634ee55c1acf408008fde7d5481cf751cbd11e3)
|
| | | |
| | |
| | |
| | |
| | | |
Change-Id: I0658f1515e29b5f585b7ffa1b5366f74ff17150d
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
| | | |
| | |
| | |
| | |
| | | |
Change-Id: I5b46c45aefe744e2914c9bc931b0b006ffc994c6
Reviewed-by: Tarja Sundqvist <tarja.sundqvist@qt.io>
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
On macOS, readOnly/non-editable text controls don't accept tab
focus. This behavior is also respected in Qt since
c1d2bcff3dededa5b560713f4fd4874a023c43a2 .
Since this behavior is particular to macOS and not to other
platforms, in Qt we have tabFocusBehavior() in
qGuiApp->styleHints() which represents the system setting.
For all platforms other than macOS this always returns
Qt::TabFocusAllControls, which hints that all enabled controls
should receive tab focus no matter if editable or not. On
macOS if this true, all controls will accept tab focus, and if not,
it means that only editable text inputs and lists will.
The problem was that on macOS readOnly text edits were receivng
tab focus even if tabFocusBehaviour was not
Qt::TabFocusAllControls. This was because they have an
EditableText accessible role, which took precedence over their
editable status. To fix, if tabFocusBehaviour allows,
non-editable/readOnly properties should not receive tab focus no
matter the accessible role.
While at it, move the tabFocusBehaviour check inside
QQuickItem::canAcceptTabFocus.
Remove expect_fail in test covering case.
Note that this patch assumes that if tabFocusBehaviour ==
Qt::TabFocusAllControls readOnly text inputs will receive tab
focus on macOS too, even if this is never the case on a native
application: such inputs never get tab focus on Mac. We could
introduce a new enum value for tabFocusBehaviour that more
accurately depicts the readOnly text input focus behavior.
Change-Id: I098f75eb118b04f73dae3deec0c798f18870a202
Reviewed-by: Jan Arve Sæther <jan-arve.saether@qt.io>
Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io>
(cherry picked from commit aa7eb60a703cdc076115a45c2ac39e4965da2b87)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit 2a0e0fac0ff6672431d6b2e6dc5bc81d27e0ae85)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If the type loader thread is waiting for the main thread to process a
message, we cannot shut it down without waking it first. However, having
locked the mutex, we can detect this situation by exemining the mainSync
member. If that is set, wake the type loader thread one last time. It
will then have the opportunity to see the isShutdown flag we've just set
and dutifully shut itself down.
Amends commit 73b2e33d7854618b881aff9a8230cce24ce7d7f9
Fixes: QTBUG-128269
Change-Id: I8bf897010972de5e40e717846f3ff106e040dbe6
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
(cherry picked from commit 2296fad08d2d2db74e26bc7e5f339a21800f581a)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit 998641d0ea8a188238e07fa93744d3de33b4f43b)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The module QQuickItem belongs to is called "QtQuick", not only "Quick".
Amends commit 920745223d1c1ff401e3083327fcd88d8461ebc0.
Change-Id: Ifd7c1c50551793ecee7c620f9f8aac2a37a518cb
Reviewed-by: Olivier De Cannière <olivier.decanniere@qt.io>
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
(cherry picked from commit bb00c712833e2983d9367f7070bbff500d977fa4)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit cf126b32aa6f72d51a6e2a1d62de1a92cabd21fc)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If the user has disabled the rotation or scale axis, the target item's
rotation or scale property must not be set at all, to avoid breaking
bindings that were set differently.
Fixes: QTBUG-130517
Change-Id: I8f84f6845532f748bbdcc3af91a398d6659156ca
Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io>
(cherry picked from commit 49fbf2f86afa62b8c1c2be330620a0b310584a34)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit 6c9123f0933f476a2fd4a8bf4b9c01b36ff56d0f)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Add code snippet for how to supply source string templates to
Qt::qsTrId using /*% <string> */. The /begincomment and
/endcomment expand to /* and */, respectively.
Fixes: QTBUG-127794
Pick-to: 6.2
Change-Id: I84b77179892eea6dba2c8816b658916d665e718e
Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
(cherry picked from commit 00a4a181411cb1198a5a0f4fb6d40db2f6f787ed)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit 460b3d02e2aa9197c7132d8bdf70d18ccd025289)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
QQuickScreenInfo is created every time we access the Window's `screen`
property. See QQuickWindowQmlImpl::screen(). However, it didn't handle
any changes to the screen passed to the constructor. Therefore, any
bindings to the internal properties of the Window's screen didn't work
correctly either.
Fix this by calling setWrappedScreen() directly from the constructor
to ensure that we handle all changes to the wrapped platform's screen.
Fixes: QTBUG-130689
Change-Id: I92337169c12c2c294ee00af45f3885f53b5e6588
Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io>
(cherry picked from commit 00f58f2eca6bfcc66dcc79c249e51d2d34eb6a11)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit 9512dad108c22356708007fbb7f2eb285676df86)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
QAccessibleQuickWindow::text() was returning the window
title for all QAccessible::Text enum values, including
QAccessible::Accelerator. This caused Windows Narrator
to read the window title twice: once for Name and once
for Accelerator.
Fix this by returning the window title for QAccessible::Name
only.
Fixes: QTBUG-119530
Pick-to: 5.15
Change-Id: I3c51056670281158ef65dfebc83abe293bb20dd9
Reviewed-by: Jan Arve Sæther <jan-arve.saether@qt.io>
(cherry picked from commit 6ee7100b16fa7aa0902a1b8e89f8fbc03427aeb9)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit 6e99d7c3e06023a94a3c1392ce501478d161d148)
|
| | | |
| | |
| | |
| | |
| | | |
Change-Id: I22a84a73a43fa1d748268ef1004fced9cc69b6f1
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When running the minimal example from the bug report, the order of
events is:
1. deletables are iterated in QQuickRepeater::clear(), and deleteLater
is called on the delegate item.
2. deletables are unparented. This causes Container (SwipeView) to be
notified of the parent change and it removes the item. Part of this
involves changing the currentIndex, since the removed item was current.
3. SwipeView's contentItem (ListView) has its currentIndex bound to the
container's, so QQuickItemView::setCurrentIndex is called.
4. setCurrentIndex calls updateCurrent, which detects that the
currentIndex (which is -1, because there was only one item) is out of
range and so releases the item. This causes it to be added to
unrequestedItems, even though it has been scheduled for deletion.
This patch makes QQuickItemView detect that the item is going to be
deleted and not add it to the list of deletables.
Fixes: QTBUG-129622
Change-Id: I999aedbdfafc61ff6d33eb6579331f470e9c1454
Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io>
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
(cherry picked from commit 18a6a658aaf25fa8c380daef8a72dee4c1661164)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit 861a7921ed7833a90f77b5fca436c789a4f9517c)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
You can continue scrolling the main list with the mouse wheel even after
reaching the end of the nested list. When using a trackpad, behavior is
now the same.
Added tst_qquickflickable::nestedSameDirectionTrackpad.
nestedSameDirection.qml or the example from QTBUG-126514 is suitable
for manual testing.
Since we add a custom QPointingDevice to simulate a trackpad, use it in
nestedTrackpad() too, for better realism.
Fixes: QTBUG-124478
Change-Id: I9b9c9a41afcfa5d950093a31682013ae9e917f1a
Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
(cherry picked from commit 6d921e2d0ec6bec154ee03bbf70b882117bfcb2d)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit e1121fb1a072c2f2454addf1412390603580f553)
|
| | | |
| | |
| | |
| | |
| | | |
Change-Id: I2184ba8cd223ad4d937a7b4f37528743e88c6b3a
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This gives background information and a brief summary of why deferred
execution exists.
Change-Id: I991d9ffd175d781d286f855404b767d652fa6c84
Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io>
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
(cherry picked from commit 66008a31db41391aefe9436d1f5d15870457839b)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit 953a05bffcfa35b18982186f3a344c2ffc8c53f1)
|
| | | |
| | |
| | |
| | |
| | | |
Change-Id: I24aac766e8a3b3055e4a2560b9d075724c00c001
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- Replace mention of deprecated currentFile(s) with selectedFile(s).
- Mention currentFolder.
Change-Id: Ib7a414cba7a6f8e479159afc9ed50b014f93442c
Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
(cherry picked from commit 200d38a9b9561bba646bb8a61f8dc48b99ed6596)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit 17efc95bbffed2a2e132a9ddff490de626f938ac)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Paths can contain various interesting characters that need to be
specially encoded in URLs. Therefore, when funneling the path through
QUrl in order to normalize it, retrieve a path again in the end. Do not
just stringify the URL.
Amends commit e0400d08755bb40c303bbe330bc3bd6045436c22
Pick-to: 6.2
Fixes: QTBUG-129681
Change-Id: Ief49ce08acb3d346655abaf34278cf7c6afd107e
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
Reviewed-by: Olivier De Cannière <olivier.decanniere@qt.io>
(cherry picked from commit a24baed01a0f2cdda37f3eb9a406cb2fa94da4cb)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit ec00e10458f42c31b136b06ce14b29f81eafda0e)
|
| | | |
| | |
| | |
| | |
| | | |
Change-Id: I2fc89a774bcf4ebcb41a6c20348496eabf10ae80
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
While this makes no difference in practice, it was technically undefined
behavior before. You cannot call the object getter through the interface
of the context getter.
Amends commit 20d413aaac3e2edd8859b7325805d8fbd35d28e3.
Change-Id: Iab15d4b05a18aa1997e1e0a45aa9df19adf283df
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
Reviewed-by: Olivier De Cannière <olivier.decanniere@qt.io>
Reviewed-by: Sami Shalayel <sami.shalayel@qt.io>
(cherry picked from commit adc90d3c15f80011c8c737440ff8593c27b4a711)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit 1268040ce2d07b0e1d645f96dfceec57158bff51)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If we remove a value type binding from a proxy binding, the proxy
binding is still there. We must not clear the toplevel binding bit then.
Amends commit c9d7620bc2e47d3e1b84f824eb5b643f269f4a56
Pick-to: 6.2
Fixes: QTBUG-130143
Change-Id: Ie4f1ba4a22a1e15eaa218fb8e72f78964ae8cf75
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
(cherry picked from commit cdcfed60e12a0ba386287c8bdd96736c6a639b7a)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit e1cfc24d39b0e199f60e864c78dd7476f01d1cd1)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We must not delete a QQmlTypeData on the main thread since it interacts
with data on the type loader thread. If the type loader thread is still
alive, we have to drop any QQmlDataBlobs there. Otherwise the type
loader thread may crash when accessing a dangling pointer.
Pick-to: 6.2
Task-number: QTBUG-128269
Change-Id: If4cfbd40caef8cc8ac5d96f41dd08631170191c5
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
(cherry picked from commit 6396c5bf29cceab41f2adc211b1dec8b08eaa04e)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit 0a928061a0146a045e69287304c2832d26c8d5cd)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When these fail, we'll get more information in CI logs.
Task-number: QTBUG-118062
Task-number: QTBUG-123499
Change-Id: I90cdb466ca29bf955c45d3918be429e5d4d86d1b
Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
(cherry picked from commit 0acbcc1ad5beaea96505d38e80c03e5ceb1a7ae3)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit cf9e1d92d62b4dd45755fe05129b5a56f1909370)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Fixes: QTBUG-129850
Change-Id: I4a88b19672479a452facb0f1ca62e4fbb1d50203
Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io>
(cherry picked from commit 6ce0dc45d254f48ecb3957df772167ea41510eaf)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit 5b392593a18154a105122c7f72954455769fcf47)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
It was marked as internal but is necessary to implement a custom
ComboBox, as demonstrated by the customization docs.
Fixes: QTBUG-129759
Change-Id: Ieb53a49a022a1d237738217fc88dda7a630d31d2
Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io>
(cherry picked from commit 9ed04229a490b65d9cdf7b4b7af86b128e2b2499)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit 6dc017a82cc9c7d547bf4bc2d8ee1b981d5b4cdd)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
A follow-up of e4577eb6bb9308d2b84bfe66216333b001ac670b.
This ensures that the user won't inadvertently base the customizations
on top of the native styles.
Change-Id: Ibfeebfdb5ddad377947481deeb8de46976109daa
Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io>
(cherry picked from commit c71e8955f29a9e3778e1889e75f1a5aab611ecd0)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit 636fd5578ea0f9aa8ec7a9e52e4b559e55d934fd)
|