Re: IBOutlet to different classes, conditional build
Re: IBOutlet to different classes, conditional build
- Subject: Re: IBOutlet to different classes, conditional build
- From: Graham Cox <email@hidden>
- Date: Fri, 25 Feb 2011 09:04:40 +1100
On 25/02/2011, at 7:16 AM, Trygve Inda wrote:
> I am guessing IB is reading the MyClass.m which has both .h files imported
> with #ifdef
I don't think this is true - I have sometimes defined the header for a class and then set up the interface in IB using that header before I've even written a line in the .m file. IB seems quite happy, though at that point XCode wouldn't be if I tried to compile.
I'm not sure why you're even doing this. Just keep the two .m files totally separate, reading their own header file as is the usual case. If there's code common to both that you are uncomfortable duplicating, move it into a common helper class used by both.
--Graham
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden