Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

ThreadWorker return value

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

ThreadWorker return value

Subject: ThreadWorker return value
From: Greg Hoover <email@hidden>
Date: Wed, 13 Sep 2006 20:49:50 -0700

I'm using the ThreadWorker class by Robert Harder for a variety of MT tasks in my app. I've discovered that if one of my worker threads returns an NSAttributedString object, the whole app hangs, but if it returns an NSArray object, the app works beautifully. The calls are all identical and I haven't modified the functionality of the methods -- the only thing I've changed is the returned object. I've also tried adding superfluous retain calls to the returned objects, thinking that the object was possibly being deallocated before it could be used, but this didn't solve the problem. Does anyone have experience with this? Can certain objects not be distributed across threads/tasks/etc?

Thanks. Greg _______________________________________________ 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 Prev by Date: String in NSRect Next by Date: Re: Threading and NSApplicationMain() Previous by thread: Re: String in NSRect Next by thread: GCOV question Index(es): Date Thread