Never mind. I got it working. When you reach a certain point, you
should just walk away from a problem I guess.... Setting the sheet's
first responder to nil is now working, but I do it when the button is
pressed, not in my sheet callback method.
On Mar 25, 2008, at 7:59 AM, Jeff LaMarche wrote:
Okay, I know I've had this problem before a couple of years ago when
Core Data was fairly new, but searching the archives didn't turn
anything up and I think I've just been looking at it too long - it's
probably something really obvious, but... I have a custom sheet
with several text fields. These text fields are bound to attributes
of an outline view's selection binding. When a button is pressed, it
drops the sheet down to let them edit additional properties of the
selected entity in a sheet, and that all works great.
Except, the field that the cursor is in when the user presses okay
doesn't get saved. Now, if I tab out of the field or click on
another field before hitting okay, it works fine and saves the
changed value. It seems that I have to tell the field to somehow
commit its changes, but I'm not sure how to do that. I've tried
having the field resignFirstResponder, and have tried setting the
sheet's first responder to nil, and neither changed my results.
_______________________________________________
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 [EMAIL PROTECTED]
