文章目录
前言
事件分发机制在Android体系中是相当重要的，在自定义View的时候可能需要考虑事件分发机制的影响。之前也看过别人写的文章，但是总感觉容易忘记，这里就对Android事件分发机制做一下浅析。
一.MotionEvent
MotionEvent是一个用于记录你接触屏幕后留下的一系列的事件。这些事件用的最多就是这几个ACTION_DOWN，ACTION_MOVE，ACTION_UP。下面罗列些比较常用的几个事件。
| 事件类型 | 具体动作 |
|---|---|
| ACTION_DOWN | 手指按下 |
| ACTION_MOVE | 手指滑动 |
| ACTION_UP | 手指抬起 |
| ACTION_CANCEL | 事件被拦截 |
| ACTION_OUTSIDE | 超出区域 |
一般的事件顺序是：
(1).ACTION_DOWN->ACTION_MOVE->ACTION_MOVE->-…->ACTION_UP
(2).ACTION_DOWN->ACTION_UP
对于ACTION_DOWN，ACTION_MOVE，ACTION_UP这些点击事件，大家其实已经很熟悉了。但是在看代码的时候，也会看到这两个事件ACTION_CANCEL 和 ACTION_OUTSIDE。通过MotionEvent详解这篇文章所述。
(1)ACTION_CANCEL：是只有上层 View 回收事件处理权的时候，ChildView 才会收到一个 ACTION_CANCEL 事件。
(2)ACTION_OUTSIDE：在特殊情况下，比如Dialog(没有占满屏幕大小的窗口)能够接收到视图区域外的事件。
二.事件分发
1.代码模型
在研究代码之前，先建立一个模型，先上代码。
xml代码：
<?xml version="1.0" encoding="utf-8"?>
<com.example.view.LayoutView1 xmlns:android="http://schemas.android.com/apk/res/android"
android:layout_width="match_parent"
android:layout_height="match_parent"
android:gravity="center"
android:background="@color/colorPrimary">
<com.example.view.LayoutView2
android:layout_width="350dp"
android:layout_height="350dp"
android:gravity="center"
android:background="@color/colorAccent">
<com.example.view.MyTextView
android:layout_width="200dp"
android:layout_height="200dp"
android:gravity="center"
android:background="@android:color/holo_green_dark" />
</com.example.view.LayoutView2>
</com.example.view.LayoutView1>
从xml来看LayoutView1在最外层，LayoutView2在中间一层，MyTextView在最里面一层。界面效果如下:
java代码：
// LayoutView1
public class LayoutView1 extends LinearLayout {
public LayoutView1(Context context) {
super(context);
}
public LayoutView1(Context context, AttributeSet attrs) {
super(context, attrs);
}
public LayoutView1(Context context, AttributeSet attrs, int defStyleAttr) {
super(context, attrs, defStyleAttr);
}
@Override
public boolean dispatchTouchEvent(MotionEvent ev) {
Log.e("test", "LayoutView1::dispatchTouchEvent!");
return super.dispatchTouchEvent(ev);
}
@Override
public boolean onInterceptTouchEvent(MotionEvent ev) {
Log.e("test", "LayoutView1::onInterceptTouchEvent!");
return false;
}
@Override
public boolean onTouchEvent(MotionEvent event) {
Log.e("test", "LayoutView1::onTouchEvent!");
return super.onTouchEvent(event);
}
}
// LayoutView2
public class LayoutView2 extends LinearLayout {
public LayoutView2(Context context) {
super(context);
}
public LayoutView2(Context context, AttributeSet attrs) {
super(context, attrs);
}
public LayoutView2(Context context, AttributeSet attrs, int defStyleAttr) {
super(context, attrs, defStyleAttr);
}
@Override
public boolean dispatchTouchEvent(MotionEvent ev) {
Log.e("test", "LayoutView2::dispatchTouchEvent!");
return super.dispatchTouchEvent(ev);
}
@Override
public boolean onInterceptTouchEvent(MotionEvent ev) {
Log.e("test", "LayoutView2::onInterceptTouchEvent!");
return false;
}
@Override
public boolean onTouchEvent(MotionEvent event) {
Log.e("test", "LayoutView2::onTouchEvent!");
return super.onTouchEvent(event);
}
}
// MyTextView
public class MyTextView extends TextView {
public MyTextView(Context context) {
super(context);
}
public MyTextView(Context context, AttributeSet attrs) {
super(context, attrs);
}
public MyTextView(Context context, AttributeSet attrs, int defStyleAttr) {
super(context, attrs, defStyleAttr);
}
@Override
public boolean dispatchTouchEvent(MotionEvent event) {
Log.e("test", "MyTextView::dispatchTouchEvent!");
return super.dispatchTouchEvent(event);
}
@Override
public boolean onTouchEvent(MotionEvent event) {
Log.e("test", "MyTextView::onTouchEvent!");
return true;
}
}
在LayoutView1，LayoutView2的onInterceptTouchEvent都返回false的时候：
在LayoutView1的onInterceptTouchEvent返回true，LayoutView2的onInterceptTouchEvent返回false的时候：
在LayoutView1的onInterceptTouchEvent返回false，LayoutView2的onInterceptTouchEvent返回true的时候：
等等。。。
还有其他的匹配选择，那么在这里总结下规律：
- 如果该ViewGroup的onInterceptTouchEvent()在接收到down事件处理完成之后return false，那么后续的move, up等事件将继续会先传递给该ViewGroup，之后才和down事件一样传递给最终的目标view的onTouchEvent()处理。
- 如果该ViewGroup的onInterceptTouchEvent()在接收到down事件处理完成之后return true，那么后续的move, up等事件将不再传递给onInterceptTouchEvent()，而是和down事件一样传递给该ViewGroup的onTouchEvent()处理，注意，目标view将接收不到任何事件。
- 如果最终需要处理事件的view的onTouchEvent()返回了false，那么该事件将被传递至其上一层次的view的onTouchEvent()处理。
- 如果最终需要处理事件的view 的onTouchEvent()返回了true，那么后续事件将可以继续传递给该view的onTouchEvent()处理。
该段引自onInterceptTouchEvent和onTouchEvent调用时序
2.代码分析
0x00.Activity
为了能够详细的了解事件分发的规律，下面对事件分发的代码做一个分析。
“事件分发”除了是事件分发是从最外层分发到最内层，还要经过Activity的dispatchTouchEvent方法做事件分发。
// Activity
public boolean dispatchTouchEvent(MotionEvent ev) {
if (ev.getAction() == MotionEvent.ACTION_DOWN) {
onUserInteraction();
}
// 重点代码
if (getWindow().superDispatchTouchEvent(ev)) {
return true;
}
return onTouchEvent(ev);
}
调用了Activity的dispatchTouchEvent方法后，再调用了PhoneWindow的superDispatchTouchEvent方法，这里的getWindow方法获取的就是PhoneWindow的实例。
// PhoneWindow
@Override
public boolean superDispatchTouchEvent(MotionEvent event) {
return mDecor.superDispatchTouchEvent(event);
}
又调用了DecorView的superDispatchTouchEvent方法，再来看看superDispatchTouchEvent方法。
public boolean superDispatchTouchEvent(MotionEvent event) {
return super.dispatchTouchEvent(event);
}
要知道DecorView的父类是ViewGroup，所以这里就是调用了ViewGroup的dispatchTouchEvent方法。至此我们开始进入ViewGroup类。
0x01.ViewGroup
下面可以通过dispatchTouchEvent代码可以大概归纳以下的一些分发流程。
1.是否分发事件
// 测试程序
if (mInputEventConsistencyVerifier != null) {
mInputEventConsistencyVerifier.onTouchEvent(ev, 1);
}
// 和Android的无障碍服务(AccessibilityService)有关
if (ev.isTargetAccessibilityFocus() && isAccessibilityFocusedViewOrHost()) {
ev.setTargetAccessibilityFocus(false);
}
boolean handled = false;
// 首先判断该View是否需要执行后面的分发逻辑
if (onFilterTouchEventForSecurity(ev)) {
final int action = ev.getAction();
final int actionMasked = action & MotionEvent.ACTION_MASK;
// 如果当前是ACTION_DOWN操作，就清除触摸操作的所有痕迹
if (actionMasked == MotionEvent.ACTION_DOWN) {
// 清除触摸操作的所有痕迹
cancelAndClearTouchTargets(ev);
resetTouchState();
}
这里主要的逻辑在于onFilterTouchEventForSecurity方法，该方法会判断是否需要执行下面的逻辑，也就是是否需要分发事件
onFilterTouchEventForSecurity代码：
// 依据安全策略，过滤触摸事件
public boolean onFilterTouchEventForSecurity(MotionEvent event) {
// 判断是否设置了被遮挡的时候是否处理触摸事件
// 判断当前的View是否被其他View遮挡
if ((mViewFlags & FILTER_TOUCHES_WHEN_OBSCURED) != 0
&& (event.getFlags() & MotionEvent.FLAG_WINDOW_IS_OBSCURED) != 0) {
// Window is obscured, drop this touch.
return false;
}
return true;
}
FILTER_TOUCHES_WHEN_OBSCURED：设置被遮挡时是否处理触摸事件，该变量可以通过android:filterTouchesWhenObscured来设置。
FLAG_WINDOW_IS_OBSCURED：该事件的窗口是否被其它窗口遮挡
由此可见，如果包含FILTER_TOUCHES_WHEN_OBSCURED和FLAG_WINDOW_IS_OBSCURED，则不会向下分发点击事件。
2.事件分发前清除标记
// ACTION_DOWN的时候清理TouchTargets和Touch状态
if (actionMasked == MotionEvent.ACTION_DOWN) {
// 清理上次事件的状态
cancelAndClearTouchTargets(ev);
// 重置ViewGroup的Touch状态
resetTouchState();
}
首先看下cancelAndClearTouchTargets方法：
private void cancelAndClearTouchTargets(MotionEvent event) {
// 判断mFirstTouchTarget是否为null
// 通过调试代码发现该View从Window中移除的时候mFirstTouchTarget为null
if (mFirstTouchTarget != null) {
boolean syntheticEvent = false;
// 判断event是否为null
if (event == null) {
// 人工包装一个ACTION_CANCEL的事件
final long now = SystemClock.uptimeMillis();
event = MotionEvent.obtain(now, now,
MotionEvent.ACTION_CANCEL, 0.0f, 0.0f, 0);
event.setSource(InputDevice.SOURCE_TOUCHSCREEN);
syntheticEvent = true;
}
// 遍历TouchTarget链表
for (TouchTarget target = mFirstTouchTarget; target != null; target = target.next) {
// 重置PFLAG_CANCEL_NEXT_UP_EVENT常量
// 该常量用于View在与ViewGroup解绑的时候起到标记作用
resetCancelNextUpFlag(target.child);
// 向子View分发ACTION_CANCEL事件
// cancel为true，所以无论是什么事件都会被置为ACTION_CANCEL事件
dispatchTransformedTouchEvent(event, true, target.child, target.pointerIdBits);
}
// 清空TouchTargets链表
clearTouchTargets();
// 释放MotionEvent
if (syntheticEvent) {
event.recycle();
}
}
}
private static boolean resetCancelNextUpFlag(@NonNull View view) {
// 首先判断是否包含PFLAG_CANCEL_NEXT_UP_EVENT，再重置该标记
if ((view.mPrivateFlags & PFLAG_CANCEL_NEXT_UP_EVENT) != 0) {
view.mPrivateFlags &= ~PFLAG_CANCEL_NEXT_UP_EVENT;
return true;
}
return false;
}
private void clearTouchTargets() {
// 遍历TouchTarget链表并释放链表资源
TouchTarget target = mFirstTouchTarget;
if (target != null) {
do {
TouchTarget next = target.next;
target.recycle();
target = next;
} while (target != null);
mFirstTouchTarget = null;
}
}
resetTouchState方法
private void resetTouchState() {
// 遍历TouchTarget链表并释放链表资源
clearTouchTargets();
// 重置该ViewGroup的PFLAG_CANCEL_NEXT_UP_EVENT标记
resetCancelNextUpFlag(this);
// 重置FLAG_DISALLOW_INTERCEPT
mGroupFlags &= ~FLAG_DISALLOW_INTERCEPT;
mNestedScrollAxes = SCROLL_AXIS_NONE;
}
关于TouchTarget mFirstTouchTarget变量
首先看下TouchTarget类
private static final class TouchTarget {
// ...省略代码
//子View
public View child;
//由该目标捕获的所有的手指的IDS 的结合位掩码
public int pointerIdBits;
//用于指向链表中的下一个TouchTarget
public TouchTarget next;
// ...省略代码
}
这个类最重要的是child变量和next变量，前者是被触摸的子View指针，后者则是指向下一个TouchTarget的地址，从这里可以看出把ViewGroup的子View和子View的信息封装成一个TouchTarget链表。mFirstTouchTarget通过字面意思也知道是链表的头，通过链表头可以遍历整个链表。
3.是否拦截Touch事件
// 是否拦截Touch事件
final boolean intercepted;
// ACTION_DOWN事件或者mFirstTouchTarget不为null
if (actionMasked == MotionEvent.ACTION_DOWN
|| mFirstTouchTarget != null) {
// disallowIntercept和requestDisallowInterceptTouchEvent有关
// 如果设置为true代表子View不希望父View拦截Touch事件
final boolean disallowIntercept = (mGroupFlags & FLAG_DISALLOW_INTERCEPT) != 0;
// disallowIntercept默认为false
// true的时候代表子View不希望父View拦截Touch事件
if (!disallowIntercept) {
// 调用自己的onInterceptTouchEvent，来决定是否拦截touch事件
intercepted = onInterceptTouchEvent(ev);
ev.setAction(action);
} else {
intercepted = false;
}
} else {
intercepted = true;
}
这段代码中一个重要的常量就是FLAG_DISALLOW_INTERCEPT，这个常量和requestDisallowInterceptTouchEvent方法有关。
requestDisallowInterceptTouchEvent代码：
@Override
public void requestDisallowInterceptTouchEvent(boolean disallowIntercept) {
if (disallowIntercept == ((mGroupFlags & FLAG_DISALLOW_INTERCEPT) != 0)) {
// We're already in this state, assume our ancestors are too
return;
}
if (disallowIntercept) {
mGroupFlags |= FLAG_DISALLOW_INTERCEPT;
} else {
mGroupFlags &= ~FLAG_DISALLOW_INTERCEPT;
}
// Pass it up to our parent
if (mParent != null) {
mParent.requestDisallowInterceptTouchEvent(disallowIntercept);
}
}
从代码可以看出disallowIntercept设置为true的时候mGroupFlags添加一个FLAG_DISALLOW_INTERCEPT常量。ViewGroup中的(mGroupFlags & FLAG_DISALLOW_INTERCEPT) != 0代码判断是否被设置了FLAG_DISALLOW_INTERCEPT，如果被设置了，那么intercepted为false，代表不去拦截Touch事件，同时向子View分发Touch事件。
4.拦截&分发
首先是关于事件取消的判断
// 包含PFLAG_CANCEL_NEXT_UP_EVENT或者ACTION_CANCEL
final boolean canceled = resetCancelNextUpFlag(this)
|| actionMasked == MotionEvent.ACTION_CANCEL;
// 是否包括PFLAG_CANCEL_NEXT_UP_EVENT
private static boolean resetCancelNextUpFlag(@NonNull View view) {
if ((view.mPrivateFlags & PFLAG_CANCEL_NEXT_UP_EVENT) != 0) {
view.mPrivateFlags &= ~PFLAG_CANCEL_NEXT_UP_EVENT;
return true;
}
return false;
}
接下来是分发事件
// 暂时不清楚
final boolean split = (mGroupFlags & FLAG_SPLIT_MOTION_EVENTS) != 0;
// TouchTarget链表
TouchTarget newTouchTarget = null;
// 判断事件是否被消费
boolean alreadyDispatchedToNewTouchTarget = false;
// 前面的canceled和intercepted已经说明
// canceled是否取消事件
// intercepted是否拦截
// canceled或者intercepted为false
if (!canceled && !intercepted) {
// Accessibility辅助功能
View childWithAccessibilityFocus = ev.isTargetAccessibilityFocus()
? findChildWithAccessibilityFocus() : null;
// ACTION_DOWN或者ACTION_POINTER_DOWN，ACTION_HOVER_MOVE
if (actionMasked == MotionEvent.ACTION_DOWN
|| (split && actionMasked == MotionEvent.ACTION_POINTER_DOWN)
|| actionMasked == MotionEvent.ACTION_HOVER_MOVE) {
// 获取当前触摸手指在多点触控中的排序
// 这个值可能因为有手指发生Down或Up而发生改变
final int actionIndex = ev.getActionIndex(); // always 0 for down
// 标识当前是那一个点的触摸事件
final int idBitsToAssign = split ? 1 <<
// 此时获取到手指的Id，这个值在Down到Up这个过程中是不会改变的
ev.getPointerId(actionIndex)
: TouchTarget.ALL_POINTER_IDS;
// Clean up earlier touch targets for this pointer id in case they
// 清理之前触摸事件中的目标
removePointersFromTouchTargets(idBitsToAssign);
// 子View的数量
final int childrenCount = mChildrenCount;
if (newTouchTarget == null && childrenCount != 0) {
// 通过actionIndex获取X,Y
final float x = ev.getX(actionIndex);
final float y = ev.getY(actionIndex);
// Find a child that can receive the event.
// Scan children from front to back.
final ArrayList<View> preorderedList = buildTouchDispatchChildList();
final boolean customOrder = preorderedList == null
&& isChildrenDrawingOrderEnabled();
// 所有子View组成的数组
final View[] children = mChildren;
// 遍历子View
for (int i = childrenCount - 1; i >= 0; i--) {
final int childIndex = getAndVerifyPreorderedIndex(
childrenCount, i, customOrder);
// 获取子View
final View child = getAndVerifyPreorderedView(
preorderedList, children, childIndex);
// 和Accessibility服务相关
if (childWithAccessibilityFocus != null) {
if (childWithAccessibilityFocus != child) {
continue;
}
childWithAccessibilityFocus = null;
i = childrenCount - 1;
}
if (!canViewReceivePointerEvents(child)
|| !isTransformedTouchPointInView(x, y, child, null)) {
ev.setTargetAccessibilityFocus(false);
continue;
}
newTouchTarget = getTouchTarget(child);
if (newTouchTarget != null) {
// Child is already receiving touch within its bounds.
// Give it the new pointer in addition to the ones it is handling.
newTouchTarget.pointerIdBits |= idBitsToAssign;
break;
}
// 判断是否包含PFLAG_CANCEL_NEXT_UP_EVENT,如果包含就去除该常量
resetCancelNextUpFlag(child);
// 分发事件，重要方法
if (dispatchTransformedTouchEvent(ev, false, child, idBitsToAssign)) {
// Child wants to receive touch within its bounds.
mLastTouchDownTime = ev.getDownTime();
if (preorderedList != null) {
// childIndex points into presorted list, find original index
for (int j = 0; j < childrenCount; j++) {
if (children[childIndex] == mChildren[j]) {
mLastTouchDownIndex = j;
break;
}
}
} else {
mLastTouchDownIndex = childIndex;
}
mLastTouchDownX = ev.getX();
mLastTouchDownY = ev.getY();
// 分发成功后封装一个TouchTarget同时添加到链表
newTouchTarget = addTouchTarget(child, idBitsToAssign);
// touch事件分发成功修改为true
alreadyDispatchedToNewTouchTarget = true;
break;
}
// The accessibility focus didn't handle the event, so clear
// the flag and do a normal dispatch to all children.
ev.setTargetAccessibilityFocus(false);
}
if (preorderedList != null) preorderedList.clear();
}
if (newTouchTarget == null && mFirstTouchTarget != null) {
// Did not find a child to receive the event.
// Assign the pointer to the least recently added target.
newTouchTarget = mFirstTouchTarget;
while (newTouchTarget.next != null) {
newTouchTarget = newTouchTarget.next;
}
newTouchTarget.pointerIdBits |= idBitsToAssign;
}
}
}
通过上面的代码可知道，如果不拦截touch事件，就去执行dispatchTransformedTouchEvent方法。现在我们看下dispatchTransformedTouchEvent方法。
private boolean dispatchTransformedTouchEvent(MotionEvent event, boolean cancel,
View child, int desiredPointerIdBits) {
final boolean handled;
// Canceling motions is a special case. We don't need to perform any transformations
// or filtering. The important part is the action, not the contents.
final int oldAction = event.getAction();
// 如果cancel为true，则进入下面的逻辑，分发所有的View一个cancel的touch事件
if (cancel || oldAction == MotionEvent.ACTION_CANCEL) {
event.setAction(MotionEvent.ACTION_CANCEL);
if (child == null) {
handled = super.dispatchTouchEvent(event);
} else {
handled = child.dispatchTouchEvent(event);
}
event.setAction(oldAction);
return handled;
}
// Calculate the number of pointers to deliver.
final int oldPointerIdBits = event.getPointerIdBits();
final int newPointerIdBits = oldPointerIdBits & desiredPointerIdBits;
// If for some reason we ended up in an inconsistent state where it looks like we
// might produce a motion event with no pointers in it, then drop the event.
if (newPointerIdBits == 0) {
return false;
}
// If the number of pointers is the same and we don't need to perform any fancy
// irreversible transformations, then we can reuse the motion event for this
// dispatch as long as we are careful to revert any changes we make.
// Otherwise we need to make a copy.
final MotionEvent transformedEvent;
if (newPointerIdBits == oldPointerIdBits) {
if (child == null || child.hasIdentityMatrix()) {
if (child == null) {
handled = super.dispatchTouchEvent(event);
} else {
final float offsetX = mScrollX - child.mLeft;
final float offsetY = mScrollY - child.mTop;
event.offsetLocation(offsetX, offsetY);
handled = child.dispatchTouchEvent(event);
event.offsetLocation(-offsetX, -offsetY);
}
return handled;
}
transformedEvent = MotionEvent.obtain(event);
} else {
transformedEvent = event.split(newPointerIdBits);
}
// Perform any necessary transformations and dispatch.
if (child == null) {
handled = super.dispatchTouchEvent(transformedEvent);
} else {
final float offsetX = mScrollX - child.mLeft;
final float offsetY = mScrollY - child.mTop;
transformedEvent.offsetLocation(offsetX, offsetY);
if (! child.hasIdentityMatrix()) {
transformedEvent.transform(child.getInverseMatrix());
}
handled = child.dispatchTouchEvent(transformedEvent);
}
// Done.
transformedEvent.recycle();
return handled;
}
这里的"cancel"为false
if (cancel || oldAction == MotionEvent.ACTION_CANCEL) {
event.setAction(MotionEvent.ACTION_CANCEL);
if (child == null) {
handled = super.dispatchTouchEvent(event);
} else {
handled = child.dispatchTouchEvent(event);
}
event.setAction(oldAction);
return handled;
}
那么会主要执行这段逻辑，判断childView不为null的情况下，调用childView的dispatchTouchEvent；如果为null，则调用父View的dispatchTouchEvent事件。
// Perform any necessary transformations and dispatch.
if (child == null) {// chlidView为null就执行ViewGroup父类View的dispatchTouchEvent
handled = super.dispatchTouchEvent(transformedEvent);
} else {
final float offsetX = mScrollX - child.mLeft;
final float offsetY = mScrollY - child.mTop;
transformedEvent.offsetLocation(offsetX, offsetY);
if (! child.hasIdentityMatrix()) {
transformedEvent.transform(child.getInverseMatrix());
}
// 调用childView的dispatchTouchEvent
handled = child.dispatchTouchEvent(transformedEvent);
}
总之，无论如何都会调用View的dispatchTouchEvent方法。接下来就会调用View的onTouchEvent方法。
0x02.View的dispatchTouchEvent
View里面的dispatchTouchEvent方法相对比较简单，代码如下：
public boolean dispatchTouchEvent(MotionEvent event) {
// Accessibility辅助功能相关
// If the event should be handled by accessibility focus first.
if (event.isTargetAccessibilityFocus()) {
// We don't have focus or no virtual descendant has it, do not handle the event.
if (!isAccessibilityFocusedViewOrHost()) {
return false;
}
// We have focus and got the event, then use normal event dispatch.
event.setTargetAccessibilityFocus(false);
}
boolean result = false;
if (mInputEventConsistencyVerifier != null) {
mInputEventConsistencyVerifier.onTouchEvent(event, 0);
}
final int actionMasked = event.getActionMasked();
if (actionMasked == MotionEvent.ACTION_DOWN) {
// Defensive cleanup for new gesture
stopNestedScroll();
}
// 和ViewGroup的onFilterTouchEventForSecurity的作用一样，可以参考前面的分析
if (onFilterTouchEventForSecurity(event)) {
if ((mViewFlags & ENABLED_MASK) == ENABLED && handleScrollBarDragging(event)) {
result = true;
}
// =====================重要的核心代码=====================
//noinspection SimplifiableIfStatement
ListenerInfo li = mListenerInfo;
if (li != null && li.mOnTouchListener != null
&& (mViewFlags & ENABLED_MASK) == ENABLED
&& li.mOnTouchListener.onTouch(this, event)) {
result = true;
}
if (!result && onTouchEvent(event)) {
result = true;
}
}
// =====================重要的核心代码=====================
if (!result && mInputEventConsistencyVerifier != null) {
mInputEventConsistencyVerifier.onUnhandledEvent(event, 0);
}
// 和嵌套滚动有关
// Clean up after nested scrolls if this is the end of a gesture;
// also cancel it if we tried an ACTION_DOWN but we didn't want the rest
// of the gesture.
if (actionMasked == MotionEvent.ACTION_UP ||
actionMasked == MotionEvent.ACTION_CANCEL ||
(actionMasked == MotionEvent.ACTION_DOWN && !result)) {
stopNestedScroll();
}
return result;
}
重点看下面的代码：
// 和ViewGroup的onFilterTouchEventForSecurity的作用一样，可以参考前面的分析
if (onFilterTouchEventForSecurity(event)) {
if ((mViewFlags & ENABLED_MASK) == ENABLED && handleScrollBarDragging(event)) {
result = true;
}
//noinspection SimplifiableIfStatement
ListenerInfo li = mListenerInfo;
if (li != null && li.mOnTouchListener != null
&& (mViewFlags & ENABLED_MASK) == ENABLED
&& li.mOnTouchListener.onTouch(this, event)) {
result = true;
}
if (!result && onTouchEvent(event)) {
result = true;
}
}
注意到li.mOnTouchListener.onTouch(this, event)代码，从这段代码可以看出，如果要执行View的onTouchEvent方法，需要保证复写的onTouch接口返回值为false(事件未被消费，向下传递)，这样才可以调用View的onTouchEvent方法。那么接下来就进入到onTouchEvent方法中。
0x03.View的onTouchEvent
public boolean onTouchEvent(MotionEvent event) {
final float x = event.getX();
final float y = event.getY();
final int viewFlags = mViewFlags;
final int action = event.getAction();
// 判断是否有CLICKABLE，LONG_CLICKABLE，CONTEXT_CLICKABLE事件
final boolean clickable = ((viewFlags & CLICKABLE) == CLICKABLE
|| (viewFlags & LONG_CLICKABLE) == LONG_CLICKABLE)
|| (viewFlags & CONTEXT_CLICKABLE) == CONTEXT_CLICKABLE;
if ((viewFlags & ENABLED_MASK) == DISABLED) {
if (action == MotionEvent.ACTION_UP && (mPrivateFlags & PFLAG_PRESSED) != 0) {
setPressed(false);
}
mPrivateFlags3 &= ~PFLAG3_FINGER_DOWN;
// A disabled view that is clickable still consumes the touch
// events, it just doesn't respond to them.
return clickable;
}
// 和TouchDelegate相关的，该类可以用来扩大View的点击区域
if (mTouchDelegate != null) {
if (mTouchDelegate.onTouchEvent(event)) {
return true;
}
}
// 用来判断ACTION_UP，ACTION_DOWN，ACTION_CANCEL，ACTION_MOVE相关的touch事件
if (clickable || (viewFlags & TOOLTIP) == TOOLTIP) {
switch (action) {
case MotionEvent.ACTION_UP:
mPrivateFlags3 &= ~PFLAG3_FINGER_DOWN;
if ((viewFlags & TOOLTIP) == TOOLTIP) {
handleTooltipUp();
}
if (!clickable) {
removeTapCallback();
removeLongPressCallback();
mInContextButtonPress = false;
mHasPerformedLongPress = false;
mIgnoreNextUpEvent = false;
break;
}
boolean prepressed = (mPrivateFlags & PFLAG_PREPRESSED) != 0;
if ((mPrivateFlags & PFLAG_PRESSED) != 0 || prepressed) {
// take focus if we don't have it already and we should in
// touch mode.
boolean focusTaken = false;
if (isFocusable() && isFocusableInTouchMode() && !isFocused()) {
focusTaken = requestFocus();
}
if (prepressed) {
// The button is being released before we actually
// showed it as pressed. Make it show the pressed
// state now (before scheduling the click) to ensure
// the user sees it.
setPressed(true, x, y);
}
if (!mHasPerformedLongPress && !mIgnoreNextUpEvent) {
// This is a tap, so remove the longpress check
removeLongPressCallback();
// Only perform take click actions if we were in the pressed state
if (!focusTaken) {
// Use a Runnable and post this rather than calling
// performClick directly. This lets other visual state
// of the view update before click actions start.
if (mPerformClick == null) {
mPerformClick = new PerformClick();
}
// 核心代码
if (!post(mPerformClick)) {
performClickInternal();
}
// 核心代码
}
}
if (mUnsetPressedState == null) {
mUnsetPressedState = new UnsetPressedState();
}
if (prepressed) {
postDelayed(mUnsetPressedState,
ViewConfiguration.getPressedStateDuration());
} else if (!post(mUnsetPressedState)) {
// If the post failed, unpress right now
mUnsetPressedState.run();
}
removeTapCallback();
}
mIgnoreNextUpEvent = false;
break;
case MotionEvent.ACTION_DOWN:
if (event.getSource() == InputDevice.SOURCE_TOUCHSCREEN) {
mPrivateFlags3 |= PFLAG3_FINGER_DOWN;
}
mHasPerformedLongPress = false;
if (!clickable) {
checkForLongClick(0, x, y);
break;
}
if (performButtonActionOnTouchDown(event)) {
break;
}
// Walk up the hierarchy to determine if we're inside a scrolling container.
boolean isInScrollingContainer = isInScrollingContainer();
// For views inside a scrolling container, delay the pressed feedback for
// a short period in case this is a scroll.
if (isInScrollingContainer) {
mPrivateFlags |= PFLAG_PREPRESSED;
if (mPendingCheckForTap == null) {
mPendingCheckForTap = new CheckForTap();
}
mPendingCheckForTap.x = event.getX();
mPendingCheckForTap.y = event.getY();
postDelayed(mPendingCheckForTap, ViewConfiguration.getTapTimeout());
} else {
// Not inside a scrolling container, so show the feedback right away
setPressed(true, x, y);
checkForLongClick(0, x, y);
}
break;
case MotionEvent.ACTION_CANCEL:
if (clickable) {
setPressed(false);
}
removeTapCallback();
removeLongPressCallback();
mInContextButtonPress = false;
mHasPerformedLongPress = false;
mIgnoreNextUpEvent = false;
mPrivateFlags3 &= ~PFLAG3_FINGER_DOWN;
break;
case MotionEvent.ACTION_MOVE:
if (clickable) {
drawableHotspotChanged(x, y);
}
// Be lenient about moving outside of buttons
if (!pointInView(x, y, mTouchSlop)) {
// Outside button
// Remove any future long press/tap checks
removeTapCallback();
removeLongPressCallback();
if ((mPrivateFlags & PFLAG_PRESSED) != 0) {
setPressed(false);
}
mPrivateFlags3 &= ~PFLAG3_FINGER_DOWN;
}
break;
}
return true;
}
return false;
}
注：TouchDelegate相关的可以参考我写的文章：TouchDelegate的用法
这里重点看ACTION_UP事件中的performClickInternal相关代码
private boolean performClickInternal() {
// Must notify autofill manager before performing the click actions to avoid scenarios where
// the app has a click listener that changes the state of views the autofill service might
// be interested on.
notifyAutofillManagerOnClick();
return performClick();
}
再进入到performClick方法，performClick方法代码如下：
public boolean performClick() {
// We still need to call this method to handle the cases where performClick() was called
// externally, instead of through performClickInternal()
notifyAutofillManagerOnClick();
final boolean result;
final ListenerInfo li = mListenerInfo;
if (li != null && li.mOnClickListener != null) {
playSoundEffect(SoundEffectConstants.CLICK);
// 这里调用了onClick回调方法
li.mOnClickListener.onClick(this);
result = true;
} else {
result = false;
}
sendAccessibilityEvent(AccessibilityEvent.TYPE_VIEW_CLICKED);
notifyEnterOrExitForAutoFillIfNeeded(true);
return result;
}
综上，通过代码可以知道在执行ACTION_UP后调用OnClickListener的onClick回调函数，由此可知，整个调用onClick回调的流程如下：
onTouch->onTouchEvent->onClick
至此对于整个事件分发流程的简单分下告一段落了，如果有什么纰漏的，欢迎在评论区留言！
参考文章：
你不能错过的View事件分发机制分析
onInterceptTouchEvent和onTouchEvent调用时序
Android Touch事件学习系列汇总
你还在被触摸事件困扰吗？看看这篇吧
触摸事件的分发（ViewGroup篇之一）
944
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
