Can you imagine of any kind of work around? I can't really use
HIMovieView since compositions rendered this way don't accept input
keys and also, they randomly deadlock the application which is just
slightly worse than a pause when closing a menu.
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.
I was about to try this after arjen mentioned it, but it requires a
bit of code refactoring to use. Pity I can't gut that particular
piece of QCView.
Be careful when accessing the QCRenderer from several threads at once
But is it ok having multiple CVDisplayLinks, one for each QCRenderer
(say there being a max of 5 QCRenderers on screen at once?). As in,
is there a global state shared between QCRenderers that might need
some lovin?
Since this is my very first time ever using Quartz Composer, since
I've already rewrote the Quartz Composer display code twice (once in
HIMovieView, once in QCView when HIMovieView kept locking the
application randomly) I'm wondering if there are any downsides other
than the amount of initial setup work done when using QCRenderer.
--
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
