Strange Behavior with UITapGestureRecognizer

I implemented a SnackBar / Toast Message in Swift 4 which allows the developer to set the following display duration (enum) and with the following behaviour:

.long / .short: Timer gets fired and dismisses the SnackBar OR the user taps the view and it also dismisses

.constant: No Timer, only TapGesture to dismiss

Now in the first case (.long / .short) the SnackBar reacts as expected. Either the Timer fires or the user taps and the view gets dismissed.

In the second case (.constant) - where there is no timer - the Tap gesture is not recognised and the view doesn't get dismissed

here are the three functions:

    private func defineDismissMode(){

        switch self.message.duration {

        case .short, .long:

            self.setTimer()

        case .constant:

            self.setTapGesture()

        }

    }



    private func setTimer(){

        guard self.timer == nil else {return}

        self.timer = Timer.scheduledTimer(timeInterval: self.message.duration.rawValue, target: self, selector: #selector(self.dismissSnackBar), userInfo: nil, repeats: false)

        self.setTapGesture()

    }



    private func setTapGesture() {

        self.tapGestureRecognizer = UITapGestureRecognizer(target: self, action: #selector(self.dismissSnackBar))

        self.snackView.addGestureRecognizer(self.tapGestureRecognizer!)

    }



    @objc private func dismissSnackBar(){

      ...

    }

Anyone a clue why when setTapGesture() is called after setTimer() it works and a tap triggers self.dismissSnackBar , but when called without setTimer() the UITapGestureRecognizer is not triggered?

Note: Yes I checked that case: .constant -> setTapGesture() gets called

asked Jan 1 at 16:26

CRE8IT

126112

Are you doing this on a background thread?

– agibson007
Jan 1 at 16:44

@agibson007 valid question which I was shortly also looking into, but since setTapGesture() works well when called after setTimer() but not when called directly, I naively figure the thread might have no relevance

– CRE8IT
Jan 1 at 16:48

it has relevance. It could be something about adding a timer that forces it to the main thread. I would make sure you are calling from the main thread.

– agibson007
Jan 1 at 19:10

@agibson007 you could make a point although I might miss the correlation between the two calls in terms of threads. By using .scheduledTimer I indeed set the timer in the main thread; what I miss to understand is why the next call to setTapGesture() would be pulled into the main thread because of the timer (any idea why?). I will thus try - when called without timer - to set the tapgesture into the main thread...

– CRE8IT
Jan 1 at 20:41

@agibson007 unfortunately calling it from the main thread hasn't helped

– CRE8IT
Jan 1 at 20:50

add a comment |

I implemented a SnackBar / Toast Message in Swift 4 which allows the developer to set the following display duration (enum) and with the following behaviour:

.long / .short: Timer gets fired and dismisses the SnackBar OR the user taps the view and it also dismisses

.constant: No Timer, only TapGesture to dismiss

Now in the first case (.long / .short) the SnackBar reacts as expected. Either the Timer fires or the user taps and the view gets dismissed.

In the second case (.constant) - where there is no timer - the Tap gesture is not recognised and the view doesn't get dismissed

here are the three functions:

    private func defineDismissMode(){

        switch self.message.duration {

        case .short, .long:

            self.setTimer()

        case .constant:

            self.setTapGesture()

        }

    }



    private func setTimer(){

        guard self.timer == nil else {return}

        self.timer = Timer.scheduledTimer(timeInterval: self.message.duration.rawValue, target: self, selector: #selector(self.dismissSnackBar), userInfo: nil, repeats: false)

        self.setTapGesture()

    }



    private func setTapGesture() {

        self.tapGestureRecognizer = UITapGestureRecognizer(target: self, action: #selector(self.dismissSnackBar))

        self.snackView.addGestureRecognizer(self.tapGestureRecognizer!)

    }



    @objc private func dismissSnackBar(){

      ...

    }

Note: Yes I checked that case: .constant -> setTapGesture() gets called

asked Jan 1 at 16:26

CRE8IT

126112

Are you doing this on a background thread?

– agibson007
Jan 1 at 16:44

@agibson007 valid question which I was shortly also looking into, but since setTapGesture() works well when called after setTimer() but not when called directly, I naively figure the thread might have no relevance

– CRE8IT
Jan 1 at 16:48

it has relevance. It could be something about adding a timer that forces it to the main thread. I would make sure you are calling from the main thread.

– agibson007
Jan 1 at 19:10

@agibson007 you could make a point although I might miss the correlation between the two calls in terms of threads. By using .scheduledTimer I indeed set the timer in the main thread; what I miss to understand is why the next call to setTapGesture() would be pulled into the main thread because of the timer (any idea why?). I will thus try - when called without timer - to set the tapgesture into the main thread...

– CRE8IT
Jan 1 at 20:41

@agibson007 unfortunately calling it from the main thread hasn't helped

– CRE8IT
Jan 1 at 20:50

add a comment |

I implemented a SnackBar / Toast Message in Swift 4 which allows the developer to set the following display duration (enum) and with the following behaviour:

.long / .short: Timer gets fired and dismisses the SnackBar OR the user taps the view and it also dismisses

.constant: No Timer, only TapGesture to dismiss

Now in the first case (.long / .short) the SnackBar reacts as expected. Either the Timer fires or the user taps and the view gets dismissed.

In the second case (.constant) - where there is no timer - the Tap gesture is not recognised and the view doesn't get dismissed

here are the three functions:

    private func defineDismissMode(){

        switch self.message.duration {

        case .short, .long:

            self.setTimer()

        case .constant:

            self.setTapGesture()

        }

    }



    private func setTimer(){

        guard self.timer == nil else {return}

        self.timer = Timer.scheduledTimer(timeInterval: self.message.duration.rawValue, target: self, selector: #selector(self.dismissSnackBar), userInfo: nil, repeats: false)

        self.setTapGesture()

    }



    private func setTapGesture() {

        self.tapGestureRecognizer = UITapGestureRecognizer(target: self, action: #selector(self.dismissSnackBar))

        self.snackView.addGestureRecognizer(self.tapGestureRecognizer!)

    }



    @objc private func dismissSnackBar(){

      ...

    }

Note: Yes I checked that case: .constant -> setTapGesture() gets called

asked Jan 1 at 16:26

CRE8IT

126112

I implemented a SnackBar / Toast Message in Swift 4 which allows the developer to set the following display duration (enum) and with the following behaviour:

.long / .short: Timer gets fired and dismisses the SnackBar OR the user taps the view and it also dismisses

.constant: No Timer, only TapGesture to dismiss

Now in the first case (.long / .short) the SnackBar reacts as expected. Either the Timer fires or the user taps and the view gets dismissed.

In the second case (.constant) - where there is no timer - the Tap gesture is not recognised and the view doesn't get dismissed

here are the three functions:

    private func defineDismissMode(){

        switch self.message.duration {

        case .short, .long:

            self.setTimer()

        case .constant:

            self.setTapGesture()

        }

    }



    private func setTimer(){

        guard self.timer == nil else {return}

        self.timer = Timer.scheduledTimer(timeInterval: self.message.duration.rawValue, target: self, selector: #selector(self.dismissSnackBar), userInfo: nil, repeats: false)

        self.setTapGesture()

    }



    private func setTapGesture() {

        self.tapGestureRecognizer = UITapGestureRecognizer(target: self, action: #selector(self.dismissSnackBar))

        self.snackView.addGestureRecognizer(self.tapGestureRecognizer!)

    }



    @objc private func dismissSnackBar(){

      ...

    }

Note: Yes I checked that case: .constant -> setTapGesture() gets called

ios swift uitapgesturerecognizer

asked Jan 1 at 16:26

CRE8IT

126112

asked Jan 1 at 16:26

CRE8IT

126112

asked Jan 1 at 16:26

CRE8IT

126112

asked Jan 1 at 16:26

CRE8IT

126112

asked Jan 1 at 16:26

CRE8IT

126112

Are you doing this on a background thread?

– agibson007
Jan 1 at 16:44

@agibson007 valid question which I was shortly also looking into, but since setTapGesture() works well when called after setTimer() but not when called directly, I naively figure the thread might have no relevance

– CRE8IT
Jan 1 at 16:48

it has relevance. It could be something about adding a timer that forces it to the main thread. I would make sure you are calling from the main thread.

– agibson007
Jan 1 at 19:10

@agibson007 you could make a point although I might miss the correlation between the two calls in terms of threads. By using .scheduledTimer I indeed set the timer in the main thread; what I miss to understand is why the next call to setTapGesture() would be pulled into the main thread because of the timer (any idea why?). I will thus try - when called without timer - to set the tapgesture into the main thread...

– CRE8IT
Jan 1 at 20:41

@agibson007 unfortunately calling it from the main thread hasn't helped

– CRE8IT
Jan 1 at 20:50

add a comment |

Are you doing this on a background thread?

– agibson007
Jan 1 at 16:44

@agibson007 valid question which I was shortly also looking into, but since setTapGesture() works well when called after setTimer() but not when called directly, I naively figure the thread might have no relevance

– CRE8IT
Jan 1 at 16:48

it has relevance. It could be something about adding a timer that forces it to the main thread. I would make sure you are calling from the main thread.

– agibson007
Jan 1 at 19:10

@agibson007 you could make a point although I might miss the correlation between the two calls in terms of threads. By using .scheduledTimer I indeed set the timer in the main thread; what I miss to understand is why the next call to setTapGesture() would be pulled into the main thread because of the timer (any idea why?). I will thus try - when called without timer - to set the tapgesture into the main thread...

– CRE8IT
Jan 1 at 20:41

@agibson007 unfortunately calling it from the main thread hasn't helped

– CRE8IT
Jan 1 at 20:50

Are you doing this on a background thread?

– agibson007
Jan 1 at 16:44

@agibson007 valid question which I was shortly also looking into, but since setTapGesture() works well when called after setTimer() but not when called directly, I naively figure the thread might have no relevance

– CRE8IT
Jan 1 at 16:48

it has relevance. It could be something about adding a timer that forces it to the main thread. I would make sure you are calling from the main thread.

– agibson007
Jan 1 at 19:10

@agibson007 you could make a point although I might miss the correlation between the two calls in terms of threads. By using .scheduledTimer I indeed set the timer in the main thread; what I miss to understand is why the next call to setTapGesture() would be pulled into the main thread because of the timer (any idea why?). I will thus try - when called without timer - to set the tapgesture into the main thread...

– CRE8IT
Jan 1 at 20:41

@agibson007 unfortunately calling it from the main thread hasn't helped

– CRE8IT
Jan 1 at 20:50

add a comment |

0

active

oldest

votes

Your Answer

StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53997059%2fstrange-behavior-with-uitapgesturerecognizer%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

0

active

oldest

votes

0

active

oldest

votes

draft saved

draft discarded

Thanks for contributing an answer to Stack Overflow!

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

Search This Blog

Ufyukyu