Re: NSNumberFormatter Issues
Re: NSNumberFormatter Issues
- Subject: Re: NSNumberFormatter Issues
- From: Gordon Apple <email@hidden>
- Date: Sun, 05 Jul 2015 10:40:22 -0500
- Thread-topic: NSNumberFormatter Issues
There is no explicit code involved. It’s just a simple binding to a CGFloat.
The original property also had a binding from a JoyStick view. However, for
testing, I added a new CGFloat property so I could bind the text field only,
with no potential interference from the JoyStick view. The angle settings
are for shaders and shadows, with the same problem showing up in both
places. This has worked just fine for a long time until recently. (I just
tested it again with “lenient” set in IB, to make sure, and it didn’t help.)
On 7/5/15 1:41 AM, "Graham Cox" <email@hidden> wrote:
>
>> > On 5 Jul 2015, at 6:53 am, Gordon Apple <email@hidden> wrote:
>> >
>> > However, if user changes the
>> > displayed value, leaving the degree symbol intact, it says it is invalid >>
and
>> > throws an exception, essentially ending the program run. This is totally
>> > unacceptable. What is going on here? (And this behavior is showing up in
>> > several places.) I tried setting ³lenient². Didn¹t help.
>
>
> This sounds exactly what happens when ‘lenient’ isn’t checked, so are you
> certain about that? Is there something that could be setting it to non-lenient
> in code?
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden