NSOutlineView assertion failures
NSOutlineView assertion failures
- Subject: NSOutlineView assertion failures
- From: Jeff Wilcox <email@hidden>
- Date: Fri, 3 Oct 2008 18:00:50 -0700
I am suddenly having a load of issues with NSOutline view failing with
the following assertion:
Assertion failure in -[NSOutlineView
_expandItemEntry:expandChildren:startLevel:](), /SourceCache/AppKit/
AppKit-949.35/TableView.subproj/NSOutlineView.m:1003
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:
- (NSInteger)numberOfRows{
@synchronized(self){
return [super numberOfRows];
}
}
- (void)reloadData{
@synchronized(self){
[super reloadData];
}
}
Here is one of many signatures that it yields (back trace abbreviated)
#0 0x94893e17 in objc_exception_throw ()
#1 0x918f7f2b in +[NSException raise:format:arguments:] ()
#2 0x95affac5 in -[NSAssertionHandler
handleFailureInFunction:file:lineNumber:description:] ()
#3 0x9038363f in -[NSOutlineView
_expandItemEntry:expandChildren:startLevel:] ()
#4 0x903833f6 in -[NSOutlineView _expandItemEntry:expandChildren:] ()
#5 0x90383314 in -[NSOutlineView numberOfRows] ()
#6 0x9022dfa9 in -[NSTableView rectOfRow:] ()
#7 0x9022de28 in -[NSOutlineView rectOfRow:] ()
Any ideas? This is driving me a little crazy and delaying my next
release. I finally got the work around I mentioned seemingly stable
for a couple of outline views but then other ones started showing the
same issue. I don't feel confident enough about the side effects of
the work around above to use it pervasively.
Thanks
Jeff
_______________________________________________
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