How can I format a large number to have comma separators?

[Henrik_Volkers]

it's 2019

Screens and graphics allow a more easy way (better readability) to display long numbers (on each side of the decimal seperator).

Numeric inputs and outputs of a modern UI should be able to group the numbers with fractions of a space (I would prefer as a general seperator).

And don't miss the scales !!

Ideas to push:

https://forums.ni.com/t5/LabVIEW-Idea-Exchange/Visual-Aides-Numeric-Separators/idc-p/3881749

https://forums.ni.com/t5/LabVIEW-Idea-Exchange/Digit-grouping-for-Numerics/idc-p/2123338

[Yamaeda]

There's some good function in .net for this that I made a test with. I can't find it quickly though.

/Y

[Henrik_Volkers]

Well. since 20 years I can use TeX to set nice tables for documents ... however, I want this in native LabVIEW on my UI including the graph scales. 

[altenbach]

---

@Henrik_Volkers wrote:

it's 2019

Screens and graphics allow a more easy way (better readability) to display long numbers (on each side of the decimal seperator). 

---

"long numbers" (especially with a reasonably number of significant digits), should probably be displayed in SI or scientific format anyway. Much more concise.

Even with seperators, things will get out of hand if you need to (mis?)count the number of triplets, for example. The problem is just pushed a little bit, but still exists.

[Yamaeda]

There's a good .net function for that, that I finally figured out (though I agree with Altenbach about the SI format).

/Y

[crossrulz]

---

@altenbach wrote:

"long numbers" (especially with a reasonably number of significant digits), should probably be displayed in SI or scientific format anyway. Much more concise.

Even with seperators, things will get out of hand if you need to (mis?)count the number of triplets, for example. The problem is just pushed a little bit, but still exists.

---

That is why my go to formats for numbers is "%0.3p" and "%#.3p" (depending on if I really want to see the trailing 0s or not).

[Henrik_Volkers]

Unless you have to deal with ppms and ppbs 😉  

---

---

That is why my go to formats for numbers is "%0.3p" and "%#.3p" (depending on if I really want to see the trailing 0s or not).

---

[crossrulz]

---

@Henrik_Volkers wrote:

Unless you have to deal with ppms and ppbs 😉

---

That would be an exception.  99.5% of the time, 3 decimal places is more than enough.

[Henrik_Volkers]

---

@crossrulz wrote:

---

@Henrik_Volkers wrote:

Unless you have to deal with ppms and ppbs 😉

---

That would be an exception.  99.5% of the time, 3 decimal places is more than enough.

---

Say for 99,5% of the applications ...

unless you work in a national metrology lab... 😄

[nibuddy1777]

There was a small bug with code posted above. You to exclude a comma when the "substring after match" output = "" (null string) otherwise it adds an extra comma at the beginning of the number.