Re: Which thing should be an IBOutlet?
Re: Which thing should be an IBOutlet?
- Subject: Re: Which thing should be an IBOutlet?
- From: Roland King <email@hidden>
- Date: Wed, 12 Dec 2012 06:23:58 +0800
On 12 Dec, 2012, at 6:02 AM, Tom Davie < email@hidden> wrote: The ivar shouldn't even be part of the public interface:
@interface Blah
@property (assign) IBOutlet Thing *thing;
@end
Bob
Agreed. I usually make a readonly property in the public header and then a class continuation that makes it read-write in the .m file. Not strictly necessary, the NIB loading system is undeterred by such niceties and will happily set instance variables if it can't find a property setter to use, but I like to be explicit, and sometimes the readwrite properties come in handy in the implementation. I always put ivars in the @implementation now, it's much tidier.
|
_______________________________________________
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