Yay, it works! Thanks! And ripping out the relevant code from
Performer wasn't hard at all. In fact, Switching to QCRenderer
allowed my NSWindow subclass to do all the heavy lifting. There does
not appear to be any downside.
At 12:32 AM +0200 5/29/06, arjen wrote:
i'm using the display link and a callback function to render each frame.
this way the rendering gets triggered from another thread.
At 7:34 PM -0700 5/29/06, Pierre-Olivier Latour wrote:
You can use a QCRenderer to render the composition from a separate
thread. See the /Developer/Examples/Quartz Composer/Performer sample
code for a CVDisplayLink based case.
Ack, at 5/29/06, Pierre-Olivier Latour said:
I'm wondering if there are any downsides other than the amount of
initial setup work done when using QCRenderer.
there should be no downside, it's pretty using the QC engine directly
--
Sincerely,
Rosyna Keller
Technical Support/Holy Knight/Always needs a hug
Unsanity: Unsane Tools for Insanely Great People
It's either this, or imagining Phil Schiller in a thong.
_______________________________________________
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
