It is going to be 10.6+, so I think I could use a dispatch queue. Are there any examples?
On Jan 13, 2012, at 8:43 AM, Christopher Wright 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? > > > Yes - when you use NSTimer, it will by default happen on the main > thread/queue. This has all the benefits of trying to share time with Event > Handling and UI Drawing (including focus stuff like what you've noticed), > which is rarely what you want. > > If you're targeting 10.6 or later, you can use a dispatch queue (it's fairly > straight forward), or if you're targeting 10.4 (I think? 10.5 for sure) or > later you can use a CVDisplayLink (this is the recommended way, and there > should be a few examples of how to set this up). One gotcha is that the > movie player is often unhappy on non-main-thread, so that might require some > extra massaging. > > -- > Christopher Wright > [email protected] > > >
_______________________________________________ Do not post admin requests to the list. They will be ignored. Quartzcomposer-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com This email sent to [email protected]
