In a Double Configuration node, when I try to set a default value lower than 0.0005…
…it immediately rounds it down to 0 when I point the cursor somewhere else:
It is not just the way the number is displayed, it internally rounds the number down to 0. Proof: when I try to multiply the number by a million:
…it is still very much zero.
In the “Preferred renderers” section of the Preferences, the “Number (double)” is set to “Full Precision”, so that is not the problem. So my question is, how can I set the default for the Double Configuration node to a value lower than 0.0005?
I believe there is a problem with the way the default value is visualized (decimals are systematically truncated beyond a precision). While waiting for this to be fixed, I suggest the following work around :
so it is not just me thanks for your suggestion, I will use that workaround for the time being.
It is funny that, in contract with the Double Configuration window, the Component configuration stores small numbers properly, even when they are not displayed.
I will share the workflow, but the problem only occurs when interacting with the Double Configuration dialog window.
Again, the workflow:
Entering 0.5 into the Double Configuration dialog:
…the workflow has no problem:
Entering 0.05 into the Double Configuration dialog, no problem:
Entering 0.005 into the Double Configuration dialog, no problem:
Entering 0.0005 into the Double Configuration dialog however…
Entering the number as 5e-4 doesn’t help.
When I, instead of trying to enter the value literally into the Default Value field of the Double Configuration node, get the value from a flow variable, as @aworker suggested :
using
and entering the value into the Double Configuration dialog by:
it works perfectly:
So it seems to be a user interface problem. Maybe specific to my system (xubuntu 20.04)? Unfortunately I do not have any other OSs to try it on.
Best
Aswin
p.s. what I wrote in my earlier post
“It is funny that, in contract with the Double Configuration window, the Component configuration stores small numbers properly, even when they are not displayed.”
is not correct. A field in a Component dialog window that comes from a Double Configuration node inside the component suffers from exactly the same problem.