Re: NSOperation communicating progress?
Re: NSOperation communicating progress?
- Subject: Re: NSOperation communicating progress?
- From: Todd Heberlein <email@hidden>
- Date: Mon, 04 Feb 2013 17:06:21 -0800
On Feb 4, 2013, at 3:16 PM, Graham Cox <email@hidden> wrote:
> You have heard of performSelectorOnMainThread? Might simplify your code substantially.
I was following Apple's "Concurrency Programming Guide", and I don't think it is in there. I've gone back and used it now to call the clean-up code.
On Feb 4, 2013, at 3:09 PM, Mike Abdullah <email@hidden> wrote:
> Out of interest, is there any reason why you're shying away from blocks here? They make this sort of code much simpler to write.
Baby steps. I'm still not fully comfortable with blocks (even though I know it is very popular now). I guess I just need to get past the fears of its strange (to me) lexical scoping. It is probably triggering some PTSD symptoms from my short period of programming in LISP.
Todd
_______________________________________________
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