Re: [NSCFNumber intValue]: unrecognized selector
Re: [NSCFNumber intValue]: unrecognized selector
- Subject: Re: [NSCFNumber intValue]: unrecognized selector
- From: j o a r <email@hidden>
- Date: Fri, 26 Sep 2008 17:38:28 -0700
On Sep 26, 2008, at 4:36 PM, Steve Rossi wrote:
Yes, that is correct. A separate thread is spawned which updates the
model - consequently driving UI updates based on KVO notifications.
It is the only thread that is updating the model - the main thread
does very little except respond to fairly minimal UI events.
It works very reliably it seems ... except on these occassions when
the OpenPanel is opened from the main thread.
That might appear to be the case on your machine, on this version of
your application, and on this version of Mac OS X - But as soon as you
change any of these variables, it might well start to fall apart.
I can think through whether I really need that separate thread. But
is there a way to make the model updates from the 2nd thread safe?
If you're doing blocking work, having it on a separate thread is
probably a good thing - But you need to forward your UI updates to the
main thread. That's typically easy to do using
"performSelectorOnMainThread:"
j o a r
_______________________________________________
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