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

@JLimbocker Tried your code but unfortunately it does not exactly what I want. It is selecting from the beginning instead of from where I was clicking when dragging.

Problem with passing the mouse event through to the TextField is that when I do that using mouse.accepted = false. The other handler like onRelease: are not called on the MouseArea anymore which destroys my handling there. The selectAll() could be switched off when something is already selected but I do not know why that TextField's selection is starting from the beginning...

Anyone knows how to forward the mouse events to an underlying element but still have the complete handling in the MouseArea available? That would solve my question.

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;
}

You're welcome !

Since the mystery is gone, please mark the thread as solved using the "Topic Tool" button so that other forum users may know a solution has been found :)

Hello @p3c0 thank you for helping. Unfortunately i did try as you suggested but no luck so far. Mouse wheel is not responding it just wok when i press and drag Don't know what could be the issue. I must check other files of my app maybe something is interfering with this file.

@dzimiwine Did you try acceptedButtons ?

acceptedButtons: Qt.MiddleButton : Qt.RightButton

@nnnnn Hmm. I overlooked your onEntered requirement. It doesnot work in my example. The problem is that once you set mouse.accepted=false the release event is not trapped.

I still had to remove the QWidget.. it's useless this way.
My error was that I can't have a QWidget class without a QQmlApplicationEngine.

This problem occurs in qt 5.4 under linux. I just checked, and it doesn't occur under 5.3 - there, onExit is correctly triggered even on drag-release outside the GridView.

@mcosta Actually, my problem is solved. Thanks to @t3685 for the solution. I've just forgot to mark it as SOLVED. Anyway, thanks ;)

@nedo99: A big thanks for the tip! That in fact solved my problem, but maybe not in the way you might have thought! I finally got it to work this way:

MouseArea { id: myMouseArea property point cursorPos property bool cursorPosActive : false // new code to handle flicking property point startFlickContentRef: Qt.point(0, 0) property point startFlickMousePos: Qt.point(mouseX, mouseY) property bool flicking: false function setStartFlickMousePos(x,y) { // "prepare" for flicking whenever we have a legitimate mouse pos... if (!flicking) // ...but are not actually flicking! startFlickMousePos = Qt.point(x,y) } function startFlick(refPt) { // Note: startFlick() might be called multiple times before endFlick() is called... if (!flicking) { // ...so this is an important check! startFlickContentRef = refPt flicking = true } } function endFlick(refPt) { if (flicking) { var diffX = refPt.x - startFlickContentRef.x var diffY = refPt.y - startFlickContentRef.y statBar.cursorPos = Qt.point(startFlickMousePos.x + diffX, startFlickMousePos.y + diffY) flicking = false } } anchors.fill: parent hoverEnabled: true onClicked: { // MouseEvent OK cursorPos = Qt.point(mouse.x, mouse.y) setStartFlickMousePos(mouse.x, mouse.y) } onEntered: { // here: mouseX/Y OK? cursorPos = Qt.point(mouseX, mouseY) setStartFlickMousePos(mouseX, mouseY) cursorPosActive = true } onExited: { cursorPosActive = false } onPositionChanged: { // MouseEvent OK cursorPos = Qt.point(mouse.x, mouse.y) setStartFlickMousePos(mouse.x, mouse.y) } onWheel: { // WheelEvent OK cursorPos = Qt.point(wheel.x, wheel.y) setStartFlickMousePos(wheel.x, wheel.y) wheel.accepted = false; // pass to Flickable } }

Then I added the following code to my Flickable:

onFlickStarted: { myMouseArea.startFlick(Qt.point(contentX, contentY)) } onFlickEnded: { myMouseArea.endFlick(Qt.point(contentX, contentY)) }

Note that it turned out to be important to use onFlickStarted/Ended instead of onMovementStarted/Ended. Also it's important to update the startFlickMousePos at every opportunity, because at the point where I normally would want to set it (in startFlick()), I might not have a valid mouseX and mouseY (that was the reason for this post in the first place!).

Again thanks! Together we are strong!

@shedo Hmm. Well then try to use the only relevant code from the blog post into your original code. The code of interest would be the one in onWheel handler and the properties it updates.

@maxsivkov

Scenario is to have several elements (images with attached mouseareas (to change image source when mouse is inside the image)
and also show hints (tooltips) for listview's item.

So its better no to do it when the ListView scrolls and only when user hovers mouse over that particular Item

To show tooltip my idea was to sit on a onPositionChanged event and restart timer, stop it in onExited event.

I think better to use onEntered and onExited. Using onPositionChanged will continuously restart it as mouse moves. Also hide it after a particular timeout instead of only in onExited.