UISwipeGestureRecognizer not being called

Question

faustarts OP

Created Oct ’15

Replies 11

Boosts 0

Views 4.0k

Participants 5

Hello all,

Is there a known issue with UISwipeGestureRecognizers in tvOS with SpriteKit? My swipe gestures just don't seem to be getting called. I have the following in my didMoveToView:

        let swipeDown = UISwipeGestureRecognizer(target: self, action: "swiped:")
        swipeDown.direction = UISwipeGestureRecognizerDirection.Down
        view.addGestureRecognizer(swipeDown)
       
        let swipeUp = UISwipeGestureRecognizer(target: self, action: "swiped:")
        swipeUp.direction = UISwipeGestureRecognizerDirection.Up
        view.addGestureRecognizer(swipeUp)
       
        let swipeLeft = UISwipeGestureRecognizer(target: self, action: "swiped:")
        swipeLeft.direction = UISwipeGestureRecognizerDirection.Left
        view.addGestureRecognizer(swipeLeft)
       
        let swipeRight = UISwipeGestureRecognizer(target: self, action: "swiped:")
        swipeRight.direction = UISwipeGestureRecognizerDirection.Right
        view.addGestureRecognizer(swipeRight)

I have tap gestures that are called without any issues, but for some reason the swipe gestures aren't being recognized.

Any help would be greatly appreciated. Thanks!

Answered by nthState in 77259022

Other thoughts:

- Are you remembering to remove the swipe gestures from previous scenes ? - if any.

- Are you doing anything with touches which might interfere with the cancelation of gestures ?

Boost

Answer 1

Brent Royal-Gordon OP

Oct ’15

Make sure the gesture recognizer allows indirect touches.

swipeDown.allowedTouchTypes = [UITouchType.Indirect].map { $0.rawValue }

0

Answer 2

faustarts OP

Oct ’15

Unfortunately it still doesn't recognize the swipe, even after allowing indirect touches.

0

Answer 3

bsabiston OP

Oct ’15

I was having a hard time getting swipes to work. I'm not using SpriteKit, so yours may be a different issue. But for me I think it was a matter of providing a canBecomeFocused override for the view receiving the swipes:

- (BOOL)canBecomeFocused {

return YES;

}

Bob

0

Answer 4

Gabe Kangas OP

Oct ’15

I always forget to set userInteractionEnabled to true on views with a gesture recognizer. Maybe you did too?

0

Answer 5

faustarts OP

Oct ’15

I always forget as well, but this is one of the rare cases that I didn't. Even after setting userInteractionEnabled to true. Whats particularly confusing is the fact that it the gestures are added to the view without any issues. It's just that the selector is never reached.

0

Answer 6

faustarts OP

Oct ’15

Thank you for the suggestion, however I believe since my class isn't a subclass of UIView I won't be able to override the canBecomeFocused method.

0

Answer 7

bsabiston OP

Oct ’15

In order to use gesture recognizere, don't they have to operate upon a UIView or subset? Whatever view that is, I think it needs to be the focused view.

0

Answer 8

faustarts OP

Oct ’15

You are correct. What I did was add the following to the top of my scene class:

public extension SKView {
    override func canBecomeFocused() -> Bool {
        return true
    }
}

This sets canBecomeFocused of the view that my SKScene sits on to true, however the same issue persists. The selector is never reached.

0

Answer 9

bsabiston OP

Oct ’15

You might try checking to see what is the focused view. I'm not at my computer but I remember some other calls influencing focus - shouldBecomeFocused, maybe? Maybe your problem is unrelated. I spent some time before fixing my problem where I thought it had to do with the firstResponder. You might make sure that is the he correct view.

0

Answer 10

nthState OP

Oct ’15

Accepted Answer

Other thoughts:

- Are you remembering to remove the swipe gestures from previous scenes ? - if any.

- Are you doing anything with touches which might interfere with the cancelation of gestures ?

0

Answer 11

faustarts OP

Oct ’15

AH! You are correct. For some reason there were gestures being set up in the main ViewController that I had forgotten were there. Cleaning those up seems to have fixed the issue. Thank you!

0