I'm getting an uncaught crash when dragging out the last item in the column in NSBrowser to another app (Finder), which will move the file it represents out. I set a breakpoint
//Item is gone..already been removed from our collection
[self.browser reloadColumn:0]
Now right after that, I can get a call in the browser will display cell at row column via my delegate.... with the out of bounds index in the collection (the one I just removed).
Now if I call self.browser loadColumnZero I avoid the crash, but I will lose the scroll position...ect.
Well, if I take out the browser:willDisplayCell:atRow:column: a call to reloadColumn: won't cause a crash when removing the last item. It is the will display cell method is causing the trouble by passing me the out of bounds index.
I can have my cell subclass configure its display when its objectValue is set instead, but I still need the will display cell method to set the menu property on the cell objects. I suppose I'd file a bug report but since the NSCell stuff is deprecated my bet is that this would be unlikely to get fixed. Hope they move NSBrowser to a view based table view and give us a few more hooks into it.