Re: Quartz.framework Catch-22 on Panther

2008-04-17 Thread Michael Ash
On Thu, Apr 17, 2008 at 10:13 AM, Nick Nallick <[EMAIL PROTECTED]> wrote: > I've been able to solve my problem by taking Quartz.framework out of my > project and loading QuartzComposer.framework directly at runtime with > NSBundle. For example: > > Instead of: > > QCRenderer* renderer = [

Re: Quartz.framework Catch-22 on Panther

2008-04-17 Thread Nick Nallick
I've been able to solve my problem by taking Quartz.framework out of my project and loading QuartzComposer.framework directly at runtime with NSBundle. For example: Instead of: QCRenderer* renderer = [QCRenderer alloc]; I have: static Class QCRendererClass = nil; i

Quartz.framework Catch-22 on Panther

2008-04-11 Thread Nick Nallick
I'm using the Cocoa class QCRenderer after testing for Tiger or later. This means I have to link to Quartz.framework which I do as a weak link so I can still start under Panther and test the system version before trying to instantiate QCRenderer. This worked fine when building on Tiger.