Yep, its that situation where you should render your QCRenderer objects on a separate thread (or the main thread related events will blocks the rendering), NSThread or CVDisplayLink. However, you should care when using QCRenderers on different thread: http://developer.apple.com/library/mac/#qa/qa1538/_index.html
On Jan 13, 2012, at 5:39 PM, Detour wrote: > This one goes back a way, but using a nib file and standard UI elements, and > clicking & holding any of them pauses rendering. Is this one of those > situations where I'd need to have the QCRenderer on a separate thread? I'm > not very familiar with how threading works in Coca and not sure I want to get > into that. In the past I've worked around it by coding custom UI elements as > graphics, but that's a lot of extra work. Is there a proper way to work with > nibs/standard controls and a full screen QCRenderer? > > _______________________________________________ > 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/info%40cogevj.hu > > This email sent to i...@cogevj.hu
_______________________________________________ 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
