Thanks for testing ROUND() and EVAL() NotNull,
addcol:A A:=round(16)=> 16,0
addcol:A A:=ROUND(16,0) => 16,0 (instead of 16)
ROUND() returns a double value.
(double is a real number -it has a decimal place)
I have on my TODO list to format the result as a integer value.
addcol:A A:=EVAL(round(16)) => 160
This is caused by ROUND() localizing 16.0 as 16,0
The next update will not localize double numbers when converting them to text.
EVAL() takes a string.
Everything is seeing: EVAL("16,0") => 160
addcol:A A:=EVAL(1.0*17/99) => 171717171 (instead of 0,171717171)
Same issue as above.
Everything is seeing: EVAL("0,171717171")
The next update will not localize double numbers.
addcol:A A:=EVAL(19/100) => 0 (as expected)
Keep in mind, EVAL takes a string.
19/100 will be evaluated by Formulas, converted to a string, then passed to the EVAL() function.
EVAL(19/100) => EVAL(0) => EVAL("0") => 0
EVAL() can be skipped here with:
A:=19/100
addcol:A A:=EVAL(19.0/100) => 19
Everything is incorrectly seeing: EVAL("0,19") => 19
#[define:min=33#]: addcol:A,B,C A:=[min:] C:=8 $C:>$A: B:=N([min:] nop:"A = min = 33, B= N(min); check if min is numerical, C = 8. Show results if 8>33"
Shows results. Looks like a textual comparison ("8" > "3") instead of a numericla one.
Correct, currently custom columns are just text.
Not values.
Support for custom columns values is on my TODO list.
For now, please try:
#[define:min=33#]: eval:8>[min:]