Setting UISearchController isActive to false stops segue
I'm trying to dismiss the search controller before a segue is performed. I have added the following code to the prepare
portion of my view controller:
override func prepare(for segue: UIStoryboardSegue, sender: Any?) {
searchController.isActive = false
}
This works perfectly fine at dismissing the search controller, but once the search controller has been dismissed the segue doesn't perform. It's as if dismissing the search controller stops the rest of the segue.
Is there a different way to dismiss a UISearchController
that doesn't interrupt a segue's flow while still calling all of the accompanying delegate methods?
ios swift uikit segue uisearchcontroller
add a comment |
I'm trying to dismiss the search controller before a segue is performed. I have added the following code to the prepare
portion of my view controller:
override func prepare(for segue: UIStoryboardSegue, sender: Any?) {
searchController.isActive = false
}
This works perfectly fine at dismissing the search controller, but once the search controller has been dismissed the segue doesn't perform. It's as if dismissing the search controller stops the rest of the segue.
Is there a different way to dismiss a UISearchController
that doesn't interrupt a segue's flow while still calling all of the accompanying delegate methods?
ios swift uikit segue uisearchcontroller
add a comment |
I'm trying to dismiss the search controller before a segue is performed. I have added the following code to the prepare
portion of my view controller:
override func prepare(for segue: UIStoryboardSegue, sender: Any?) {
searchController.isActive = false
}
This works perfectly fine at dismissing the search controller, but once the search controller has been dismissed the segue doesn't perform. It's as if dismissing the search controller stops the rest of the segue.
Is there a different way to dismiss a UISearchController
that doesn't interrupt a segue's flow while still calling all of the accompanying delegate methods?
ios swift uikit segue uisearchcontroller
I'm trying to dismiss the search controller before a segue is performed. I have added the following code to the prepare
portion of my view controller:
override func prepare(for segue: UIStoryboardSegue, sender: Any?) {
searchController.isActive = false
}
This works perfectly fine at dismissing the search controller, but once the search controller has been dismissed the segue doesn't perform. It's as if dismissing the search controller stops the rest of the segue.
Is there a different way to dismiss a UISearchController
that doesn't interrupt a segue's flow while still calling all of the accompanying delegate methods?
ios swift uikit segue uisearchcontroller
ios swift uikit segue uisearchcontroller
asked Nov 15 '18 at 14:12
CarlCarl
8210
8210
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Are you triggering the segue programmatically or through a storyboard?
If the former, you should dismiss the search controller before calling performSegueWithIdentifier:sender:
by moving that call out of the function above and above your performSegueWithIdentifier:sender:
call.
If the latter and you can't find a place to dismiss it elsewhere, you could try moving the dismissal to shouldPerformSegueWithIdentifier:sender:
although you might run into the same issue there.
This solution worked great, thanks so much.
– Carl
Nov 15 '18 at 15:06
add a comment |
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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53321342%2fsetting-uisearchcontroller-isactive-to-false-stops-segue%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Are you triggering the segue programmatically or through a storyboard?
If the former, you should dismiss the search controller before calling performSegueWithIdentifier:sender:
by moving that call out of the function above and above your performSegueWithIdentifier:sender:
call.
If the latter and you can't find a place to dismiss it elsewhere, you could try moving the dismissal to shouldPerformSegueWithIdentifier:sender:
although you might run into the same issue there.
This solution worked great, thanks so much.
– Carl
Nov 15 '18 at 15:06
add a comment |
Are you triggering the segue programmatically or through a storyboard?
If the former, you should dismiss the search controller before calling performSegueWithIdentifier:sender:
by moving that call out of the function above and above your performSegueWithIdentifier:sender:
call.
If the latter and you can't find a place to dismiss it elsewhere, you could try moving the dismissal to shouldPerformSegueWithIdentifier:sender:
although you might run into the same issue there.
This solution worked great, thanks so much.
– Carl
Nov 15 '18 at 15:06
add a comment |
Are you triggering the segue programmatically or through a storyboard?
If the former, you should dismiss the search controller before calling performSegueWithIdentifier:sender:
by moving that call out of the function above and above your performSegueWithIdentifier:sender:
call.
If the latter and you can't find a place to dismiss it elsewhere, you could try moving the dismissal to shouldPerformSegueWithIdentifier:sender:
although you might run into the same issue there.
Are you triggering the segue programmatically or through a storyboard?
If the former, you should dismiss the search controller before calling performSegueWithIdentifier:sender:
by moving that call out of the function above and above your performSegueWithIdentifier:sender:
call.
If the latter and you can't find a place to dismiss it elsewhere, you could try moving the dismissal to shouldPerformSegueWithIdentifier:sender:
although you might run into the same issue there.
answered Nov 15 '18 at 14:32
Mark ThormannMark Thormann
1,326712
1,326712
This solution worked great, thanks so much.
– Carl
Nov 15 '18 at 15:06
add a comment |
This solution worked great, thanks so much.
– Carl
Nov 15 '18 at 15:06
This solution worked great, thanks so much.
– Carl
Nov 15 '18 at 15:06
This solution worked great, thanks so much.
– Carl
Nov 15 '18 at 15:06
add a comment |
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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53321342%2fsetting-uisearchcontroller-isactive-to-false-stops-segue%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown