Am 21.12.2008 um 16:53 Uhr schrieb Andre Masse:
I'm using a similar design, not by locking the fields but setting a
"isDirty" flag in the model after the user start editing the record.
That's exactly the point I was trying to make. Editing should be a
distinct mode, consciously chosen by the user. That way it is not a
surprise, that ending the mode also has to be confirmed.
This hole problem arises when I want to "disable" the master view. I
thought using -selectionShouldChangeInTableView will serve this
purpose
What about
- (NSIndexSet *)tableView:(NSTableView *)tableView
selectionIndexesForProposedSelection:
(NSIndexSet*)proposedSelectionIndexes
If all else fails, you can always subclass the view and overwrite -
mouseDown: and/or keyDown:.
Andreas
_______________________________________________
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 arch...@mail-archive.com
