Re: IBOutlet to different classes, conditional build
Re: IBOutlet to different classes, conditional build
- Subject: Re: IBOutlet to different classes, conditional build
- From: Trygve Inda <email@hidden>
- Date: Thu, 24 Feb 2011 02:41:45 +0000
- Thread-topic: IBOutlet to different classes, conditional build
>
> On 24/02/2011, at 1:16 PM, Trygve Inda wrote:
>
>> Hmmm.. Mine was rejected until I totally removed all the methods too.
>
>
> That doesn't seem reasonable. Did you try explaining that the actual code that
> handles Sparkle updates has been removed?
>
> When I was initially rejected (on an unrelated issue) I explained what was
> actually happening and they accepted my explanation and continued the review.
>
> But, if you really need to, conditionally dropping out that code for one of
> the targets is easy.
>
> --Graham
I had to totally remove it.
Now, I have it conditionally compiling the code, but it my AppStore nib one
of my instantiate objects is my AppDelegate because it shares code with the
Retail version, the class has:
-(IBAction)doSparkleStuff:(id)sender;
Even though this code is #ifdef'd out in the AppStore build, it seems to be
a problem that the nib refers to it (it is not hooked up, but is part of the
class since there is no way to make IB ignore this method definition.
_______________________________________________
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