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:16:49 +0000
- Thread-topic: IBOutlet to different classes, conditional build
>
> On 24/02/2011, at 1:05 PM, Trygve Inda wrote:
>
>> And this supercalss is instantiated in the nib, won't this appear in the nib
>> somewhere even if it does not hook to the action? I can't have it that way
>> (at last if I want to call the methods anything containing "sparkle".
>
>
> Why not? This won't cause any conniptions for App Store approval. If the
> Sparkle framework is not there, and the Menu commands are removed, these
> methods are never called. Their presence in your binary is not an issue.
>
> The app I have on the App Store has the sparkle delegates remaining in place,
> just no framework, sparkle instance in MainMenu.nib or menu commands.
>
> --Graham
>
Hmmm.. Mine was rejected until I totally removed all the methods too.
Now I am trying to recombine the projects.
_______________________________________________
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