I consider this a really high priority bug that needs to be fixed as soon as possible.
This is what happens on my system:
- My OS is set to use german keyboard layout, using comma as decimal separator which never was a problem in Max
- If Corona is installed, Max 2017 will display comma as decimal separator but will not accept floating point values using a comma and expect a dot instead
- However, when using a dot, it'll first accept the value but display a comma. When leaving the numerical field, it'll re-evaluate the value and accept only the digit(s) before the comma
- Now the value will change to integer
Attached is a gif where I type in a value, leave the filed and the value gets reset to integer.
This makes it impossible to use floating point values in Max for me in the entire UI. It'll work correctly only if I uninstall Corona for Max 2017 which means I can't use Corona with 2017.