Re: Unwind segues
Re: Unwind segues
- Subject: Re: Unwind segues
- From: Alex Zavatone <email@hidden>
- Date: Tue, 30 Apr 2013 17:27:24 -0400
OK. Here's an idea.
Try a simple case.
Create an empty app with a nav controller and a button to segue to another screen. Then one more to do the same. Set up a simple case where your method should get triggered on an exit case and see if it does in a simple, easily trashable file that you don't care about at aii.
It's approaches like that that most always end up helping me work through the sticky issues.
GL.
On Apr 30, 2013, at 5:23 PM, Rick Mann wrote:
>
> On Apr 30, 2013, at 14:21 , Alex Zavatone <email@hidden> wrote:
>
>> Odd. I've never played around with the exits yet. If you hook it up to a UIButton and trigger is manually with a tap, does it get called?
>
> Yes, that's how I had it before. I just wanted to try the "new" way.
>
>> Try that and set a breakpoint on it and see if there is a clear call chain. If it doesn't appear in the execution chain, then it might be one of those hard to spot issues on your part.
>
> I can certainly connect to IBActions in the current view controller. But the implication online is that this mechanism allows calling actions in parent view controllers, but it doesn't seem to work at all.
>
>
>> If the project is small and you don't mind, you could mail it to me offlist and I could take a peek.
>
> Unfortunately, it's company work, and it's not small any more. :-)
>
>
> --
> Rick
>
>
>
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden