Bug? NumberFormat(Number,0,2): Works on Android but doesn't work in B4J

[LWGShane]

If you use NumberFormat(1000000,0,2) on Android it correctly displays as "1,000,000" but displays as "1000000" on B4J.

B4J:

B4A:

 

[klaus]

Strange, I tested it and get 1,000,000 with both platforms!
B4A version 9.80
B4J version 8.10

 

[William Lancee]

It also works for me. Are you sure that you are not using NumberFormat2(1000000,0,0,2,False) on B4J?

Edit: You are right, this is what I get

Log(NumberFormat2(1000000,0,0,2, False))    '1000000.00  on B4J Version 8.10

Log(NumberFormat(1000000,0,2))                '1000000.00  on B4J Version 8.10

Log(NumberFormat(1000000,0,2))                '1,000,000  on B4A Version 9.80

 

[William Lancee]

I was confused by inconsistency, but now I agree there is a Bug (hard to believe)! It shows up when you run these 3 lines on B4J.

Log(NumberFormat(1000000,0,2))                '1,000,000   on B4J Version 8.10
Log(NumberFormat2(1000000,0,0,2,False))        '1000000.00  on B4J Version 8.10
Log(NumberFormat(1000000,0,2))                '1000000.00  on B4J Version 8.10

 

[William Lancee]

After some experimentation, it appears that when NumberFormat call comes after a NumberFormat2 call, the separator flag is not cleared.

Log(NumberFormat2(1000000,0,0,2,False))      '1000000.00  on B4J Version 8.10
Log(NumberFormat(1000000,0,2))                '1000000.00  on B4J Version 8.10

Log(NumberFormat2(1000000,0,0,2,True))      '1,000,000.00  on B4J Version 8.10
Log(NumberFormat(1000000,0,2))                '1,000,000.00  on B4J Version 8.10

And the maximum fractions is also inherited!

    Log(NumberFormat2(1000000,0,2,0,False))        '1000000  on B4J Version 8.10
    Log(NumberFormat(1000000,0,2))                '1000000  on B4J Version 8.10

    Log(NumberFormat2(1000000,0,2,0,True))        '1,000,000  on B4J Version 8.10
    Log(NumberFormat(1000000,0,2))                '1,000,000  on B4J Version 8.10

 

[klaus]

There is indeed a problem.

 

[Sandman]

I'm away from my B4* products at the moment so I can't do any hands-on testing myself, but I have to ask if this could be explained by different regional settings on the Android device and the OS where the B4J app is run?

I would imagine that NumberFormat takes the regional settings account, isn't that correct? (The spec up top doesn't mention anything about this, but it seems very strange that it would always default to comma being used as a thousands separator.)

 

[agraham]

Yes, looking inside jCore.jar this seems to be this sems to be a bug in B4J. In B4A in Core.jar NumberFormat and NumberFormat2 use separate instances of a java.text.NumberFormat object when formatting numbers. In B4J they share a common single instance so NumberFormat inherits the latest Grouping and MinimumFractions settings from NumberFormat2!

 

[William Lancee]

Looks like it was fixed, but the bug has returned.

https://www.b4x.com/android/forum/threads/numberformat2-changes-numberformat-behaivior.86047/

 

[William Lancee]

Using only NumberFormat2 avoids the problem.
Also B4XFormatter doesn't have this problem. The following are correct and work the same in B4A and B4J.

    'Private formatter As B4XFormatter in internal Library
    formatter.Initialize
    Dim DefaultFormat As B4XFormatData = formatter.GetDefaultFormat
    DefaultFormat.MaximumFractions = 2
    DefaultFormat.MinimumFractions = 2
  
    'In . grouping Locales
    Log(formatter.Format(2131231231.12))

   'In , grouping Locales
    DefaultFormat.DecimalPoint = ","
    DefaultFormat.GroupingCharacter = "."
    Log(formatter.Format(2131231231.123456))

 

[Erel]

It is indeed a bug.
It was fixed in B4A and wasn't fixed in B4J. It is now fixed for the next update.