summaryrefslogtreecommitdiff
path: root/tools/aapt2/diff/Diff.cpp
diff options
context:
space:
mode:
authorVadim Tryshev <vadimt@google.com>2016-09-15 16:19:15 -0700
committerVadim Tryshev <vadimt@google.com>2016-09-16 11:20:16 -0700
commit1edc6daf1d13ec472da2aae2a2a88d130c495cb7 (patch)
tree50712e5b15e1a405fcb0db6674c6b2318473bf5c /tools/aapt2/diff/Diff.cpp
parentb2e0ed87722ff975cb2974d8ab25f17a4f2ae4b3 (diff)
Eliminating the “black hole” effect with location/drop events.
Currently, a container view that doesn’t accept events, but has a child that accepts events, prevents its parent from receiving LOCATION/DROP events while the drag is over the container (but not the child). This is a bug. With this fix, such a container will prevent the parent from invoking a (second) LOCATION/DROP event only if the event was really delivered to any of its descendants. To know whether the event was delivered, I added DragEvent.mEventHandlerWasCalled member. EXITED/ENTERED events are now generated upon delivery of the event that has coordinates in it. Current view that has drag focus is now global to reflect the fact that it’s one per process. Bug: 31469490 Change-Id: I248e8d1de87b7734853136eb4719f7571cea91d5
Diffstat (limited to 'tools/aapt2/diff/Diff.cpp')
0 files changed, 0 insertions, 0 deletions