Success! Looks like we've fixed this one. According to our records the fix was applied for
a recent build.
Sencha Premium Member
decimalPrecision with maxValue
Couldn't find any existing posts about this, but it's pretty straight forward:
This is a problem because this will now allow the user to enter 100, which is not a valid value. Looks like architect assumes the default precision of 2 and ignores your setting.
- Drop a numberfield anywhere.
- Set decimalPrecision to 4.
- Set maxValue to 99.9999.
- Notice architect rounded it to 100.
A resolution would to make the rounding depend on what you have in the decimalPrecision property of the same numberfield.
Edit: Forgot my info
Windows 7 64-Bit
Sencha Architect 2.1.0 Build: 613
Framework: Ext JS 4.1.0
Thanks for the bug report.
We've upped the decimalPrecision for it so that you won't run into these issues.
Currently there is only one global editor for all numbers in Architect. So it isn't specific to what precision you've set in the component (there is no additional intelligence there).