What is the proper way to insure that the animation updates as fast
as possible? The alternative seems to set up your own OpenGL
context and create your own QCRenderer.
As far as I've seen this is the only alternative. Possibly creating
the layer on a separate thread? Perhaps then the timer will also live
on that thread. (I've honestly not worked with CA extensively in a
threaded environment to know the pitfalls that await you there).
Is there a way to grab the renderer from a QCCompositionLayer and
put it in its own thread? Or, is the best way to brute force it and
go back to the manual way of setting up a QCCompositon in an OpenGL
context.
There's no officially supported way to get a renderer from the layer.
you can get its context (-renderingContext private method), but that's
not particularly helpful. So Tthe latter, while requiring a bunch
more work, might be a better solution (assuming that the timer isn't
tied to the creating thread, mentioned above).
_______________________________________________
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
This email sent to email@hidden
