Guang Zhu
authored
Last attempt to fix ACTION_MOVE ended up breaking stuff elsewhere. For a touch based gesture, it usually have a group of motion events, and typically they have the same down time and individual event times. Example: a tap should have ACTION_DOWN with same down time and event time, and subsequent ACTION_UP should have the same down time as previous one, but a fresh event time. Similar situation applies to ACTION_DOWN, ACTION_MOVEs, ACTION_UP sequence of a drag/scroll/fling gesture In addition, a 5ms delay is added for a tap between DOWN and UP. And a 5ms delay is added for each injected event in a drag gesture Change-Id: I8e65e578152b1c1ff1fa4c0f476ef45806826479
Name | Last commit | Last update |
---|---|---|
apps | ||
build | ||
cmds/monkey | ||
data/etc | ||
docs | ||
host | ||
ide | ||
libraries/stereocamera | ||
ndk | ||
pdk | ||
samples | ||
scripts | ||
sdk | ||
sdk_overlay | ||
testrunner | ||
tools | ||
tutorials/NotepadCodeLab | ||
.gitignore | ||
CleanSpec.mk |