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: Thu, 24 Feb 2011 13:08:36 +1100
On 24/02/2011, at 1:00 PM, Trygve Inda wrote:
> I could of course combine AppControllerUnique and PaneControllerUnique and
> call it ControllerUnique with #ifdefs to split the code, but there is no way
> to make an IBAction available in only one version... Since IB does not
> recognize the #ifdef which would prevent a Sparkle IBAction from showing up
> in the AppStore nib (even though the code could be compiled out.
Sorry, I'm not really understanding what the difficulty is.
Why not just have a combined set of actions, and wire them up in one nib one way, and in the other nib another way. Unused action methods are not a problem, are they? It will save literally a few bytes, so why sweat it?
--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