https://bugs.kde.org/show_bug.cgi?id=499637
--- Comment #13 from fhortner <fhort...@yahoo.de> --- (In reply to Marc Payne from comment #11) > Yes, the MouseArea is essentially being created underneath the mouse pointer > so the pointer is already deemed to have entered it. A QEvent::HoverEnter > event is fired as a result which I think is reasonable. The change in > QTBUG-127122 causes the HoverEnter handler to now emit the positionChanged > signal. In the case of the lock screen, the pointer hasn't actually moved > but usually a HoverEnter would be occurring as a result of pointer movement > and so a positionChanged signal makes sense, which I think was the point > being made in the Qt bug report. I'm not sure the Qt Company will be > particularly interested in complicating their code to deal with this edge > case. If this behavior had been in place from the start, KDE would have > needed to work around it anyway. The point being made in the QTBUG-127122 was, that the after actively moving of the mouse into the MouseArea for the first time, the positionChanged signal was not fired. The Mouse was moved from -1,-1 to 25,25, so it was positioned from outside the MouseArea into it upon movement. Have a look at the QDEBUG messages within the bug rebort: The onPositionChanged signal is missing for the first time. this is the kind of output I got ``` QDEBUG : MouseArea::test_mouse_move() qml: move to -1,-1 QDEBUG : MouseArea::test_mouse_move() qml: move to 25,25 QDEBUG : MouseArea::test_mouse_move() qml: onEntered QDEBUG : MouseArea::test_mouse_move() qml: move to 50,50 QDEBUG : MouseArea::test_mouse_move() qml: onPositionChanged 50 , 50 QDEBUG : MouseArea::test_mouse_move() qml: move to 100,100 QDEBUG : MouseArea::test_mouse_move() qml: onExited QDEBUG : MouseArea::test_mouse_move() qml: move to 150,150 QDEBUG : MouseArea::test_mouse_move() qml: onEntered QDEBUG : MouseArea::test_mouse_move() qml: move to 175,175 QDEBUG : MouseArea::test_mouse_move() qml: onPositionChanged 175 , 175 ``` -- You are receiving this mail because: You are watching all bug changes.
