Re: tableView:setObjectValue:forTableColumn:row: not called when button pressed
Re: tableView:setObjectValue:forTableColumn:row: not called when button pressed
- Subject: Re: tableView:setObjectValue:forTableColumn:row: not called when button pressed
- From: "Sean McBride" <email@hidden>
- Date: Thu, 19 Nov 2009 22:00:30 -0500
Scott Ribe (email@hidden) on 2009-11-19 8:53 PM said:
>Table with editable columns, user is editing a cell, user is done, user
>clicks "Save" button. User's last change is lost because
>tableView:setObjectValue:forTableColumn:row: is not called. It is only
>called if the cell loses focus via the user tabbing out of the cell or
>clicking in some other editable cell. This behavior is 10.5 & 10.6--10.4 &
>10.3 worked as I expected them to, first user edit is processed, then
>button's action method.
If I understand you correctly, this is described in the 10.5 AppKit
Release Notes:
<http://developer.apple.com/mac/library/releasenotes/cocoa/
AppKitOlderNotes.html#X10_5Notes>
under the heading "Changes in NSDocument's Handling of Editors
Registered via Cocoa Bindings' NSEditorRegistration Informal Protocol"
>What's the workaround to get the user's last data entry when the "Save"
>button is clicked?
I guess you mean other than manually telling all NSControllers of all
windows to commitEditing? :) I've been meaning to figure out a nice
generic solution to this problem as well, but never did.
Sean
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden