Re: Is there another way to do performSelectorOnMainThread?
Re: Is there another way to do performSelectorOnMainThread?
- Subject: Re: Is there another way to do performSelectorOnMainThread?
- From: Aurélien Hugelé <email@hidden>
- Date: Thu, 29 Jun 2006 16:32:38 +0200
You often have to use NSInvocation because if your are passing non
object parameters... passing a NSNumber encapsulated in a dictionary
is what i call heavy-weight ;)
Apple uses a lot of performSelectorAfterDelay with NSInvocation
invokeWithTarget in AppKit...
Aurelien
On 28 juin 06, at 21:01, Alan Pearson wrote:
I have always just created a proxy method on self that I call using
performSelectorOnMainThead. I pass the proxy method a dictionary
of the objects for the real call I want to make on the main
thread. It extracts the items from the dictionary and invokes the
selector.
I'll bet you could also achieve this with NSInvocation, though that
seems a bit heavy-weight.
Alan Pearson - email@hidden
http://www.sonzea.com/
On Jun 28, 2006, at 11:55 AM, Scott Andrew wrote:
I want to user performSelectorOnMainThread however i want to pass
in more than one object (2 actually) but
performSelectorOnMainThread only supports one. Is there a way to
this besides using an arrray as my object?
Scott Andrew
_______________________________________________
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
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40gumitech.com
This email sent to email@hidden
_______________________________________________
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