I have been hit by the same issue exposed there:
In a field where you want number, say float:
if you enter a float ok
if you enter an integer, next input are coerced to integer and you can
not input float anymore (you can make a forced conversion in your model,
but it is wrong, because you may want your model to work with Float)
In a field you input ScaledDecimal, say 25.99s2
at next input, your field is set as 25.99s2, what is supped to
understand the user there?
IMHU, autoconversions will always bring issues.
Refactor the autoconversion methods
Add a bloc attribute to WebFormElement to let the user processes the
conversion as wished
Dr. Geo - http://drgeo.eu
iStoa - http://istoa.drgeo.eu
Aida mailing list