d934fd7f54
With nested popup widgets, pressing a mouse button on the lower popup will close the active popup. MouseMove events that are generated before the button is released again should not have that button included, as it is likely to result in incorrect state handling in the widget. This change removes all buttons from the MouseMove event, which is the second best option. This is mostly consistent with the behavior when closing a popup and no other popup remains. The widget underneath will get MouseMove events without the respective button included. This change doesn't include a fix for the final release event, which should ideally also not be delivered to the remaining popup, as it never got a corresponding press event. Qt has already reset the states in which it stores which widget received the press event at the time the release is generated, such as qt_button_down and qt_popup_down. So we can't separate a release grabbed by a newly opened popup (which we want) from a release to the popup that became active after closing (which we don't want). However, widgets can more easily work around this issue, and the risk of breaking things by changing the code further becomes too high. Change-Id: I603bbdbc7e7355952d96ab77c5e2d2f1e6f94987 Fixes: QTBUG-82538 Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io> Reviewed-by: Gatis Paeglis <gatis.paeglis@qt.io> |
||
|---|---|---|
| .. | ||
| accessible | ||
| dialogs | ||
| doc | ||
| effects | ||
| graphicsview | ||
| itemviews | ||
| kernel | ||
| statemachine | ||
| styles | ||
| util | ||
| widgets | ||
| Qt5WidgetsConfigExtras.cmake.in | ||
| Qt5WidgetsMacros.cmake | ||
| QtWidgets.dynlist | ||
| configure.json | ||
| configure.pri | ||
| qtwidgets.tracepoints | ||
| widgets.pro | ||