cocos2d-x  2.2.3-gd2.113-rev1ec524e
Loading...
Searching...
No Matches
CCTargetedTouchDelegate Class Reference

Using this type of delegate results in two benefits: More...

#include <CCTouchDelegateProtocol.h>

Inheritance diagram for CCTargetedTouchDelegate:
[legend]
Collaboration diagram for CCTargetedTouchDelegate:
[legend]

Public Member Functions

virtual bool ccTouchBegan (CCTouch *pTouch, CCEvent *pEvent)
 Return YES to claim the touch. More...
 
virtual void ccTouchMoved (CCTouch *pTouch, CCEvent *pEvent)
 
virtual void ccTouchEnded (CCTouch *pTouch, CCEvent *pEvent)
 
virtual void ccTouchCancelled (CCTouch *pTouch, CCEvent *pEvent)
 
- Public Member Functions inherited from CCTouchDelegate
 CCTouchDelegate ()
 
virtual ~CCTouchDelegate ()
 
virtual bool ccTouchBegan (CCTouch *pTouch, CCEvent *pEvent)
 
virtual void ccTouchMoved (CCTouch *pTouch, CCEvent *pEvent)
 
virtual void ccTouchEnded (CCTouch *pTouch, CCEvent *pEvent)
 
virtual void ccTouchCancelled (CCTouch *pTouch, CCEvent *pEvent)
 
virtual void ccTouchesBegan (CCSet *pTouches, CCEvent *pEvent)
 
virtual void ccTouchesMoved (CCSet *pTouches, CCEvent *pEvent)
 
virtual void ccTouchesEnded (CCSet *pTouches, CCEvent *pEvent)
 
virtual void ccTouchesCancelled (CCSet *pTouches, CCEvent *pEvent)
 

Detailed Description

Using this type of delegate results in two benefits:

  • 1. You don't need to deal with CCSets, the dispatcher does the job of splitting them. You get exactly one UITouch per call.
  • 2. You can claim a UITouch by returning YES in ccTouchBegan. Updates of claimed touches are sent only to the delegate(s) that claimed them. So if you get a move/ ended/canceled update you're sure it's your touch. This frees you from doing a lot of checks when doing multi-touch.

(The name TargetedTouchDelegate relates to updates "targeting" their specific handler, without bothering the other handlers.)

Since
v0.8 NA NA

Member Function Documentation

◆ ccTouchBegan()

virtual bool ccTouchBegan ( CCTouch pTouch,
CCEvent pEvent 
)
inlinevirtual

Return YES to claim the touch.

Since
v0

Reimplemented from CCTouchDelegate.

◆ ccTouchCancelled()

virtual void ccTouchCancelled ( CCTouch pTouch,
CCEvent pEvent 
)
inlinevirtual

Reimplemented from CCTouchDelegate.

◆ ccTouchEnded()

virtual void ccTouchEnded ( CCTouch pTouch,
CCEvent pEvent 
)
inlinevirtual

Reimplemented from CCTouchDelegate.

◆ ccTouchMoved()

virtual void ccTouchMoved ( CCTouch pTouch,
CCEvent pEvent 
)
inlinevirtual

Reimplemented from CCTouchDelegate.


The documentation for this class was generated from the following file: