Re: Order of resulting selector invocations from performSelector
Re: Order of resulting selector invocations from performSelector
- Subject: Re: Order of resulting selector invocations from performSelector
- From: "Hamish Allan" <email@hidden>
- Date: Fri, 14 Mar 2008 15:25:10 +0000
On Fri, Mar 14, 2008 at 8:52 AM, Stuart Malin <email@hidden> wrote:
> If I have my code issue multiple
> performSelectorOnMainThread:someSelector :waitUntilDone:NO
>
> is there any guarantee about the resulting order of execution?
> (please note that I passed in NO for waitUntilDone)
>
> That is, if for the same object, if performSelectoronMainThread is
> executed twice, first for selectorA, and then for selectorB, can I
> reasonably expect that selectorA will be invoked before selectorB ?
I had the same question answered recently on this list:
http://lists.apple.com/archives/cocoa-dev/2008/Feb/msg02280.html
Best wishes,
Hamish
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden