Re: using performSelectorOnMainThread to update the ui
Re: using performSelectorOnMainThread to update the ui
- Subject: Re: using performSelectorOnMainThread to update the ui
- From: Kyle Sluder <email@hidden>
- Date: Sun, 15 Nov 2009 17:31:06 -0800
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?
If you are using garbage collection, correct. Even simple stores and
loads into instance variables might block if the collector is running.
(It gets even more complicated when you have per-thread garbage
collection.)
> if you cant notify your ui from the render thread, then is the only
> other option writing information to shared data and continually
> polling it from the ui? ( i cant think of any other way off the top of
> my head )
It is possible to write non-blocking concurrent code. See OSAtomic.h.
This is not an easy thing to do.
--Kyle Sluder
_______________________________________________
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