> > On 25/02/2011, at 11:17 AM, Trygve Inda wrote: > >> So what file would I define this protocol in... > > Another header? > >> The two .h files for the >> unique classes? > > No - just #import the protocol into these headers. > >> It'd be nice if IB let me define a class two different ways and linked only >> to the header file (which I should be able to replace in IB without a >> "superclass mismatch warning" > > Well it doesn't so you have to find another solution. I don't think the case > you're trying to make work is common, and there are nicer ways to solve it > than conditional compiles - such as the one I've been trying to tell you. > > --Graham > > >
One thought I had is to just build two versions of the PrefPane... My retail one would work in System Preferences as it always has... And for the other I would build a wrapper app that just loaded the pref bundle (which would be #ifdef'd to not contain Sparkle and such). Do you think an app that loads a code bundle from within it's own Resource folder would be rejected? I currently have two separate app bundles launched from within the Resources folder so that isn't much different. These two apps are not signed but the app of course is. I know I'd have to sign the app wrapper bundle, but not sure about the loadable bundle... It'd make things much easier I think. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
