Re: textShouldNotEvenThinkAboutEndEditingIfItKnowsWhatIsGoodForIt
Re: textShouldNotEvenThinkAboutEndEditingIfItKnowsWhatIsGoodForIt
- Subject: Re: textShouldNotEvenThinkAboutEndEditingIfItKnowsWhatIsGoodForIt
- From: Scott Stevenson <email@hidden>
- Date: Thu, 2 Dec 2004 12:18:25 -0800
On Dec 2, 2004, at 8:00 AM, Graham J Lee wrote:
However I've noticed that if a user enters an out-of-range number and
then, rather than hitting return or tab, just presses e.g. a button,
then the method invoked by that button does run and does see the
current intValue of the field and hence crashes and burns. Now I've
just noticed the existence of NSStepper, but before I [i]dig into that
[ii]change my UI as a result, is there a way of making sure that the
NSTextField's content is *definitely* validated before it is used?
Key-value validation?
http://developer.apple.com/documentation/Cocoa/Conceptual/
KeyValueCoding/Concepts/Validation.html
Works well with bindings.
- Scott
--
http://treehouseideas.com/
http://theobroma.treehouseideas.com/ [blog]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden