In <OTidndWhkvX6IPuiXTWc-gspeakeasy.net> Paul Forgey wrote:If you believe the problem is that you're calling reloadData *during*> I've got two very similar things going on in both an NSOutlineView and
> an NSTableView. If the user edits the text in the leftmost column,
> this changes the key in a dictionary, which can cause the data to be
> reordered. If this happens in outlineView:setObjectValue:
> forTableColumn:byItem, I send a reloadData: to the NSOutlineView
> instance after the data used by the data source has been changed.
> In an NSTableView, this works fine. In an NSOutlineView, this causes
> a crash sometime after setObjectValue: has returned. I've checked and
> re-checked my data source. Especially since an NSTableView works just
> fine, is there a known problem or limitation that isn't doented
> about doing this in an NSOutlineView? If there's something else I
> need to do instead, what is it?
setObjectValue, then you can test that hypothesis by calling reloadData *
after* setObjectValue has returned. You can arrange that easily through
delayed execution. m.
matt neuburg, phd = [email]matttidbits.com[/email], [url]http://www.tidbits.com/matt[/url]
REALbasic: The Definitive Guide! 2nd edition!
Subscribe to TidBITS. It's free and smart.