Implementing Gestures in Sparrow as an external class... Insights?

Colin Gilbert

Hi,

I am making a game which will (more or less) rely on a rather expanded set of gestures. The use of a big method in the Game.m file is messy, and in order to keep things portable I want to place them in a separate file. I've already read about the lack of UIGestureRecognizer, so I'll roll my own from the Sparrow classes.

I contemplate subclassing an SPEventDispatcher class to do the calculations+respond accordingly, and then adding an instance of it to whatever SPDisplayObject needs it. Is that the correct manner of doing so, or should that logic be inserted elsewhere?

Please offer you opinions,
Colin

Daniel

Sorry for the (ridiculously!) long response time! 🙁

Since a display object container only gets the touch events if some of its children are touched, it might not be the right place for a gesture recognizer.

E.g. if you've got a display object containing a quad that's centered on the screen, and a player swipes from the very left to the very right of the screen, your quad won't even be notified. (The target of the touch event is, throughout its lifetime, the object where the touch was started.)

So you probably need to create a global gesture recognizer that listens to touch events on the stage. When it detects a swipe, it could "broadcast" a "SwipEvent" (defined by you) to all its children (there's a "broadcastEvent:" method that does just that).