Re: Tuning KVO validation.
Re: Tuning KVO validation.
- Subject: Re: Tuning KVO validation.
- From: Óscar Morales Vivó <email@hidden>
- Date: Wed, 25 Feb 2004 15:03:23 +0100
It may not allow it, but it should. There should be a mechanism (maybe
there is and I just haven't found it) to capture the model's validation
errors and act on them. Otherwise I'm doing redundant validating, which
is bad style and makes the code harder to maintain.
On 25 Feb 2004, at 14:47, Allan Odgaard wrote:
On 25. Feb 2004, at 14:42, Sscar Morales Vivs wrote:
And I don't have anything against that behaviour, as I already
understood why it is set so. I just want to be able to specify the
one I want too.
Then implement textView:shouldChangeTextInRange:replacementString: in
your delegate (of the field editor) and let it return NO (and do
NSBeep()) when you see an illegal string.
The binding system nor the formatter system is made for that.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.