I've been playing with an outline view bound to an NSTreeController, based on the great SourceView example. My tree controller is populated with a tree of network devices, categorized by type. As things come on and off the network, entries are added to the appropriate category, and all works beautifully.
I've been trying to do some stress testing, adding and removing the same network instrument (watching it pop in and out of existance in the NSOutlineView). However, I am periodically getting a EXC_BAD_ACCESS, which I can't seem to track down. The tree controller (or perhaps the NSOutlineView) seems to be generating NSLog entries: "unexpected state: found the same object more than once, but can't find the treenode for it" I'm not sure if this: a) indicates IP address conflicts that cause the same IP address to attempt to be added multiple times - or - b) my add/remove test is leaving some vestige of the node behind. I have confirmed that the node does get removed via a call to "removeObjectIdenticalTo" call to the NSMutableArray, and that the count of the array drops by one. Has anyone seen this "unexpected state" error when working with tree controllers/NSOutlineView ? Thanks, -Brent _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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]
