Skip to main content

When I use an Attribute Creator to create a "copy" of an Attribute, it converts the value to an incorrect Floating-Point number. 92.7 --> 92.700000000000003. When I compare this value later, the test obviously fails. How do I ensure the correct number (or the string) is retained?

This is not necessarily an error, see https://floating-point-gui.de/

If it's an issue for your use case, consider using an AttributeRounder.


This is not necessarily an error, see https://floating-point-gui.de/

If it's an issue for your use case, consider using an AttributeRounder.

How do I force the use of a decimal data-type or prevent the numeric conversion?

You'll note the issue is also quite misleading in the inspector as per the screen-shot above.


Reply