Thanks Pierre. To be clear, I am not using 0 for time value. The
solution I chose was to use a time value based on the current time
rather than using the time passed into the displayLink. That
solution works well, but I like your idea of saving the most recent
time value and reusing that if I'm not rendering from within the
displayLink.
-Chris
On Jul 12, 2007, at 12:28 AM, Pierre-Olivier Latour wrote:
The above is not complete because "renderAtTime:" doesn't know how
to handle a nil value for the time. I'm not sure what the best
solution is, so I decided to simply ignore the incoming time value
entirely. In renderAtTime:, here is what I changed:
I don't think you should be using 0 as if the composition is
currently rendering far in time, you're gonna have it jump backward
and this might affect performance.
Just store the time of the latest rendered frame and re-use it.
________________________________________________________
Pierre-Olivier Latour email@hidden
Quartz Composer Apple, Inc.
