>> ...If you're targeting 10.6 or later, you can use a dispatch queue (it's
>> fairly straight forward)...
>
> Are there any example exists about driving the rendering on this way?
I don't think so. It should be straightforward though, and not in any way
superior to a CVDisplayLink, so I don't know why anyone would bother for
on-screen live content. An offline renderer could perhaps benefit from a
dispatch queue.
My suggestion for using a dispatch queue was purely because it's easy.
[QCRenderer render]
turns into
dispatch_async(dispatch_get_global_queue(DISPATCH_QUEUE_PRIORITY_DEFAULT, 0), ^{
NSAutoreleasePool *pool = [NSAutoreleasePool new];
[QCRenderer render];
[pool drain];
});
(more or less - that's probably grossly oversimplifying and missing something
important - the linked technote says to not render on a non-creating thread,
and that's going to be difficult to ensure with Dispatch).
--
Christopher Wright
christopher_wri...@apple.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list (Quartzcomposer-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
