Details
-
Bug
-
Resolution: Done
-
P2: Important
-
5.15.9, 6.3.0
-
61a9612f5b (qt/qtdeclarative/dev) 61a9612f5b (qt/tqtc-qtdeclarative/dev)
Description
Seems that there is a difference in event delivery logic for mouse and touch. If parent of MouseArea is disabled in onPressed handler, the pressed state is remains active. When later enabled again, the MouseArea does not respond to clicks anymore.
This works fine with touch event though. And also if MouseArea itself is being disabled instead of its parent.
To reproduce:
- run attached example
- click upper blue rectangle
-> it remains yellow - click lower blue rectangle to enable it
-> does not respond to clicks anymore, unless double clicked first
Attachments
Issue Links
- duplicates
-
QTBUG-39806 MouseArea press is not canceled when enabled becomes false
-
- Closed
-
- relates to
-
QTBUG-38364 MouseArea doesn't propagate the disabled state to children
-
- Open
-
-
QTBUG-74987 [REG 5.11->5.12] Setting visible=false in MouseArea.onPressed is broken
-
- Closed
-
-
QTBUG-69696 Mousearea forwards events when disabled
-
- Reported
-
-
QTBUG-15798 Non-enabled MouseArea consumes events it usually pass on
-
- Closed
-
-
QTBUG-29783 onPositionChanged signal keeps coming when MouseArea enabled is set to false in onPressed.
-
- Closed
-
For Gerrit Dashboard: QTBUG-103788 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
438881,7 | MouseArea: don't get stuck in pressed state when disabling in press | dev | qt/qtdeclarative | Status: MERGED | +2 | 0 |