If I select the new-style NSNumberFormatter, I don't see a Zero field in
Xcode/IB where I can enter that. Since it's working when I just create the
formatter in code, I'll just keep doing that.
What's really strange is that using the an almost identical project converted
from Xcode 3.2 to
Hi,
is the 10.0+ style of NSNumberFormatter no longer supported? I
recently moved from developing in Xcode3 under OS X 10.7 to Xcode 4 under OS X
10.8, and from having a Base SDK of 10.6 to 10.7, and from a Deployment Target
of 10.5 to 10.6, and am now having problems with my xib-base
Hm, it may be that something else is at play here. I did make ONE change when
porting… I put my text fields inside a tab view. I wonder if maybe there's a
problem accessing the number formatter from a control inside a tab view? All
the connections *appear* to be there, and the call stack
Ok, this seems to be an IB issue. I've made my own NSNumberFormatter, set its
properties, and set it as the formatter for my text fields, all in code, and
that works perfectly. No idea why the same object created in Xcode fails, but
I'll do whatever it takes to make it work, I guess!
There are occasional bugs when converting from earlier formats. What I do
besides reporting the bug is to look at the underlying XML in the earlier
version of the XIB and the later version and try to manually make the necessary
changes using a text editor. I've sometimes had to quit Xcode, edit
The implementation of old-style NSNumberFormatter has some sort of
compatibility code for old archive formats. It's possible that new versions of
Xcode don't write that old format correctly, or even try to do it at all.
(The error occurs because the Zero field came back as an NSString instead
