Working on adapting my torque app for use in Spain - during device connectivity testing (Serial Device connection troubleshooting), when we finally got Tulip connected properly and registered output from the test equipment, I noticed when we cast the number-formatted-as-text value to numerical, it cast it with a comma instead of a period to indicate the decimal place. However, when casting that number back to text, Tulip cast it with a period. This actually works out great for me because logically I won’t have to rework anything, the text parts will parse the same and the number parts will evaluate normally, but I thought this was interesting:
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| TEXTTONUMBER checks invalid decimal point PLAT-42852 | 1 | 55 | July 2, 2025 | |
| Fix non-US locale display issues | 1 | 46 | July 9, 2024 | |
| Ability to influence number output format when trying to send a number input with a connector function to a remote sytsem | 1 | 181 | March 1, 2024 | |
| Csv import - comma/period as decimal separator | 5 | 470 | March 11, 2021 | |
| Decimal Place Formatting Issue | 2 | 136 | January 29, 2025 |