On 05.07.2008, at 15:17, David Duncan wrote:
To handle a case like this, you are going to have to create a bundle that you link against the 10.5 SDK and only load there. This bundle will contain your NSViewController subclass and allow you to conditionally call -setAccessoryView: on 10.4 and - addAccessoryViewController: on 10.5. This is a general pattern that you can use when you want to provide alternate functionality where it is a requirement to subclass and that subclass only exists on a newer version of the OS.
Or rather, you'll want to do this in a more OO approach, i.e. abstract your custom print panel stuff away into a class. The base class is linked into your app, and the loadable bundles implement subclasses of these. Your app simply uses these classes, and they take care of using view controllers etc. as needed.
You'd just load the appropriate bundle and instantiate its main class, then hand it the appropriate views or whatever makes sense.
Alternately, you could also implement your own version of NSViewController and the viewcontroller-based accessory view methods, and just load them on 10.4 to provide backwards compatibility, while your code can effectively assume it always uses the 10.5 APIs.
Cheers, -- Uli Kusterer "The Witnesses of TeachText are everywhere..." http://www.zathras.de _______________________________________________ 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 [EMAIL PROTECTED]
