美文网首页将来跳槽用
iOS 事件传递和视图响应链

iOS 事件传递和视图响应链

作者: Silence_xl | 来源:发表于2021-06-12 14:39 被阅读0次

    1、事件的分类

    multitouch events:所谓的多点触摸事件,即用户触摸屏幕交互产生的事件类型;
    motion events:所谓的移动事件。是指用户在摇晃、移动和倾斜手机的时候产生的事件称为移动事件。这类事件依赖于iPhone手机里边的加速器,陀螺仪等传感器;
    remote control events:所谓的远程控制事件。指的是用户在操作多媒体的时候产生的事件。比如,播放音乐,视频等。

    2、触摸事件

    UIEvent
    iOS将触摸事件定义第一个手指开始触摸屏幕到最后一个手指离开屏幕为一个触摸事件。用类UIEvent表示。
    UITouch
    一个手指第一次点屏幕,会形成一个UITouch对象,知道离开销毁,表示触碰。UITouch对象能表明了当前手指触碰屏幕的位置,状态。状态分为开始触碰,移动和离开。
    根据定义,UIEvent实际包括了多个UITouch对象。有几个手指触碰,就会有几个UITouch对象。代码定义如下:

    typedef NS_ENUM(NSInteger, UIEventType) {
        UIEventTypeTouches,
        UIEventTypeMotion,
        UIEventTypeRemoteControl,
        UIEventTypePresses API_AVAILABLE(ios(9.0)),
    };
    @interface UIEvent : NSObject
    
    @property(nonatomic,readonly) UIEventType     type API_AVAILABLE(ios(3.0));
    @property(nonatomic,readonly) UIEventSubtype  subtype API_AVAILABLE(ios(3.0));
    
    @property(nonatomic,readonly) NSTimeInterval  timestamp;
    
    @property(nonatomic, readonly, nullable) NSSet <UITouch *> *allTouches;
    
    - (nullable NSSet <UITouch *> *)touchesForWindow:(UIWindow *)window;
    - (nullable NSSet <UITouch *> *)touchesForView:(UIView *)view;
    - (nullable NSSet <UITouch *> *)touchesForGestureRecognizer:(UIGestureRecognizer *)gesture API_AVAILABLE(ios(3.2));
    
    @end
    

    其中UIEventType表明了事件类型,UIEvent表示了三大事件。
    allTouches是该事件所有UITouch对象的集合。

    typedef NS_ENUM(NSInteger, UITouchPhase) {
        UITouchPhaseBegan,             // whenever a finger touches the surface.
        UITouchPhaseMoved,             // whenever a finger moves on the surface.
        UITouchPhaseStationary,        // whenever a finger is touching the surface but hasn't moved since the previous event.
        UITouchPhaseEnded,             // whenever a finger leaves the surface.
        UITouchPhaseCancelled,         // whenever a touch doesn't end but we need to stop tracking (e.g. putting device to face)
    };
    
    @interface UITouch : NSObject
    
    @property(nonatomic,readonly) NSTimeInterval      timestamp;
    @property(nonatomic,readonly) UITouchPhase        phase;
    @property(nonatomic,readonly) NSUInteger          tapCount;   // touch down within a certain point within a certain amount of time
    @property(nonatomic,readonly) UITouchType         type API_AVAILABLE(ios(9.0));
    
    // majorRadius and majorRadiusTolerance are in points
    // The majorRadius will be accurate +/- the majorRadiusTolerance
    @property(nonatomic,readonly) CGFloat majorRadius API_AVAILABLE(ios(8.0));
    @property(nonatomic,readonly) CGFloat majorRadiusTolerance API_AVAILABLE(ios(8.0));
    
    @property(nullable,nonatomic,readonly,strong) UIWindow                        *window;
    @property(nullable,nonatomic,readonly,strong) UIView                          *view;
    @property(nullable,nonatomic,readonly,copy)   NSArray <UIGestureRecognizer *> *gestureRecognizers API_AVAILABLE(ios(3.2));
    

    UITouch中phase表明了手指移动的状态,包括 1.开始点击;2.移动;3.保持; 4.离开;5.被取消(手指没有离开屏幕,但是系统不再跟踪它了)

    综上,UIEvent就是一组UITouch。每当该组中任何一个UITouch对象的phase发生变化,系统都会产生一条TouchMessage。也就是说每次用户手指的移动和变化,UITouch都会形成状态改变,系统变回会形成Touch message进行传递和派发。

    3、Responder

    Responder是用来接收和处理事件的类。Responder的属性和方法

    @property(nonatomic, readonly, nullable) UIResponder *nextResponder;
    
    @property(nonatomic, readonly) BOOL canBecomeFirstResponder;    // default is NO
    - (BOOL)becomeFirstResponder;
    
    @property(nonatomic, readonly) BOOL canResignFirstResponder;    // default is YES
    - (BOOL)resignFirstResponder;
    
    @property(nonatomic, readonly) BOOL isFirstResponder;
    
    // Generally, all responders which do custom touch handling should override all four of these methods.
    // Your responder will receive either touchesEnded:withEvent: or touchesCancelled:withEvent: for each
    // touch it is handling (those touches it received in touchesBegan:withEvent:).
    // *** You must handle cancelled touches to ensure correct behavior in your application.  Failure to
    // do so is very likely to lead to incorrect behavior or crashes.
    - (void)touchesBegan:(NSSet<UITouch *> *)touches withEvent:(nullable UIEvent *)event;
    - (void)touchesMoved:(NSSet<UITouch *> *)touches withEvent:(nullable UIEvent *)event;
    - (void)touchesEnded:(NSSet<UITouch *> *)touches withEvent:(nullable UIEvent *)event;
    - (void)touchesCancelled:(NSSet<UITouch *> *)touches withEvent:(nullable UIEvent *)event;
    - (void)touchesEstimatedPropertiesUpdated:(NSSet<UITouch *> *)touches API_AVAILABLE(ios(9.1));
    
    // Generally, all responders which do custom press handling should override all four of these methods.
    // Your responder will receive either pressesEnded:withEvent or pressesCancelled:withEvent: for each
    // press it is handling (those presses it received in pressesBegan:withEvent:).
    // pressesChanged:withEvent: will be invoked for presses that provide an analog value
    // (like thumbsticks or analog push buttons)
    // *** You must handle cancelled presses to ensure correct behavior in your application.  Failure to
    // do so is very likely to lead to incorrect behavior or crashes.
    - (void)pressesBegan:(NSSet<UIPress *> *)presses withEvent:(nullable UIPressesEvent *)event API_AVAILABLE(ios(9.0));
    - (void)pressesChanged:(NSSet<UIPress *> *)presses withEvent:(nullable UIPressesEvent *)event API_AVAILABLE(ios(9.0));
    - (void)pressesEnded:(NSSet<UIPress *> *)presses withEvent:(nullable UIPressesEvent *)event API_AVAILABLE(ios(9.0));
    - (void)pressesCancelled:(NSSet<UIPress *> *)presses withEvent:(nullable UIPressesEvent *)event API_AVAILABLE(ios(9.0));
    
    - (void)motionBegan:(UIEventSubtype)motion withEvent:(nullable UIEvent *)event API_AVAILABLE(ios(3.0));
    - (void)motionEnded:(UIEventSubtype)motion withEvent:(nullable UIEvent *)event API_AVAILABLE(ios(3.0));
    - (void)motionCancelled:(UIEventSubtype)motion withEvent:(nullable UIEvent *)event API_AVAILABLE(ios(3.0));
    

    注意有个很中重要的方法,nextResponder,表明响应是一个链表结构,通过nextResponder找到下一个responder。这里是从第一个responder开始通过nextResponder传递事件,直到有responder响应了事件就停止传递;如果传递到最后一个responder都没有被响应,那么该事件就被抛弃。

    注意:UIResponser包括了各种Touch message的处理,比如说开始,移动,停止等等。常见的UIResponser有UIView及子类。UIApplication、UIWindow、UIViewController、UIView都是继承UIResponder,都可以传递和响应事件。

    程序启动
    UIApplication会生成一个单例,并会关联一个APPDelegate。APPDelegate作为整个响应链的根建立起来,而UIApplication会将自己与这个单例链接,即UIApplication的nextResponder(下一个事件处理者)为APPDelegate
    创建UIWindow
    程序启动后,任何的UIWindow被创建时,UIWindow内部都会把nextResponser设置为UIApplication单例。
    UIWindow初始化rootViewController, rootViewController的nextResponser会设置为UIWindow
    UIViewController初始化
    loadView, VC的view的nextResponser会被设置为VC.
    addSubView
    addSubView操作过程中,如果子subView不是VC的View,那么subView的nextResponser会被设置为superView。如果是VC的View,那就是 subView -> subView.VC ->superView

    4、事件的传递

    4.1 事件传递的流程

    触摸事件的传递是从父控件传递到子控件
    也就是从UIApplicaiton->window->寻找处理事件的最合适的view
    注意:如果父控件不能接受触摸事件,那么子控件就不可能接收到触摸事件。

    4.2 如何寻找最合适的控件来处理事件

    ①.首先判断主窗口(keyWindou)自己是否能接受触摸事件
    ②.判断触摸点是否在自己身上
    ③.子控件数组中从后往前遍历子控件,重复前面两个步骤(所谓从后往前遍历子控件,就是首先查找子控件数组中最后一个元素,然后执行1、2步骤)
    ④.如果没有符合条件的子控件,那么就认为自己最合适处理这个事件,也就是自己是最合适的view。

    4.3 两个重要的方法
    - (UIView *)hitTest:(CGPoint)point withEvent:(UIEvent *)event;
    - (BOOL)pointInside:(CGPoint)point withEvent:(UIEvent *)event;
    

    view会调用hitTest:withEvent:方法,hitTest:withEvent:方法底层会调用pointInside:withEvent:方法判断触摸点是不是在这个view的坐标上。如果在坐标上,会分发事件给这个view的子view。然后每个子view重复以上步骤,直至最底层的一个合适的view。

    UIView不能接收触摸事件的三种情况:

    不允许交互:userInteractionEnabled = NO
    隐藏:如果把父控件隐藏,那么子控件也会隐藏,隐藏的控件不能接受事件
    透明度:如果设置一个控件的透明度<0.01,会直接影响子控件的透明度。alpha:0.0~0.01为透明。
    整个过程的系统实现大致如下

    - (nullable UIView *)hitTest:(CGPoint)point withEvent:(nullable UIEvent *)event {
      //判断是否合格
        if (!self.hidden && self.alpha > 0.01 && self.isUserInteractionEnabled) {
            //判断点击位置是否在自己区域内部
            if ([self pointInside: point withEvent:event]) {
                UIView *attachedView;
                for (int i = self.subviews.count - 1; i >= 0; i--) {
                    UIView *view  = self.subviews[i];
                    //对子view进行hitTest
                    attachedView =  [view hitTest:point withEvent:event];
                    if (attachedView)
                        break;
                }
                if (attachedView)  {
                    return attachedView;
                } else {
                    return self;
                }
            }
        }
        return nil;
    }
    

    5、事件的响应

    5.1 触摸事件处理的整体过程

    1 用户点击屏幕后产生的一个触摸事件,经过一系列的传递过程后,会找到最合适的视图控件来处理这个事件
    2 找到最合适的视图控件后,就会调用控件的touches方法来作具体的事件处理touchesBegan…touchesMoved…touchedEnded…
    3 这些touches方法的默认做法是将事件顺着响应者链条向上传递(也就是touch方法默认不处理事件,只传递事件),将事件交给上一个响应者进行处理

    5.2 响应者链条

    在iOS程序中无论是最后面的UIWindow还是最前面的某个按钮,它们的摆放是有前后关系的,一个控件可以放到另一个控件上面或下面,那么用户点击某个控件时是触发上面的控件还是下面的控件呢,这种先后关系构成一个链条就叫响应者链。也可以说,响应者链是由多个响应者对象连接起来的链条。

    事件响应会先从底层最合适的view开始,然后随着上一步找到的链一层一层响应touch事件。默认touch事件会传递给上一层。如果到了viewcontroller的view,就会传递给viewcontroller。如果viewcontroller不能处理,就会传递给UIWindow。如果UIWindow无法处理,就会传递给UIApplication。如果UIApplication无法处理,就会传递给UIApplicationDelegate。如果UIApplicationDelegate不能处理,则会丢弃该事件。

    相关文章

      网友评论

        本文标题:iOS 事件传递和视图响应链

        本文链接:https://www.haomeiwen.com/subject/rfcieltx.html