assigning delegate?

[wdcurry]

The area that the repo seems to be missing entirely is the ability to easily use the repo and assign "self" to the popover to handle the proper workflow of actually using the popover's reason for being show. Perhaps I have a preset notion of what I am seeking that is keeping me from seeing the answer.

I searched "delegate" in the issues and found nary a mention, so thought to ask. thx.

[cozzin]

Hello, @wdcurry
Can you explain the specific situation that requires delegate?

[wdcurry]

I am trying to ensure my calling ViewController(s) act on the dismissal from a xib-based view popover and tap into the popover protocol that should be present. I can unwind but to do that nullifies the xib-based approach which has some benefits. Not the end of the world, just trying to help round out the repo (without actually doing pulls ;) )

[wdcurry]

I am sure I'm just not seeing the easy way out here but without accessing to the delegate in order to explicitly trap the dismissing of a popup from within the originating parent VC, AND allowing navigational movement within popovers (which is awesome), I just don't see how to track what I need.

The original popover call is done AFTER a fadeout to dim the main VC (looks better). Then when the one popover is in the willDisappear method, the fadeIn occurs (we have to do this here since we cannot catch via delegate the act if the user taps out of the popover by tapping on the originating VC).

This works UNTIL the user navigates deeper. The disappear method fades in, and then the new popover must fade out, and on and on. Messy as heck.

Unless we disallow tapping out to return, without expressing assigning delegates, it seems an elusive answer to find. I feel I may be all around the answer, and and tested via incrementing counters, but it is just not straightforward without an external tightly-coupled controlling global variable.