Nice, note that TapHandler has a doubleTapped signal.

I v solve this problem： insert this 2 line code in main.cpp before create QGuiApplication object: qputenv("QSG_RENDER_LOOP", "basic" ); QQuickWindow::setGraphicsApi(QSGRendererInterface::OpenGL);

@jeremy_k said in onPressAndHold not working with Qt.TapAndHoldGesture: TextArea takes focus when it receives a press, rather than a click. That's a good idea. I've tried playing around with focus, however it seems no matter how I set it, that doesn't change objects funcionality.

@viliak hi and welcome to devnet, I think you should check and maybe create a ticket on the bug tracker since it's a pretty big change of behavior.

This is already fixed in 6.2.3, and 6.3

@GrecKo said in MouseArea - The very painful way of events propagation: Why are you adding MouseArea on top of clickable or scrollable items? Sorry to reply to an old post but this thread got resurrected and this caught my eye. In my case I have a MouseArea on TreeView, which is clickable and scrollable. As I recall (bearing in mind it was some time ago now) it seemed to be the only way to implement a context menu popup when right clicking tree branches. Is there something different I could have done? (This is the old TreeView BTW - I haven't looked closely at the new one in Qt 6 to see if that is any different.)

Finally I searched a while by myself, and I think I may answer my own question. Although I couldn't completely resolve my issue, I noticed that the answer is hidden in the other MouseArea events. For example, by handling the onPressed event and adding the mouse.accepted in several key locations, I could let the component take care of the scrolling when the left mouse button is pressed, whereas the right click opens a popup menu. My conclusion is that there is no ready-to-use way, i.e there is no parameter to activate in the MouseArea itself which may resolve this kind of issue, and the solution is a good balance between activating different parameters in the different functions.

Thank you, it works!

I finally succeed to create this using 2 MultiPointTouchArea but I had to write drag function on touchUpdated event. Here is my code for one drag area: import QtQuick 2.0 Item{ id: joystick width: 100 height: 500 Rectangle{ id: joystickPad height: 50 width: 100 MultiPointTouchArea{ property var offset: null anchors.fill:parent minimumTouchPoints: 1 maximumTouchPoints: 1 function dragMove(point) { if (point) { var position = joystick.mapFromItem(joystickPad, point.x, point.y); /* Change y axis */ if((position.y - offset.y) < 0) { /* Do not go on top of drag area */ joystickPad.y = 0; } else { if((position.y - offset.y) > (joystick.height-joystickPad.height)) { /* Do not go below of drag area */ joystickPad.y = (joystick.height-joystickPad.height); } else { joystickPad.y = position.y - offset.y; } } } } onPressed: { var point = touchPoints[0]; offset = Qt.point(point.x, point.y); } onTouchUpdated: { var point = touchPoints[0]; dragMove(point); } onReleased: { //Reset position joystickPad.x = (joystick.width/2 - joystickPad.width/2) joystickPad.y = (joystick.height/2 - joystickPad.height/2) } } } }

Thanks for your input jpnurmi! Yes I'm using 5.8 and 5.9 beta is fixing this issue! Thanks for pointing it out! For some reason I didn't find this bug! Best, nx

@hvoigt got the same issue

I just stumbled accros the same odd behavior with Qt 5.7.1. However, the strange thing is, that it seems to be only a problem on android (on windows it's fine). Does anybody know if that's a (already reported) bug?

In my understanding this is exact what onClicked does. From the online documentation: "A click is defined as a press followed by a release, both inside the MouseArea (pressing, moving outside the MouseArea, and then moving back inside and releasing is also considered a click)." MouseArea { anchors.fill: parent onClicked: console.log("released") onPressed: console.log("pressed") }

@kafanti If MouseArea handles mouse event it doesn't pass event to its parent. You need: onPressed: { mouse.accepted = false; }