nibs don't respect protocols
nibs don't respect protocols
- Subject: nibs don't respect protocols
- From: Matt Neuburg <email@hidden>
- Date: Wed, 02 Jun 2010 11:27:23 -0700
- Thread-topic: nibs don't respect protocols
I'm moving this over from Cocoa-Dev, so if you have the feeling you've seen
this before, that's why.
I'm struck by the following sort of situation. A UIApplication's delegate
property is defined as an id <UIApplicationDelegate>. But if I hook up the
UIApplication proxy object in a nib to another instance as its delegate, and
if that other instance does _not_ formally adopt UIApplicationDelegate,
there seems to be no penalty: the nib doesn't complain, and the app runs
fine.
So... Are nibs just ignorant of protocols? This feels like a bug. If you try
to hook up an outlet to the wrong type (e.g. a UILabel instead of a declared
UITextField), you can't; Interface Builder won't let you. Well, a class that
doesn't declare conformance to UIApplicationDelegate *is* the wrong type for
UIApplication's delegate; yet Interface Builder *does* let you. In that
case, what's the point of having the protocol at all?
I'd be willing to file a bug but I think I'd like some encouragement
first... :) m.
--
matt neuburg, phd = email@hidden, <http://www.tidbits.com/matt/>
A fool + a tool + an autorelease pool = cool!
AppleScript: the Definitive Guide - Second Edition!
http://www.tidbits.com/matt/default.html#applescriptthings
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden