Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

QCCompositionLayer Rendering Thread

I am having some issues where I have a QCcompositionLayer running in as a layer in one window where the animation is not rendering as fast as it should. I have a second window where I am updating a the location of an nsscrollview with quartz drawings. I believe the problem to be the fact that in a QCCompositionLayer, the composition is run on a nstimer from the main thread, rather in its own thread. UI updates on the main thread are causing the rendering to slow down.

I have tried everything to get this to work properly. It seems that QCView may have the same issue. So it seems that in all the ease of using QCCompositionLayer, there may be a draw back in that the rendering thread may not execute efficiently in multi threaded apps with lots of updates to the UI. 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.

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.

Thanks

Josh
_______________________________________________
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


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.