这篇View的事件分发机制,仅限于自己学习的笔记,有不正确的地方望指正。
所谓的点击事件的事件分发,其实就是对MotionEvent的事件的分发过程,即当一个MotionEvent产生之后,系统就需要把这个事件传递给一个具体的View,而这传递过程就是事件的分发过程。
1.点击事件的传递规则
public boolean dispatchTouchEvent(MotionEvent ev)
用来进行事件的分发,如果事件能够传递给当前的View,那么此方法一定会被调用,返回结果受当前View的onTouchEvent和下级的dispatchTouchEvent方法的影响,表示是否消耗掉当前事件。
public boolean onInterceptTouchEvent(MotionEvent ev)
在上述方法中调用,用来判断是否拦截事件,如果当前View拦截了某个事件,那么在同一事件序列中,此方法不会被再次调用,返回结果表示是否拦截当前事件。
public boolean onTouchEvent(MotionEvent event)
在dispatchTouchEvent方法中调用,用来处理点击事件,返回结果表示是否消耗当前事件,如果不消耗,则在同一事件序列中,当前View无法再次接受到事件
上面的关系可以简单用下面的伪代码理解
public boolean dispatchTouchEvent(MotionEvent ev){
boolean intercepted;
if(onTnterceptTouchEvent(ev)){
intercepted=onTonchEvent(ev);
}else{
intercepted=child.dispatchTouchEvent(ev);
}
return intercepted;
}
点击事件的传递规则:
- 对于一个根ViewGroup来说,点击事件产生后,首先会传递给它,这是它的dispatchTouchEvent方法会被调用,如果这个ViewGroup的onTnterceptTouchEvent方法返回true就表示它要拦截当前事件,接着事件会交给这个ViewGroup处理,即它的onTonchEvent方法会执行,如果onTnterceptTouchEvent返回为false就表示它不拦截事件,及传递给它的子元素,接着子元素的dispatchTouchEvent方法调用,如此反复执行直到事件被最终处理。
当 一个View需要处理事件时,如果它设置了OnTouchListener,那么OnTouchListener中的onTouch方法会被回调。这时事件如何处理要看onTouch的返回值,如果返回false则当前的View的onTonchEvent方法会被调用;如果返回为true那么onTonchEvent方法不会执行。由此可见给View设置的OnTouchListener其优先级比onTonchEvent要高。在onTonchEvent方法中,如果当前设置了OnClickListener,其优先级是最低的,即处于事件传递的底端。
- 点击事件产生,它的传递过程遵循如下顺序:
Activity==>Window==>View
即事件总是先传递给Activity,Activity再传递给Window,最后Window再传递给顶级View。顶级View接受到事件后,就会按照事件分发机制去分发事件。考虑一种情况:如果view的onTonchEvent返回false,那么他的父容器的onTonchEvent将会调用,依次类推,如果所有的元素都不处理这个事件,那么这个事件将会最终传递给Activity处理。即Activity的onTonchEvent方法会被调用。
- 点击事件产生,它的传递过程遵循如下顺序:
关于事件传递的机制,总结如下:
- 同一个事件序列是从手指接触屏幕那一刻起,到手指离开屏幕的那一刻结束,在这个过程中所产生的一系列事件,这个事件是从Down开始中间会有很多Move到Up结束.
- 正常情况下,一个事件序列只能被一个View拦截且消耗。
- 某个View一旦决定拦截,那么这个事件序列都只能由它处理(如果事件序列能够传递给他的话),并且它的onTnterceptTouchEvent不会再调用
- 某个View一旦开始处理事件,如果它不消耗ACCTION_DOWN事件(onTonchEvent返回false),那么同一事件的序列中的其他事件都不会交给它再来处理,并且将事件重新交给它的父元素来处理,即父元素的onTonchEvent将被执行。
- 如果View不消耗除ACTION_DOWN以外的其他事件,那么这个点击事件将会消失,此时父元素的onTonchEvent也不会调用,并且当前可以接受的后续的事件,最终这些消失的点击事件交给Activity来处理
- ViewGroup默认是不拦截任何事件,源码中默认返回的false
- View没有onTnterceptTouchEvent方法,一旦有点击事件传递给它,那么它的onTonchEvent方法将会被调用。
- View的onTonchEvent默认都会消耗掉事件(返回为true),除非它是不可点击的
- View的enable属性不影响onTonchEvent的默认返回值
- View会发生的前提是当前View是可点击的,并且它收到了down和up的事件
- 事件传递过程是由外向内的,及时间总是先传递给父元素,然后再由父元素分发给子View,通过requestDisallowInterceptTouchEvent方法可以在子元素中干预父元素的事件分发过程,但是ACTTION_DOWN事件除外。
2.事件分发的源码解析
Activity对点击事件的分发过程
点击事件用MotionEvent来表示,当一个点击事件操作发生,事件最先传递给当前的Activity,由Activity的dispatchTouchEvent来进行事件委派。具体的工作由Activity内部的Window来完成
public boolean dispatchTouchEvent(MotionEvent ev) {
if (ev.getAction() == MotionEvent.ACTION_DOWN) {
onUserInteraction();
}
if (getWindow().superDispatchTouchEvent(ev)) {
return true;
}
return onTouchEvent(ev);
}
事件首先交给Activity所附属的window进行分发,如果返回true,则整个循坏就结束了,返回false则意味着没人处理,所有的View的onTouchEvent都返回false,则Activity的onTouchEvent会被调用。
点击事件到达顶级View(一般是ViewGroup)以后,会调用ViewGroup的dispatchTouchEvent方法,然后逻辑是这样的:如果顶级ViewGroup拦截事件即
onTnterceptTouchEvent返回true,则事件由ViewGroup处理,这时如果ViewGroup的OnTouchListener被设置,则onTouch会被调用,否则onTonchEvent会被调用。也就是说如果都提供的话,onTouch会屏蔽掉onTonchEvent,在onTonchEvent事件中,如果设置了OnClickListener,则onClick会被调用。如果顶级ViewGroup不拦截事件,则事件会传递给它所在的 点击事件链上的子View,这时子元素的dispatchTouchEvent会被调用。到此为止,事件已经从顶级的View传递给了下一层View,接下来的传递过程和顶级View是一致。如此循换,完成整个事件的分发。
// Check for interception.
final boolean intercepted;
if (actionMasked == MotionEvent.ACTION_DOWN
|| mFirstTouchTarget != null) {
final boolean disallowIntercept = (mGroupFlags & FLAG_DISALLOW_INTERCEPT) != 0;
if (!disallowIntercept) {
intercepted = onInterceptTouchEvent(ev);
ev.setAction(action); // restore action in case it was changed
} else {
intercepted = false;
}
} else {
// There are no touch targets and this action is not an initial down
// so this view group continues to intercept touches.
intercepted = true;
}
从上述的代码ViewGroup在两种情况下,判断是否要拦截当前事件类型
:分别为ACTION_DOWN和mFirstTouchTarget!=null;
ACTION_DOWN 是指点击事件按下的事件类型
mFirstTouchTarget!=null 是指当ViewGroup的子元素成功处理,换种方式来理解,当ViewGroup不拦截事件并将事件交给子元素处理时,mFirstTouchTarget!=null成立,反过来一旦ViewGroup拦截事件则mFirstTouchTarget!=null不成立。那么当(actionMasked == MotionEvent.ACTION_DOWN || mFirstTouchTarget != null)这个条件为false,将会导致ViewGroup的onInterceptTouchEvent不会被调用,并且同一序列中的其他事件都会默认交给它处理。
当然,特殊情况那就是FLAG_DISALLOW_INTERCEPT标记为,这个标记为是通过requestDisallowInterceptTouchEvent方法来设置的,一般用于子View中。FLAG_DISALLOW_INTERCEPT一旦设置,ViewGroup将无法拦截除了ACTION_DOWN以外的其他的点击事件。因为ViewGroup在事件分发时,如果是ACTION_DOWN将会重置FLAG_DISALLOW_INTERCEPT,导致设置无效
// Handle an initial down.
if (actionMasked == MotionEvent.ACTION_DOWN) {
// Throw away all previous state when starting a new touch gesture.
// The framework may have dropped the up or cancel event for the previous gesture
// due to an app switch, ANR, or some other state change.
cancelAndClearTouchTargets(ev);
resetTouchState();
}
根据源码总结两点:
1.onInterceptTouchEvent不是每次事件都会调用,如果我们提前处理所有的点击事件,要选择dispatchTouchEvent方法,只有这个方法确保每次调用,前期是事件能够传递到当前的ViewGroup
2.使用FLAG_DISALLOW_INTERCEPT解决滑动冲突。
当ViewGroup不拦截事件时候,事件将会传递给子元素进行处理 。
final View[] children = mChildren;
for (int i = childrenCount - 1; i >= 0; i--) {
final int childIndex = getAndVerifyPreorderedIndex(
childrenCount, i, customOrder);
final View child = getAndVerifyPreorderedView(
preorderedList, children, childIndex);
// If there is a view that has accessibility focus we want it
// to get the event first and if not handled we will perform a
// normal dispatch. We may do a double iteration but this is
// safer given the timeframe.
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;
}
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();
newTouchTarget = addTouchTarget(child, idBitsToAssign);
alreadyDispatchedToNewTouchTarget = true;
break;
}
}
首先遍历ViewGrop的所有的子View,然后判断子元素是否能够接收到点击事件。是否能够接收到点击事件的权限:子元素是否在播放动画,点击事件的坐标是否在该View的区域内。如果某个元素满足这两个条件,那么事件就会传递给它来处理.可以看到dispatchTransformedTouchEvent实际是调用子元素的dispatchTouchEvent方法,只要child不为null就调用子元素的dispatchTouchEvent。
if (child == null) {
handled = super.dispatchTouchEvent(event);
} else {
handled = child.dispatchTouchEvent(event);
}
如果dispatchTouchEvent返回true,这是就不用考虑了事件在子元素内部是怎么分发的。如果返回false则将把事件传递给下级子元素。
那么mFirstTouchTarget在哪里赋值呢
newTouchTarget = addTouchTarget(child, idBitsToAssign);
alreadyDispatchedToNewTouchTarget = true;
break;
private TouchTarget addTouchTarget(@NonNull View child, int pointerIdBits) {
final TouchTarget target = TouchTarget.obtain(child, pointerIdBits);
target.next = mFirstTouchTarget;
mFirstTouchTarget = target;
return target;
}
mFirstTouchTarget 是否被赋值,则直接影响到ViewGroup对事件的拦截策略,如果为Null则会交给View处理事件。
// Dispatch to touch targets.
if (mFirstTouchTarget == null) {
// No touch targets so treat this as an ordinary view.
handled = dispatchTransformedTouchEvent(ev, canceled, null,
TouchTarget.ALL_POINTER_IDS);
}
但mFirstTouchTarget 为null可以看见传递的第三个参数为null。这里也就转到的View的dispatchTouchEvent,则事件交给View来处理。
3.View对点击事件的处理过程
直接来代码分析吧
public boolean dispatchTouchEvent(MotionEvent event) {
// 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();
}
===》 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;
}
View是一个单独的元素,没有元素,则遇到事件自己去处理。可以看出View的点击事件处理的机制是先判断有没有mOnTouchListener ,如果设置了mOnTouchListener的onTouch返回值为true,则onTouchEvent就不执行。由此可见mOnTouchListener 的优先级高于onTouchEvent。
接着看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();
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;
}
if (mTouchDelegate != null) {
if (mTouchDelegate.onTouchEvent(event)) {
return true;
}
}
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)) {
performClick();
}
}
}
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;
}
可以看到View的CLICKABLE和LONG_CLICKABLE有一个为true,那么就代表onTouchEvent消耗掉该事件。即onTouchEvent返回值为true.
默认View是不可点击的,而CLICKABLE是和具体的View有关系。可以用过设置改变它们的属性。
public void setOnClickListener(@Nullable OnClickListener l) {
if (!isClickable()) {
setClickable(true);
}
getListenerInfo().mOnClickListener = l;
}
设置setOnClickListener会将CLICKABLE设置为 true.
参考:Android开发艺术探讨