Details
-
Task
-
Resolution: Done
-
P2: Important
-
None
-
None
Description
One idea is to look at velocity (if you hit the screen "running" then you meant to flick, otherwise if you hit a button it could be pressed already); but we need a few touch movements to calculate velocity, so this still would tend to impose a delay. And in the other case, where you press and hold your finger very still, if there is only the press event, we would need to wait some time anyway, to detect that it's not moving.
Anyway pressDelay is existing API so we need to ensure that it's OK to use pressDelay on Flickable or ListView while delegates inside are using Pointer Handlers.
It needs an autotest, of course.