On 24 Jan 2009, at 09:27, Kyle Sluder wrote:

On Sat, Jan 24, 2009 at 3:49 AM, Jonathan Fewtrell
<jonathanfewtr...@mac.com> wrote:
Yes, I saw that. Maybe I misunderstood it. I thought that if the app was running under 10.3.9 the formatter would always be created as 10.0 format since the 10.4 format stuff didn't exist in the 10.3 frameworks. Isn't that
right?

Yes, that's correct.  Your format string seems to be correct as well.

Are you sure you haven't called a 10.4-only method against the number
formatter before calling -setFormat: ?

Yes. The only possibly relevant code I have is in the class's +initialize method:

+ (void)initialize
{
if ( [NSNumberFormatter instancesRespondToSelector:@selector(setFormatterBehavior:)] ) {
                NSLog(@"They do respond");
                [NSNumberFormatter setDefaultFormatterBehavior:1000];
        }
}

I put this in to force 10.0 behaviour when running on 10.5. The log message is not called on 10.3.9, confirming that the +setDefaultFormatterBehavior method is not called under 10.3.9. Anyway, the problem still exists even if I remove the +initialize method.

I've also tried different format strings. And retyping the whole thing to make sure no invisible characters crept in. Makes no difference.

Bafflement reigns.


_______________________________________________

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to