Re: using performSelectorOnMainThread to update the ui
Re: using performSelectorOnMainThread to update the ui
- Subject: Re: using performSelectorOnMainThread to update the ui
- From: Brian Willoughby <email@hidden>
- Date: Sun, 15 Nov 2009 21:08:56 -0800
You can still use ObjC outside your CoreAudio code, in the main
application. I suppose that's obvious, but I wanted to spell it out.
What I do is define a Standard C struct which contains all of the
variables needed to communicate between GUI and audio code. But I
pass the address of the struct, not the ObjC object. I also make
sure that the ObjC object does not get deallocated until all
CoreAudio callbacks are disconnected. This allows all CoreAudio code
to work with Standard C data that will not be freed.
Semaphores and Mach message, as mentioned before, and even GUI
polling are valid.
Brian Willoughby
Sound Consulting
On Nov 15, 2009, at 19:22, Aran Mulholland wrote:
thanks for the clarification, when i get around to it ill rewrite my
stuff in c or c++.
i had a feeling that objective C stuff was too good to be true :)
On Sun, Nov 15, 2009 at 2:25 PM, Aran Mulholland
<email@hidden> wrote:
does this mean that storing your data in objC data structures is a
no no?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden