I played around with what Uli seemed to be hinting at, and indeed it does seem that NSOutlineView is not particularly thread safe. If you update the content for the NSTreeController that is the data source for the outline view outside of the main thread it blows up as I described, and does so pretty consistently. Once I forced the update to be done only on the main thread the issue went away.

Jeff

On Oct 3, 2008, at 10:48 PM, Jeff Wilcox wrote:

Not explicitly, but maybe. This seems to be taking place when the content for the NSTreeController is changing (explicitly) in one thread, causing a reload in the outline view, and in another thread the NSOutlineView's drawrect is getting called. I can't say for sure that this accounts for all of the cases but that seems like a common theme.

Thoughts?

On Oct 3, 2008, at 6:10 PM, Uli Kusterer wrote:

On 04.10.2008, at 03:00, Jeff Wilcox wrote:
I seemed to be able to make this go away by subclassing the outline view and locking it down before starting a reload or evaluating the number of rows (found mostly by lots or trial and error) with the following:


Wait, you're not calling numberOfRows and reloadData on an outline view from another thread, are you?

Cheers,
-- Uli Kusterer
"The Witnesses of TeachText are everywhere..."
http://www.zathras.de






_______________________________________________

Cocoa-dev mailing list ([email protected])

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:
http://lists.apple.com/mailman/options/cocoa-dev/cocoa%40logicpoet.com

This email sent to [EMAIL PROTECTED]

_______________________________________________

Cocoa-dev mailing list ([email protected])

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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to [EMAIL PROTECTED]

Reply via email to