`
lxq_xsyu
  • 浏览: 65438 次
  • 性别: Icon_minigender_1
  • 来自: 西安
文章分类
社区版块
存档分类
最新评论

Android源码分析-点击事件派发机制

阅读更多
转载请注明出处:http://blog.csdn.net/singwhatiwanna/article/details/17339857

概述

一直想写篇关于Android事件派发机制的文章,却一直没写,这两天刚好是周末,有时间了,想想写一篇吧,不然总是只停留在会用的层次上但是无法了解其内部机制。我用的是4.4源码,打开看看,挺复杂的,尤其是事件是怎么从Activity派发出来的,太费解了。了解Windows消息机制的人会发现,觉得Android的事件派发机制和Windows的消息派发机制挺像的,其实这是一种典型的消息“冒泡”机制,很多平台采用这个机制,消息最先到达最底层View,然后它先进行判断是不是它所需要的,否则就将消息传递给它的子View,这样一来,消息就从水底的气泡一样向上浮了一点距离,以此类推,气泡达到顶部和空气接触,破了(消息被处理了),当然也有气泡浮出到顶层了,还没破(消息无人处理),这个消息将由系统来处理,对于Android来说,会由Activity来处理。

Android点击事件的派发机制

1. 从Activity传递到底层View

点击事件用MotionEvent来表示,当一个点击操作发生时,事件最先传递给当前Activity,由Activity的dispatchTouchEvent来进行事件派发,具体的工作是由Activity内部的Window来完成的,Window会将事件传递给decor view,decor view一般就是当前界面的底层容器(即setContentView所设置的View),通过Activity.getWindow.getDecorView()可以获得。另外,看下面代码的的时候,主要看我注释的地方,代码很多很复杂,我无法一一说明,但是我注释的地方都是关键点,是博主仔细读代码总结出来的。

源码解读:

事件是由哪里传递给Activity的,这个我还不清楚,但是不要紧,我们从activity开始分析,已经足够我们了解它的内部实现了。

Code:Activity#dispatchTouchEvent

  1. /**
  2. *Calledtoprocesstouchscreenevents.Youcanoverridethisto
  3. *interceptalltouchscreeneventsbeforetheyaredispatchedtothe
  4. *window.Besuretocallthisimplementationfortouchscreenevents
  5. *thatshouldbehandlednormally.
  6. *
  7. *@paramevThetouchscreenevent.
  8. *
  9. *@returnbooleanReturntrueifthiseventwasconsumed.
  10. */
  11. publicbooleandispatchTouchEvent(MotionEventev){
  12. if(ev.getAction()==MotionEvent.ACTION_DOWN){
  13. //这个函数其实是个空函数,啥也没干,如果你没重写的话,不用关心
  14. onUserInteraction();
  15. }
  16. //这里事件开始交给Activity所附属的Window进行派发,如果返回true,整个事件循环就结束了
  17. //返回false意味着事件没人处理,所有人的onTouchEvent都返回了false,那么Activity就要来做最后的收场。
  18. if(getWindow().superDispatchTouchEvent(ev)){
  19. returntrue;
  20. }
  21. //这里,Activity来收场了,Activity的onTouchEvent被调用
  22. returnonTouchEvent(ev);
  23. }

Window是如何将事件传递给ViewGroup的

Code:Window#superDispatchTouchEvent

  1. /**
  2. *Usedbycustomwindows,suchasDialog,topassthetouchscreenevent
  3. *furtherdowntheviewhierarchy.Applicationdevelopersshould
  4. *notneedtoimplementorcallthis.
  5. *
  6. */
  7. publicabstractbooleansuperDispatchTouchEvent(MotionEventevent);
这竟然是一个抽象函数,还注明了应用开发者不要实现它或者调用它,这是什么情况?再看看如下类的说明,大意是说:这个类可以控制顶级View的外观和行为策略,而且还说这个类的唯一一个实现位于android.policy.PhoneWindow,当你要实例化这个Window类的时候,你并不知道它的细节,因为这个类会被重构,只有一个工厂方法可以使用。好吧,还是很模糊啊,不太懂,不过我们可以看一下android.policy.PhoneWindow这个类,尽管实例化的时候此类会被重构,但是重构而已,功能是类似的。

Abstract base class for a top-level window look and behavior policy. An instance of this class should be used as the top-level view added to the window manager. It provides standard UI policies such as a background, title area, default key processing, etc.

The only existing implementation of this abstract class is android.policy.PhoneWindow, which you should instantiate when needing a Window. Eventually that class will be refactored and a factory method added for creating Window instances without knowing about a particular implementation.

Code:PhoneWindow#superDispatchTouchEvent
  1. @Override
  2. publicbooleansuperDispatchTouchEvent(MotionEventevent){
  3. returnmDecor.superDispatchTouchEvent(event);
  4. }
这个逻辑很清晰了,PhoneWindow将事件传递给DecorView了,这个DecorView是啥呢,请看下面

  1. privatefinalclassDecorViewextendsFrameLayoutimplementsRootViewSurfaceTaker
  2. //Thisisthetop-levelviewofthewindow,containingthewindowdecor.
  3. privateDecorViewmDecor;
  4. @Override
  5. publicfinalViewgetDecorView(){
  6. if(mDecor==null){
  7. installDecor();
  8. }
  9. returnmDecor;
  10. }

顺便说一下,平时Window用的最多的就是((ViewGroup)getWindow().getDecorView().findViewById(android.R.id.content)).getChildAt(0)即通过Activity来得到内部的View。这个mDecor显然就是getWindow().getDecorView()返回的View,而我们通过setContentView设置的View是它的一个子View。目前事件传递到了DecorView 这里,由于DecorView 继承自FrameLayout且是我们的父View,所以最终事件会传递给我们的View,原因先不管了,换句话来说,事件肯定会传递到我们的View,不然我们的应用如何响应点击事件呢。不过这不是我们的重点,重点是事件到了我们的View以后应该如何传递,这是对我们更有用的。从这里开始,事件已经传递到我们的顶级View了,注意:顶级View实际上是最底层View,也叫根View。

2.底层View对事件的分发过程

点击事件到底层View(一般是一个ViewGroup)以后,会调用ViewGroup的dispatchTouchEvent方法,然后的逻辑是这样的:如果底层ViewGroup拦截事件即onInterceptTouchEvent返回true,则事件由ViewGroup处理,这个时候,如果ViewGroup的mOnTouchListener被设置,则会onTouch会被调用,否则,onTouchEvent会被调用,也就是说,如果都提供的话,onTouch会屏蔽掉onTouchEvent。在onTouchEvent中,如果设置了mOnClickListener,则onClick会被调用。如果顶层ViewGroup不拦截事件,则事件会传递给它的在点击事件链上的子View,这个时候,子View的dispatchTouchEvent会被调用,到此为止,事件已经从最底层View传递给了上一层View,接下来的行为和其底层View一致,如此循环,完成整个事件派发。另外要说明的是,ViewGroup默认是不拦截点击事件的,其onInterceptTouchEvent返回false。

源码解读:

Code:ViewGroup#dispatchTouchEvent

  1. @Override
  2. publicbooleandispatchTouchEvent(MotionEventev){
  3. if(mInputEventConsistencyVerifier!=null){
  4. mInputEventConsistencyVerifier.onTouchEvent(ev,1);
  5. }
  6. booleanhandled=false;
  7. if(onFilterTouchEventForSecurity(ev)){
  8. finalintaction=ev.getAction();
  9. finalintactionMasked=action&MotionEvent.ACTION_MASK;
  10. //Handleaninitialdown.
  11. if(actionMasked==MotionEvent.ACTION_DOWN){
  12. //Throwawayallpreviousstatewhenstartinganewtouchgesture.
  13. //Theframeworkmayhavedroppedtheuporcanceleventforthepreviousgesture
  14. //duetoanappswitch,ANR,orsomeotherstatechange.
  15. cancelAndClearTouchTargets(ev);
  16. resetTouchState();
  17. }
  18. //Checkforinterception.
  19. finalbooleanintercepted;
  20. if(actionMasked==MotionEvent.ACTION_DOWN
  21. ||mFirstTouchTarget!=null){
  22. finalbooleandisallowIntercept=(mGroupFlags&FLAG_DISALLOW_INTERCEPT)!=0;
  23. if(!disallowIntercept){
  24. //这里判断是否拦截点击事件,如果拦截,则intercepted=true
  25. intercepted=onInterceptTouchEvent(ev);
  26. ev.setAction(action);//restoreactionincaseitwaschanged
  27. }else{
  28. intercepted=false;
  29. }
  30. }else{
  31. //Therearenotouchtargetsandthisactionisnotaninitialdown
  32. //sothisviewgroupcontinuestointercepttouches.
  33. intercepted=true;
  34. }
  35. //Checkforcancelation.
  36. finalbooleancanceled=resetCancelNextUpFlag(this)
  37. ||actionMasked==MotionEvent.ACTION_CANCEL;
  38. //Updatelistoftouchtargetsforpointerdown,ifneeded.
  39. finalbooleansplit=(mGroupFlags&FLAG_SPLIT_MOTION_EVENTS)!=0;
  40. TouchTargetnewTouchTarget=null;
  41. booleanalreadyDispatchedToNewTouchTarget=false;
  42. //这里面一大堆是派发事件到子View,如果intercepted是true,则直接跳过
  43. if(!canceled&&!intercepted){
  44. if(actionMasked==MotionEvent.ACTION_DOWN
  45. ||(split&&actionMasked==MotionEvent.ACTION_POINTER_DOWN)
  46. ||actionMasked==MotionEvent.ACTION_HOVER_MOVE){
  47. finalintactionIndex=ev.getActionIndex();//always0fordown
  48. finalintidBitsToAssign=split?1<<ev.getPointerId(actionIndex)
  49. :TouchTarget.ALL_POINTER_IDS;
  50. //Cleanupearliertouchtargetsforthispointeridincasethey
  51. //havebecomeoutofsync.
  52. removePointersFromTouchTargets(idBitsToAssign);
  53. finalintchildrenCount=mChildrenCount;
  54. if(newTouchTarget==null&&childrenCount!=0){
  55. finalfloatx=ev.getX(actionIndex);
  56. finalfloaty=ev.getY(actionIndex);
  57. //Findachildthatcanreceivetheevent.
  58. //Scanchildrenfromfronttoback.
  59. finalView[]children=mChildren;
  60. finalbooleancustomOrder=isChildrenDrawingOrderEnabled();
  61. for(inti=childrenCount-1;i>=0;i--){
  62. finalintchildIndex=customOrder?
  63. getChildDrawingOrder(childrenCount,i):i;
  64. finalViewchild=children[childIndex];
  65. if(!canViewReceivePointerEvents(child)
  66. ||!isTransformedTouchPointInView(x,y,child,null)){
  67. continue;
  68. }
  69. newTouchTarget=getTouchTarget(child);
  70. if(newTouchTarget!=null){
  71. //Childisalreadyreceivingtouchwithinitsbounds.
  72. //Giveitthenewpointerinadditiontotheonesitishandling.
  73. newTouchTarget.pointerIdBits|=idBitsToAssign;
  74. break;
  75. }
  76. resetCancelNextUpFlag(child);
  77. if(dispatchTransformedTouchEvent(ev,false,child,idBitsToAssign)){
  78. //Childwantstoreceivetouchwithinitsbounds.
  79. mLastTouchDownTime=ev.getDownTime();
  80. mLastTouchDownIndex=childIndex;
  81. mLastTouchDownX=ev.getX();
  82. mLastTouchDownY=ev.getY();
  83. //注意下面两句,如果有子View处理了点击事件,则newTouchTarget会被赋值,
  84. //同时alreadyDispatchedToNewTouchTarget也会为true,这两个变量是直接影响下面的代码逻辑的。
  85. newTouchTarget=addTouchTarget(child,idBitsToAssign);
  86. alreadyDispatchedToNewTouchTarget=true;
  87. break;
  88. }
  89. }
  90. }
  91. if(newTouchTarget==null&&mFirstTouchTarget!=null){
  92. //Didnotfindachildtoreceivetheevent.
  93. //Assignthepointertotheleastrecentlyaddedtarget.
  94. newTouchTarget=mFirstTouchTarget;
  95. while(newTouchTarget.next!=null){
  96. newTouchTarget=newTouchTarget.next;
  97. }
  98. newTouchTarget.pointerIdBits|=idBitsToAssign;
  99. }
  100. }
  101. }
  102. //Dispatchtotouchtargets.
  103. //这里如果当前ViewGroup拦截了事件,或者其子View的onTouchEvent都返回了false,则事件会由ViewGroup处理
  104. if(mFirstTouchTarget==null){
  105. //Notouchtargetssotreatthisasanordinaryview.
  106. //这里就是ViewGroup对点击事件的处理
  107. handled=dispatchTransformedTouchEvent(ev,canceled,null,
  108. TouchTarget.ALL_POINTER_IDS);
  109. }else{
  110. //Dispatchtotouchtargets,excludingthenewtouchtargetifwealready
  111. //dispatchedtoit.Canceltouchtargetsifnecessary.
  112. TouchTargetpredecessor=null;
  113. TouchTargettarget=mFirstTouchTarget;
  114. while(target!=null){
  115. finalTouchTargetnext=target.next;
  116. if(alreadyDispatchedToNewTouchTarget&&target==newTouchTarget){
  117. handled=true;
  118. }else{
  119. finalbooleancancelChild=resetCancelNextUpFlag(target.child)
  120. ||intercepted;
  121. if(dispatchTransformedTouchEvent(ev,cancelChild,
  122. target.child,target.pointerIdBits)){
  123. handled=true;
  124. }
  125. if(cancelChild){
  126. if(predecessor==null){
  127. mFirstTouchTarget=next;
  128. }else{
  129. predecessor.next=next;
  130. }
  131. target.recycle();
  132. target=next;
  133. continue;
  134. }
  135. }
  136. predecessor=target;
  137. target=next;
  138. }
  139. }
  140. //Updatelistoftouchtargetsforpointeruporcancel,ifneeded.
  141. if(canceled
  142. ||actionMasked==MotionEvent.ACTION_UP
  143. ||actionMasked==MotionEvent.ACTION_HOVER_MOVE){
  144. resetTouchState();
  145. }elseif(split&&actionMasked==MotionEvent.ACTION_POINTER_UP){
  146. finalintactionIndex=ev.getActionIndex();
  147. finalintidBitsToRemove=1<<ev.getPointerId(actionIndex);
  148. removePointersFromTouchTargets(idBitsToRemove);
  149. }
  150. }
  151. if(!handled&&mInputEventConsistencyVerifier!=null){
  152. mInputEventConsistencyVerifier.onUnhandledEvent(ev,1);
  153. }
  154. returnhandled;
  155. }

下面再看ViewGroup对点击事件的处理

Code:ViewGroup#dispatchTransformedTouchEvent

  1. /**
  2. *Transformsamotioneventintothecoordinatespaceofaparticularchildview,
  3. *filtersoutirrelevantpointerids,andoverridesitsactionifnecessary.
  4. *Ifchildisnull,assumestheMotionEventwillbesenttothisViewGroupinstead.
  5. */
  6. privatebooleandispatchTransformedTouchEvent(MotionEventevent,booleancancel,
  7. Viewchild,intdesiredPointerIdBits){
  8. finalbooleanhandled;
  9. //Cancelingmotionsisaspecialcase.Wedon'tneedtoperformanytransformations
  10. //orfiltering.Theimportantpartistheaction,notthecontents.
  11. finalintoldAction=event.getAction();
  12. if(cancel||oldAction==MotionEvent.ACTION_CANCEL){
  13. event.setAction(MotionEvent.ACTION_CANCEL);
  14. if(child==null){
  15. //这里就是ViewGroup对点击事件的处理,其调用了View的dispatchTouchEvent方法
  16. handled=super.dispatchTouchEvent(event);
  17. }else{
  18. handled=child.dispatchTouchEvent(event);
  19. }
  20. event.setAction(oldAction);
  21. returnhandled;
  22. }
  23. //Calculatethenumberofpointerstodeliver.
  24. finalintoldPointerIdBits=event.getPointerIdBits();
  25. finalintnewPointerIdBits=oldPointerIdBits&desiredPointerIdBits;
  26. //Ifforsomereasonweendedupinaninconsistentstatewhereitlookslikewe
  27. //mightproduceamotioneventwithnopointersinit,thendroptheevent.
  28. if(newPointerIdBits==0){
  29. returnfalse;
  30. }
  31. //Ifthenumberofpointersisthesameandwedon'tneedtoperformanyfancy
  32. //irreversibletransformations,thenwecanreusethemotioneventforthis
  33. //dispatchaslongaswearecarefultorevertanychangeswemake.
  34. //Otherwiseweneedtomakeacopy.
  35. finalMotionEventtransformedEvent;
  36. if(newPointerIdBits==oldPointerIdBits){
  37. if(child==null||child.hasIdentityMatrix()){
  38. if(child==null){
  39. handled=super.dispatchTouchEvent(event);
  40. }else{
  41. finalfloatoffsetX=mScrollX-child.mLeft;
  42. finalfloatoffsetY=mScrollY-child.mTop;
  43. event.offsetLocation(offsetX,offsetY);
  44. handled=child.dispatchTouchEvent(event);
  45. event.offsetLocation(-offsetX,-offsetY);
  46. }
  47. returnhandled;
  48. }
  49. transformedEvent=MotionEvent.obtain(event);
  50. }else{
  51. transformedEvent=event.split(newPointerIdBits);
  52. }
  53. //Performanynecessarytransformationsanddispatch.
  54. if(child==null){
  55. handled=super.dispatchTouchEvent(transformedEvent);
  56. }else{
  57. finalfloatoffsetX=mScrollX-child.mLeft;
  58. finalfloatoffsetY=mScrollY-child.mTop;
  59. transformedEvent.offsetLocation(offsetX,offsetY);
  60. if(!child.hasIdentityMatrix()){
  61. transformedEvent.transform(child.getInverseMatrix());
  62. }
  63. handled=child.dispatchTouchEvent(transformedEvent);
  64. }
  65. //Done.
  66. transformedEvent.recycle();
  67. returnhandled;
  68. }
再看

Code:View#dispatchTouchEvent

  1. /**
  2. *Passthetouchscreenmotioneventdowntothetargetview,orthis
  3. *viewifitisthetarget.
  4. *
  5. *@parameventThemotioneventtobedispatched.
  6. *@returnTrueiftheeventwashandledbytheview,falseotherwise.
  7. */
  8. publicbooleandispatchTouchEvent(MotionEventevent){
  9. if(mInputEventConsistencyVerifier!=null){
  10. mInputEventConsistencyVerifier.onTouchEvent(event,0);
  11. }
  12. if(onFilterTouchEventForSecurity(event)){
  13. //noinspectionSimplifiableIfStatement
  14. ListenerInfoli=mListenerInfo;
  15. if(li!=null&&li.mOnTouchListener!=null&&(mViewFlags&ENABLED_MASK)==ENABLED
  16. &&li.mOnTouchListener.onTouch(this,event)){
  17. returntrue;
  18. }
  19. if(onTouchEvent(event)){
  20. returntrue;
  21. }
  22. }
  23. if(mInputEventConsistencyVerifier!=null){
  24. mInputEventConsistencyVerifier.onUnhandledEvent(event,0);
  25. }
  26. returnfalse;
  27. }
这段代码比较简单,View对事件的处理是这样的:如果设置了OnTouchListener就调用onTouch,否则就直接调用onTouchEvent,而onClick是在onTouchEvent内部通过performClick触发的。简单来说,事件如果被ViewGroup拦截或者子View的onTouchEvent都返回了false,则事件最终由ViewGroup处理。

3.无人处理的点击事件

如果一个点击事件,子View的onTouchEvent返回了false,则父View的onTouchEvent会被直接调用,以此类推。如果所有的View都不处理,则最终会由Activity来处理,这个时候,Activity的onTouchEvent会被调用。这个问题已经在1和2中做了说明。

分享到:
评论

相关推荐

Global site tag (gtag.js) - Google Analytics