abortEditing for NSTableView broken on Jaguar
abortEditing for NSTableView broken on Jaguar
- Subject: abortEditing for NSTableView broken on Jaguar
- From: Evan Gross <email@hidden>
- Date: Sun, 04 Aug 2002 21:28:46 -0400
Hi,
On Jaguar (6C115), I've discovered that calling -abortEditing when a cell is
being edited in either a NSTableView or NSOutlineView no longer works
properly (bug filed, #3011588, "6c106 AppKit/NSTableView/NSOutlineView - [tv
abortEditing] causes crash"). It appears to release the dataCell, and
subsequent attempts to edit a cell can crash or cause other "bad things" to
happen.
This is easily reproduced in the DragNDropOutlineView AppKit sample by
adding a new item to the Operations menu attached to an action method that
simply calls [outlineView abortEditing], then choosing that item while
editing a cell, then double-clicking a cell to (attempt to) start editing.
If you run from PB with zombies turned on, you get this message:
DragNDropOutlineView[2057] *** *** Selector 'retain' sent to dealloced
instance 0x148c7d0 of class ImageAndTextCell.
I know I can use [window endEditingFor:tv] when I have to force editing to
stop, but this will attempt to validate editing (calling -setObjectValue) -
not the same thing as aborting editing.
There are times I need to abort instead of validate. Is there some other way
to accomplish this (or some work-around to get abortEditing to work)?
I see that a number of other folks implement doCommandBySelector and call
abortEditing when the selector is cancel: (also something I'm doing), and
they are likely affected as well (can someone else verify this?)...
Thanks,
Evan Gross
Rainmaker Research Inc.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.