Re: performSelectorOnMainThread for a selector with a primitive argument
Re: performSelectorOnMainThread for a selector with a primitive argument
- Subject: Re: performSelectorOnMainThread for a selector with a primitive argument
- From: j o a r <email@hidden>
- Date: Thu, 16 Feb 2006 20:18:11 +0100
On 16 feb 2006, at 19.53, Eric Crichlow wrote:
Problem is, I can't see any way of forcing execution to the main
thread
other than performSelectorOnMainThread, but that method requires
that the
invoked selector take an object argument, but there are LOTS of
calls that
take a primitive type(s) as their argument(s).
Is there some solution that I'm completely missing?
In many cases your background threads triggers updates faster than
would make sense to display in the UI. So with that in mind, another
option is to update the data from the background thread - with
appropriate locking - and using the "performSelectorOnMainThread"
only as a way to notify the main thread that there are new data
available.
j o a r
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden