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:55:04 +0000
- Thread-topic: IBOutlet to different classes, conditional build
>
> On 24/02/2011, at 1:41 PM, Trygve Inda wrote:
>
>> -(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.
>
>
> If the problem is the presence of the word 'sparkle' in the method name can't
> you just rename it to something innocent?
>
> I still find it hard to accept that this is why they rejected the app. Are you
> sure it wasn't something else? You can ask for clarification.
>
> --Graham
I did inquire about the rejection... it was because of the mention of
sparkle.
I think I'll just change the name... They did accept it after I did that but
now I have two projects (appstore and retail) and I am putting them back
into one project because 98% of the code is the same... I just need to keep
sparkle totally unmentioned it seems... Even as an unused class action
method.
_______________________________________________
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