summaryrefslogtreecommitdiffstats
path: root/src/3rdparty/wasm/qt_attribution.json
diff options
context:
space:
mode:
authorVolker Hilsheimer <volker.hilsheimer@qt.io>2021-10-24 14:31:33 +0200
committerVolker Hilsheimer <volker.hilsheimer@qt.io>2021-11-05 16:54:55 +0100
commit02164b292f002b051f34a88871145415fad94f32 (patch)
tree8e94447ef374b1fba3774455009d998ce496e270 /src/3rdparty/wasm/qt_attribution.json
parentc5409964b0c627b25131c73f95794314feb51b5d (diff)
Don't use QCursor::pos in QTabBar and fix hover handling
Relying on QCursor::pos makes tests fragile and prevents multi-seat support. Instead, record the mouse position in the already existing event handling, and use that instead. Styles might use either WA_Hover or enable mouse tracking for the widget to enable hover-effects, so we need to support both. Fix the scenario where a newly inserted tab ends up under the mouse, which was previously not handled correctly (only the case of removing a tab was). Clean up the repaint management when the hovered tab changes; just call update on the old rect, and then later update on the new rect; there's no need to make a copy first, updates are posted and compressed. Add a unit test that makes sure that we paint tabs that should be under the mouse in the hovered state. Since not all styles enable hovering and/or mouse tracking in all cases, use a style sheet for those styles that don't. Change-Id: I7cdbb18e9e04b52651e273680fec87b50cb81e05 Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org> Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io> Reviewed-by: Jan Arve Sæther <jan-arve.saether@qt.io>
Diffstat (limited to 'src/3rdparty/wasm/qt_attribution.json')
0 files changed, 0 insertions, 0 deletions