写这个博客还有点费事，本来用有道笔记写的，复制过来字体有问题，算了，再重新温习一笔吧，昨天早上在看View的事件分发机制源码过程中对dispatchTouchEvent这个方法无法研究透彻，《Android开发艺术探索》这书讲的还是不错，但还是有几个地方有点模糊，好在最后参考了一下别人的博客弄明白了，高兴啊，这种心情大家也深有体会，下面就仔细讲一下ViewGroup中对事件分发的一个流程：
这里不说事件是怎么传递到顶级View的，研究的是顶级View分发给子View，不要搞混了，顶级View 也就是viewGroup,事件传到这个类时首先会调用dispatchTouchEvent这个类去判断是什么事件，我们看源码：
这里不说事件是怎么传递到顶级View的，研究的是顶级View分发给子View，不要搞混了，顶级View 也就是viewGroup,事件传到这个类时首先会调用dispatchTouchEvent这个类去判断是什么事件，我们看源码：
@Override
public boolean dispatchTouchEvent(MotionEvent ev) {
if (mInputEventConsistencyVerifier != null) {
mInputEventConsistencyVerifier.onTouchEvent(ev, 1);
}
......
// 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();
}
......
// 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;
}
......
首先所有点击事件都是以ACTION_DOWN开始，然后多个ACTION_MOVE，最后以ACTION_UP结束，第二个if中，判断是不是ACTION_DOWN，是的话在cancelAndClearTouchTargets方法最终会使mFirstTouchTarget==null，见 cancelAndClearTouchTargets方法体；紧接着由于是DOWN事件，进入第三个if中，这里有个boolean变量intercepted，它表示ViewGroup是否拦截事件，但是我们发现onInterceptTouchEvent这个方法默认返回false，即ViewGroup默认不拦截任何事件：
再回到dispatchTouchEvent方法中，如果mFirstTouchTarget==null，看代码：
这么说来如果mFirstTouchTarget 指向了子View，即mFirstTouchTarget！= null，接下来的同一事件序列都会分发给子View处理，看代码：
总结一下，ViewGroup默认是把事件分发给子View的，除非重写ViewGroup的onInterceptTouchEvent方法，并设置FLAG_DISALLOW_INTERCEPT这个标志位，那么一开始MOVE和UP事件都会被ViewGroup拦截，这个在滑动冲突中经常使用；子View处理过一个事件后，此后同一事件序列的其他事件不用去询问是否拦截，直接交给子View处理；如果DOWN事件没有子View 处理，那么以后的事件都由ViewGroup处理，ViewGroup不处理的话再由Activity处理，即上分发处理，这个流程如下：
public boolean onInterceptTouchEvent(MotionEvent ev) {
return false;
} if (!canceled && !intercepted) {
........
if (actionMasked == MotionEvent.ACTION_DOWN
|| (split && actionMasked == MotionEvent.ACTION_POINTER_DOWN)
|| actionMasked == MotionEvent.ACTION_HOVER_MOVE) {
......
final int childrenCount = mChildrenCount;
if (newTouchTarget == null && childrenCount != 0) {
.............
for (int i = childrenCount - 1; i >= 0; i--) {
final int childIndex = customOrder
? getChildDrawingOrder(childrenCount, i) : i;
final View child = (preorderedList == null)
? children[childIndex] : preorderedList.get(childIndex);
......
if (dispatchTransformedTouchEvent(ev, false, child, idBitsToAssign)) {
............
newTouchTarget = addTouchTarget(child, idBitsToAssign);
alreadyDispatchedToNewTouchTarget = true;
break;
}
......
}
进入if的条件为不是CANCEL事件并且没有拦截事件，里面 if (actionMasked == MotionEvent.ACTION_DOWN，所以DOWN事件进入这个if，这个if中对子View进行了倒序遍历，接着if(dispatchTransformedTouchEvent......中调用了dispatchTouchEvent这个方法：
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();
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;
} private TouchTarget addTouchTarget(View child, int pointerIdBits) {
TouchTarget target = TouchTarget.obtain(child, pointerIdBits);
target.next = mFirstTouchTarget;
mFirstTouchTarget = target;
return target;
} public boolean onTouchEvent(MotionEvent event) {
......
if ((viewFlags & ENABLED_MASK) == DISABLED) {
if (event.getAction() == MotionEvent.ACTION_UP && (mPrivateFlags & PFLAG_PRESSED) != 0) {
setPressed(false);
}
// A disabled view that is clickable still consumes the touch
// events, it just doesn't respond to them.
return (((viewFlags & CLICKABLE ) == CLICKABLE || (viewFlags & LONG_CLICKABLE) == LONG_CLICKABLE));
}
if (((viewFlags & CLICKABLE) == CLICKABLE || (viewFlags & LONG_CLICKABLE) == LONG_CLICKABLE)) {
switch (event.getAction()) {
case MotionEvent.ACTION_UP:
......
if (!mHasPerformedLongPress) {
// 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();
}
}
}
......
再回到dispatchTouchEvent方法中，如果mFirstTouchTarget==null，看代码：
if (mFirstTouchTarget == null) {
// No touch targets so treat this as an ordinary view.
handled = dispatchTransformedTouchEvent(ev, canceled, null,
TouchTarget.ALL_POINTER_IDS);
}
传给dispatchTransformedTouchEvent的第三个参数为null，就是child为null，很明显还是交给ViewGroup处理。到这里，才明白了为什么前面要actionMasked == MotionEvent.ACTION_DOWN || mFirstTouchTarget != null这两个条件，因为DOWN一定会分发给子View，如果子View没有消耗掉DOWN事件，mFirstTouchTarget = null，由ViewGroup来处理，下一个MOVE或UP事件来到时intercepted = true，不再分发给子View处理；相反，如果子View消耗掉DOWN事件，下一个MOVE或UP事件来到时进入 if (actionMasked == MotionEvent.ACTION_DOWN || mFirstTouchTarget != null)中，这里面要说到FLAG_DISALLOW_INTERCEPT这个标志位，它是由子View的requestDisallowInterceptEvent来设置的，默认表示不允许拦截事件，设置允许拦截后只对DWON事件以外的事件起作用，因为DOWN事件会引发重置所有标志位，但是ViewGroup不允许拦截子View处理过的事件除了ACTION_DOWN，这是因为前面说过onInterceptTouchEven这个方法默认返回false，所以这个标志位在源码中被弃用了，但是这并不妨碍我们在重写ViewGroup的时候重新用它来处理滑动冲突的问题，所以说这个标志位还是很重要的。
if (mFirstTouchTarget == null) {
............
} else {
TouchTarget predecessor = null;
TouchTarget target = mFirstTouchTarget;
while (target != null) {
final TouchTarget next = target.next;
if (alreadyDispatchedToNewTouchTarget && target == newTouchTarget) {
handled = true;
} else {
final boolean cancelChild = resetCancelNextUpFlag(target.child)
|| intercepted;
if (dispatchTransformedTouchEvent(ev, cancelChild,
target.child, target.pointerIdBits)) {
handled = true;
}
if (cancelChild) {
if (predecessor == null) {
mFirstTouchTarget = next;
} else {
predecessor.next = next;
}
target.recycle();
target = next;
continue;
}
}
predecessor = target;
target = next;
}
}总结一下，ViewGroup默认是把事件分发给子View的，除非重写ViewGroup的onInterceptTouchEvent方法，并设置FLAG_DISALLOW_INTERCEPT这个标志位，那么一开始MOVE和UP事件都会被ViewGroup拦截，这个在滑动冲突中经常使用；子View处理过一个事件后，此后同一事件序列的其他事件不用去询问是否拦截，直接交给子View处理；如果DOWN事件没有子View 处理，那么以后的事件都由ViewGroup处理，ViewGroup不处理的话再由Activity处理，即上分发处理，这个流程如下：
6305
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
