diff options
author | Mitch Curtis <mitch.curtis@qt.io> | 2022-08-19 12:01:56 +0800 |
---|---|---|
committer | Mitch Curtis <mitch.curtis@qt.io> | 2022-09-02 15:09:32 +0800 |
commit | 56acab014d490951f14e6719b7bd535146646fc7 (patch) | |
tree | 35d4ac8de618392d6d4dab246c554deb97749f3b /src/imports/controls/qquickdefaultbusyindicator_p.h | |
parent | e6d7494b64325614a3de77296a60f0769f59bc15 (diff) |
Fix scroll bars not showing up when binding to standalone contentItem
908aa77d16e00f2bccc0ddae0f8b61955c56a6a1 hid old scroll bars, but
didn't account for the situation where the old scroll bars would be put
back into place, and so they never showed up.
In the case of the linked bug report, since there was a binding to the
ScrollView's contentItem, a default Flickable would be created. After
that binding was evaluated, the contentItem was set, causing the scroll
bars to be hidden (as part of the process of disconnecting from the old
flickable). To fix the issue, we now do the reverse of hideOldItem when
a new contentItem is set.
Fixes: QTBUG-104983
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
Reviewed-by: Nate Graham
(cherry picked from commit 58bae53237417f28eac6d772fa6ecab657f8a73f)
Change-Id: I0d5d04cf9268e03b99c8b8fba2eee407e225ae56
Diffstat (limited to 'src/imports/controls/qquickdefaultbusyindicator_p.h')
0 files changed, 0 insertions, 0 deletions