NumericTextField: formatting just for showing

Richard_And_Trisha

I am wondering it is possible to show formatting like comma in thousand but the data when updating is still double?

bgrommes

I think you want to check out the formatting strings.

https://docs.objo.dev/#/format-strings?id=standard-numeric-formats

(Scroll down for custom formats)

In your case I believe you want the standard numeric format "N" followed by a digit specifying the number of decimal places to include. For example:

someDouble.ToString("N2") # e.g., 123456.3297 displays as 123,456.33 if the current culture uses comma as a thousands separator; German locale would display 123.456,33 etc.

This leaves the Double variable unchanged for use in mathematical operations, etc.

Richard_And_Trisha

bgrommes I think it does not work on NumericTextField but work for normal TextField

DrScott

NumericTextField Doesn’t have a setting for a thousands (or millions, etc.) separator. If it’s added to NumericTextField, it would need to be localizable, as would the decimal point, to account for different formats for floating-point numbers across the globe.

Richard_And_Trisha

DrScott understood. If i used a textfield, how to check for numerical value only??

DrScott

I haven’t done this in code, but here’s the gist of a very simplistic way to try:

To read the value in the TextField, I’d first set a String to the TextField’s Text, and search that string for commas and remove them. Then I’d call Double.Parse(). It’ll throw a InvalidArgumentException if the input value is incorrect, so you can present an error message to the user in the exception handler. Only set the variable you use to store the Double if the Parse doesn’t throw an exception.

To write a Double value to the TextField with a thousands separator, first convert the number to a String. If the Double is over 1000, search the String for the decimal point. If one is found, insert a comma at an index 3 spaces before it.

Garry

Thanks for the suggestion. I’ve added this in the next release: https://feedback.objo.dev/feature/1276

NumericTextField now has a UseGroupingSeparators Boolean property, available both in the Inspector and from code:

NumericTextField1.DecimalPlaces = 2
NumericTextField1.UseGroupingSeparators = True

This changes only the displayed text; Value remains a Double that can be used directly in calculations. The separators follow the user’s current locale, so the same value might appear as 1,234.50 or 1.234,50.

Richard_And_Trisha

Garry
Brilliant !! currently I am using a TextField that do the formatting("N1") but then when come to saving (which I have not done yet) I will to remove the comma or when reading in need to add the comma in. and also need to add checking for number only (which I have not done yet).

now with the new UseGroupingSeparators, I don't need to do all those anymore.

also in my tr_TextField, I can enter 1K or 1M and it will convert to 1,000 or 1,000,000 but only when AmountYN property in the subclass is set to true.

How to expose the property in the subclass to be show In the inspector or even in code so I can say Value1.AmountYN=True

Garry

Yes, you can do both.

First, ensure that AmountYN is a public, settable property on your tr_TextField subclass:

Public Class tr_TextField Inherits TextField
    Public Property AmountYN As Boolean = False
End Class

That makes it accessible from code:

Value1.AmountYN = True

To make it appear in the visual designer:

Right-click the tr_TextField class in the Solution Navigator.
Choose Inspector Behaviour...
Enable the AmountYN property.
Select Value1 on your window.

AmountYN will then appear in the regular Inspector and can be set independently for each tr_TextField instance.

Richard_And_Trisha

Garry Brilliant !! got it working !! I think I was looking for the inspector behaviour everywhere

Richard_And_Trisha

Garry

 NumericTextField now has a UseGroupingSeparators Boolean property, available both in the Inspector and from code:

NumericTextField1.DecimalPlaces = 2
NumericTextField1.UseGroupingSeparators = True

This changes only the displayed text; Value remains a Double that can be used directly in calculations. The separators follow the user’s current locale, so the same value might appear as 1,234.50 or 1.234,50.

just try this and can confirm it is working correctly