Re: tableView:setObjectValue:forTableColumn:row: not called when button pressed

2009-11-24 Thread Scott Ribe
Thanks for the in-depth info. Maybe I missed something earlier in this thread, but I don't see why using the NSEditor protocol isn't a better solution. Well, I'm not using bindings, and I am using NSWindowController which does not implement the NSEditor protocol. This is a superior solution

Re: tableView:setObjectValue:forTableColumn:row: not called when button pressed

2009-11-21 Thread Quincey Morris
On Nov 20, 2009, at 21:15, Kyle Sluder wrote: On Nov 20, 2009, at 6:38 PM, Sean McBride cwat...@cam.org wrote: Quincey Morris (quinceymor...@earthlink.net) on 2009-11-20 6:34 PM said: ...the window controller could send 'commitEditing:' messages directly to text fields and other views

Re: tableView:setObjectValue:forTableColumn:row: not called when button pressed

2009-11-21 Thread Kyle Sluder
On Sat, Nov 21, 2009 at 12:07 PM, Quincey Morris quinceymor...@earthlink.net wrote: It occurs to me that perhaps the reason sending 'commitEditing:' to a text field doesn't work is that you need to send it to the field editor, not the text field itself? Or something like that. That makes

Re: tableView:setObjectValue:forTableColumn:row: not called when button pressed

2009-11-20 Thread Scott Ribe
If I understand you correctly, this is described in the 10.5 AppKit Release Notes: I'm not using bindings (and this app is not NSDocument-based) . My controller is a subclass of NSWindowController, which does not implement commitEditing. So as far as I can tell, this doesn't help me. --

Re: tableView:setObjectValue:forTableColumn:row: not called when button pressed

2009-11-20 Thread Scott Ribe
The crude approach of [[self window] makeFirstResponder: nil]; seems to work well enough. (I'd previously tried a couple of other things along those lines and failed.) -- Scott Ribe scott_r...@killerbytes.com http://www.killerbytes.com/ (303) 722-0567 voice

Re: tableView:setObjectValue:forTableColumn:row: not called when button pressed

2009-11-20 Thread Quincey Morris
On Nov 20, 2009, at 09:11, Scott Ribe wrote: The crude approach of [[self window] makeFirstResponder: nil]; seems to work well enough. (I'd previously tried a couple of other things along those lines and failed.) Maybe I missed something earlier in this thread, but I don't see why using the

Re: tableView:setObjectValue:forTableColumn:row: not called when button pressed

2009-11-20 Thread Sean McBride
Quincey Morris (quinceymor...@earthlink.net) on 2009-11-20 6:34 PM said: ...the window controller could send 'commitEditing:' messages directly to text fields and other views that implement the NSEditor protocol. Nope. Despite the docs, you can't send commitEditing to a textfield. See also:

Re: tableView:setObjectValue:forTableColumn:row: not called when button pressed

2009-11-20 Thread Kyle Sluder
On Nov 20, 2009, at 6:38 PM, Sean McBride cwat...@cam.org wrote: Quincey Morris (quinceymor...@earthlink.net) on 2009-11-20 6:34 PM said: ...the window controller could send 'commitEditing:' messages directly to text fields and other views that implement the NSEditor protocol. Nope.

tableView:setObjectValue:forTableColumn:row: not called when button pressed

2009-11-19 Thread Scott Ribe
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

Re: tableView:setObjectValue:forTableColumn:row: not called when button pressed

2009-11-19 Thread Sean McBride
Scott Ribe (scott_r...@killerbytes.com) 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