Concurrent UIAlertController dismiss and segue
I suspect that the answer is no, but thought I would ask anyway.
Is there a way to have a segue between view controllers begin before a UIAlertController's action sheet has completed its dismissal? (The action sheet drives which view controller should be pushed.)
I have placed breakpoints and print statements in the UIAlertAction's action handler block and it appears that this block is not invoked until after the action sheet has been dismissed.
I have done similar with the completion handler of the present call that raised the action sheet. Again, not invoked until (surprise) the sheet has been dismissed.
Here is my code (without the experiments mentioned above)
func startNewPuzzle(required:Bool=false)
{
let selection = UIAlertController(title:"New Puzzle",
message:"How would you like to start the puzzle",
preferredStyle:.actionSheet)
selection.addAction( UIAlertAction(title:"manual",style:.default) { _ in
self.performSegue(withIdentifier: "showNewPuzzle", sender: self)
} )
selection.addAction( UIAlertAction(title:"random",style:.default) { _ in
self.performSegue(withIdentifier: "showRandomPuzzle", sender: self)
} )
selection.addAction( UIAlertAction(title:"scanned",style:.default) { _ in
self.performSegue(withIdentifier: "showScanPuzzle", sender: self)
} )
if !required { selection.addAction( UIAlertAction(title:"cancel",style:.cancel) ) }
self.present(selection,animated: false)
}
ios segue
add a comment |
I suspect that the answer is no, but thought I would ask anyway.
Is there a way to have a segue between view controllers begin before a UIAlertController's action sheet has completed its dismissal? (The action sheet drives which view controller should be pushed.)
I have placed breakpoints and print statements in the UIAlertAction's action handler block and it appears that this block is not invoked until after the action sheet has been dismissed.
I have done similar with the completion handler of the present call that raised the action sheet. Again, not invoked until (surprise) the sheet has been dismissed.
Here is my code (without the experiments mentioned above)
func startNewPuzzle(required:Bool=false)
{
let selection = UIAlertController(title:"New Puzzle",
message:"How would you like to start the puzzle",
preferredStyle:.actionSheet)
selection.addAction( UIAlertAction(title:"manual",style:.default) { _ in
self.performSegue(withIdentifier: "showNewPuzzle", sender: self)
} )
selection.addAction( UIAlertAction(title:"random",style:.default) { _ in
self.performSegue(withIdentifier: "showRandomPuzzle", sender: self)
} )
selection.addAction( UIAlertAction(title:"scanned",style:.default) { _ in
self.performSegue(withIdentifier: "showScanPuzzle", sender: self)
} )
if !required { selection.addAction( UIAlertAction(title:"cancel",style:.cancel) ) }
self.present(selection,animated: false)
}
ios segue
Interestingly, the behavior I'm seeing appears to be exactly opposite of the behavior observed in stackoverflow.com/questions/40367565/…
– MikeMayer67
Dec 28 '18 at 14:18
add a comment |
I suspect that the answer is no, but thought I would ask anyway.
Is there a way to have a segue between view controllers begin before a UIAlertController's action sheet has completed its dismissal? (The action sheet drives which view controller should be pushed.)
I have placed breakpoints and print statements in the UIAlertAction's action handler block and it appears that this block is not invoked until after the action sheet has been dismissed.
I have done similar with the completion handler of the present call that raised the action sheet. Again, not invoked until (surprise) the sheet has been dismissed.
Here is my code (without the experiments mentioned above)
func startNewPuzzle(required:Bool=false)
{
let selection = UIAlertController(title:"New Puzzle",
message:"How would you like to start the puzzle",
preferredStyle:.actionSheet)
selection.addAction( UIAlertAction(title:"manual",style:.default) { _ in
self.performSegue(withIdentifier: "showNewPuzzle", sender: self)
} )
selection.addAction( UIAlertAction(title:"random",style:.default) { _ in
self.performSegue(withIdentifier: "showRandomPuzzle", sender: self)
} )
selection.addAction( UIAlertAction(title:"scanned",style:.default) { _ in
self.performSegue(withIdentifier: "showScanPuzzle", sender: self)
} )
if !required { selection.addAction( UIAlertAction(title:"cancel",style:.cancel) ) }
self.present(selection,animated: false)
}
ios segue
I suspect that the answer is no, but thought I would ask anyway.
Is there a way to have a segue between view controllers begin before a UIAlertController's action sheet has completed its dismissal? (The action sheet drives which view controller should be pushed.)
I have placed breakpoints and print statements in the UIAlertAction's action handler block and it appears that this block is not invoked until after the action sheet has been dismissed.
I have done similar with the completion handler of the present call that raised the action sheet. Again, not invoked until (surprise) the sheet has been dismissed.
Here is my code (without the experiments mentioned above)
func startNewPuzzle(required:Bool=false)
{
let selection = UIAlertController(title:"New Puzzle",
message:"How would you like to start the puzzle",
preferredStyle:.actionSheet)
selection.addAction( UIAlertAction(title:"manual",style:.default) { _ in
self.performSegue(withIdentifier: "showNewPuzzle", sender: self)
} )
selection.addAction( UIAlertAction(title:"random",style:.default) { _ in
self.performSegue(withIdentifier: "showRandomPuzzle", sender: self)
} )
selection.addAction( UIAlertAction(title:"scanned",style:.default) { _ in
self.performSegue(withIdentifier: "showScanPuzzle", sender: self)
} )
if !required { selection.addAction( UIAlertAction(title:"cancel",style:.cancel) ) }
self.present(selection,animated: false)
}
ios segue
ios segue
edited Dec 28 '18 at 14:20
asked Dec 28 '18 at 0:17
MikeMayer67
173311
173311
Interestingly, the behavior I'm seeing appears to be exactly opposite of the behavior observed in stackoverflow.com/questions/40367565/…
– MikeMayer67
Dec 28 '18 at 14:18
add a comment |
Interestingly, the behavior I'm seeing appears to be exactly opposite of the behavior observed in stackoverflow.com/questions/40367565/…
– MikeMayer67
Dec 28 '18 at 14:18
Interestingly, the behavior I'm seeing appears to be exactly opposite of the behavior observed in stackoverflow.com/questions/40367565/…
– MikeMayer67
Dec 28 '18 at 14:18
Interestingly, the behavior I'm seeing appears to be exactly opposite of the behavior observed in stackoverflow.com/questions/40367565/…
– MikeMayer67
Dec 28 '18 at 14:18
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
});
}
});
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%2f53952297%2fconcurrent-uialertcontroller-dismiss-and-segue%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f53952297%2fconcurrent-uialertcontroller-dismiss-and-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
Interestingly, the behavior I'm seeing appears to be exactly opposite of the behavior observed in stackoverflow.com/questions/40367565/…
– MikeMayer67
Dec 28 '18 at 14:18