Re: Bug in NSFormatter (again)?
Re: Bug in NSFormatter (again)?
- Subject: Re: Bug in NSFormatter (again)?
- From: Chris Kane <email@hidden>
- Date: Sun, 5 Aug 2001 13:23:24 -0700
These wouldn't be bugs in NSFormatter, btw. They would be bugs in
whoever is using the formatter. For example, an NSFormatter doesn't
call it's own -isPartialStringValid:.... methods (unless your subclass
does), it's the NSCells or whatever else is using the formatter that may
be using the formatter incorrectly, or passing the wrong arguments to
the formatter methods, or mis-setting the caret/selection after
formatting, etc.
Chris Kane
Cocoa Frameworks, Apple
On Sunday, August 5, 2001, at 04:54 AM, Bill Cheeseman wrote:
I haven't gotten much in the way of a reply to my NSFormatter
inquiries, so
let me make it really simple.
Sometimes, when I attach a custom formatter to a text field and use the
new,
longer NSFormatter isPartialStringValid:... Method, the blinking
insertion
point disappears or turns weird after I use the Delete key to delete the
last character from the field. Yet no amount of debugging has revealed
anything wrong with the values for the string in the field or the
field's
insertion point, both of which are returned by indirection in
parameters to
the method. The error occurs even when the custom formatter does
NOTHING to
these parameters, but simply returns YES to indicate acceptance of the
value
typed by the user.
I therefore suspect a bug in this new method of NSFormatter. Can anybody
confirm or disprove this?
--
Bill Cheeseman - email@hidden
Quechee Software, Quechee, Vermont, USA
The AppleScript Sourcebook - www.AppleScriptSourcebook.com
Vermont Recipes - www.stepwise.com/Articles/VermontRecipes
_______________________________________________
cocoa-dev mailing list
email@hidden
http://www.lists.apple.com/mailman/listinfo/cocoa-dev