Currently, my code instantiates a new UIPresentationController subclass each time presentationControllerForPresentedViewController(…) is called. Unfortunately, when I present a VC, presentationControllerForPresentedViewController(…) is called three times! This seems wasteful, at best, and possibly broken, since state is not tracked across calls.
I could try to keep a reference around for it, but then I'm holding on to a reference that won't be updated properly the next time. presentationControllerForPresentedViewController() passes in a couple of parameters required by UIPresentationController's constructor. Is this a bug, or is this just how it is? -- Rick Mann rm...@latencyzero.com _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
