Son of a gun, I think you got it.
I was wondering about whether properties were somehow involved, but I
had not declared any like that in my classes, and didn't think of the
inherited ones. Good call.
Oh, I guess I will have to actually fix the code now, but I am willing
to bet this is the answer.
Thanks,
Paul
On Nov 20, 2009, at 5:23 PM, Michael Babin wrote:
On Nov 20, 2009, at 5:55 PM, Paul Archibald wrote:
So, why does setParentViewController get called twice, and why is
the parameter type different the second time, and why don't I get
an exception when the wrong type is gets passed into
setParentViewController that second time?
Probably because UIViewController already has a property named
parentViewController. Your set method is probably overriding the one
defined in UIViewController, and thus getting called by
UINavigationController when you tell it to push your view controller
onto its stack.
_______________________________________________
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
