On Apr 22, 2009, at 6:24 PM, Ulai Beekam wrote:
So I really must make a custom field editor to accomplish on-the-fly
validation (i.e. disallowing on-the-fly invalid characters)?
It is not your only choice, but it is probably the best choice.
Another poster suggested using
On Apr 23, 2009, at 2:25 PM, Lee Ann Rucker wrote:
It is not your only choice, but it is probably the best choice.
Another poster suggested using isPartialStrignValid of the formatter,
but I have tried this in the past and run into undo issues,
particularly when using it to filter input. The
From: Keary Suska [cocoa-...@esoteritech.com]
Sent: Thursday, April 23, 2009 2:04 PM
To: Lee Ann Rucker
Cc: Cocoa-Dev (Apple)
Subject: Re: Bindings making NSNumberFormatter strange
On Apr 23, 2009, at 2:25 PM, Lee Ann Rucker wrote:
It is not your only
Hi,
I have an (editable) NSTextField with an NSNumberFormatter attached to it. The
text field is bound to some other numerical property (if you want to test this,
you can just make a simple AppController and put the @property(readwrite) int
foo; inside it, and bind the text field to
From: ulaibee...@hotmail.com
To: cocoa-dev@lists.apple.com
Date: Wed, 22 Apr 2009 15:26:51 +
Subject: Bindings making NSNumberFormatter strange
Hi,
I have an (editable) NSTextField with an NSNumberFormatter attached to it.
The text field is bound to some other numerical property
On Apr 22, 2009, at 3:57 PM, Ulai Beekam wrote:
To elaborate, when not using bindings, the default behavior of text
fields with a number formatter is that when a user tries to enter
abc in it, the text field refuses to lose focus and makes a
beeping sounds.
However, when the text field's
-dev@lists.apple.com
From: cocoa-...@esoteritech.com
To: ulaibee...@hotmail.com
Subject: Re: Bindings making NSNumberFormatter strange
Date: Wed, 22 Apr 2009 16:46:12 -0600
On Apr 22, 2009, at 3:57 PM, Ulai Beekam wrote:
To elaborate, when not using bindings, the default behavior of text
On Apr 22, 2009, at 6:24 PM, Ulai Beekam wrote:
So I really must make a custom field editor to accomplish on-the-fly
validation (i.e. disallowing on-the-fly invalid characters)?
I suppose I could do a custom field editor and override keyDown:,
checking for characters in [NSCharacterSet
