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.
OK, so how about if I create many QCRenderer instances with the
same qtz file instead of looping within qtz. I suspect that
looping in qtz may be more efficient, but if creating many
QCRenderers isn't a big issue, I'm happy with that approach. In
fact, creating many QCRenderers makes life a little easier for me.
In summary, if I create 200 QCRenderer instances for the same qtz
file then are things going to be terribly inefficient?
QCRenderer instances do not share data, so depending on
compositions, it might be pretty inefficient
