The only reason a controller would return NO for commitEditing is that
one of *its* editors refused to commitEditing. Up the chain somewhere,
there must be a textField bound to the controller or one of its detail
controllers and a formatter or validation method is saying that the
current value is unacceptable.
commitEditing is just supposed to do it, or not. The caller shouldn't
have to know why committing didn't work. The receiver should be
communicating to the user that editing is ending – and in your case
that editing can't be ended with the current value.
I can't suggest more on how to debug this without know more about you
app.
On Oct 22, 2008, at 3:15 PM, Chris Idou wrote:
I'm calling commitEditing on a NSObjectController, and its returning
NO, for no apparent or obvious reason.
How am I supposed to debug these things?
--------------------------
RONZILLA
_______________________________________________
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]
