| |||
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
Cheers, -C
On 27/09/2005, at 9:31 AM, Christopher Hunt wrote:
Right - thanks. How about calling setValue:forInputKey: prior to renderAtTime:arguments in my own Objective-C loop - effectively the same effect as looping within QC. This sounds like a less resource- hungry solution than creating many QCRenderer instances.
Kind regards, Christopher
On 27/09/2005, at 9:16 AM, Pierre-Olivier Latour wrote:
That's actually a bug in Render in Image we are aware of, and I don't think there's anything you can do to work around it.
_______________________________________________ Do not post admin requests to the list. They will be ignored. Quartzcomposer-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/quartzcomposer-dev/email@hidden
| References: | |
| >Render In Image and params (From: Christopher Hunt <email@hidden>) | |
| >Re: Render In Image and params (From: Pierre-Olivier Latour <email@hidden>) | |
| >Re: Render In Image and params (From: Christopher Hunt <email@hidden>) | |
| >Re: Render In Image and params (From: Pierre-Olivier Latour <email@hidden>) | |
| >Re: Render In Image and params (From: Christopher Hunt <email@hidden>) |
| Home | Archives | FAQ | Terms/Conditions | Contact | RSS | Lists | About |
Visit the Apple Store online or at retail locations.
1-800-MY-APPLE
Contact Apple | Terms of Use | Privacy Policy
Copyright © 2007 Apple Inc. All rights reserved.