Why does TouchArea is not in use anymore in QML ?
-
But way it doesn't replace the MouseArea in QML ?
-
Why should it replace it? MouseArea works perfectly with both mouse and touch events... if TA is really good, I'm fine with adding it, though, as an additional element.
-
Do you use TouchArea ?
-
[quote author="aabc" date="1340700912"]Do you use TouchArea ?[/quote]
-Yes, a lot :) Works also on Android with multitouch (well, MA + PinchArea).- Srx, I meant MouseArea. I do not use TouchArea.
-
And did you use MouseArea on a devices with resistive touch ?
-
Nope. I've tried it on my SGS2 only, and this guy comes with capacitative screen.
-
Did you try to work with QML elements like ListView on this touch device ?
-
Uh, am I being interviewed? xD
I think it was GridView in my case, but yes. Also works more or less ok (but one has to be careful with embedding other mouse areas inside and remember to set focus appropriately).
Anyway, you can take a look at the code here: "gitorious":https://gitorious.org/closecombatfree/closecombatfree/trees/master. I have ported it to Qt5 recently, so it won't work right now on Android. You can grab an older commit if you need it.
-
My problem is that I work with MouseArea and ListView on a resistive touch and I getting a lot of unwanted release events
-
Could be. I combine Flickables, GridViews and MouseAreas a lot in the linked projects, and sometimes there are problems, too. You can try filling a bug report if you have an easily-reproducible case.
