Users cannot input decimal separator both "." and "," in the decimal editor. Available in minor release 2017.2.0523. It will also be available in the R2 2017 SP release.
Expose a way to control the exact string visualized in the DecimalEditor. After entering 1234.2 in the editor, users should be able to configure the string to see 1,234.20. Available in minor release 2017.2.0602. It will also be available in the R2 2017 SP release.
Built the SDKBrowser project for iOS, using VS 2017 and latest stable Xamarin.Forms. When editing a field, the OS keyboard appears and above it are "Prev" and "Next" buttons for moving between form fields. Those buttons behave erratically. Attached 2 images. 01: the 1st field is focused. 02: after pressing Next, the 3rd field is focused ("Age"). Pressing Next again does not change which field is focused, and Prev becomes active. Pushing either Prev or Next does nothing at all.
Available in minor release 2018.1.202. It will also be available in the R1 2018 SP release.
The maximum value that the DecimalEditor can set seems to be 100. If the underlying property is more than 100 it automatically sets it and you cannot increase it through the UI.
Numeric and date editors are not aligned identically to the other editors inside the dataform
When a field is of type Integer and is configured to use IntegerEditor, currently it is shown with a decimal point
Nullable int property is validated against range when no data is input.
Available in the 2018 R2 SP release.
Available in the R2 2018 release.
The expected behavior when updating the text on a button click, for example, is to expand the editor. Currently the editor is expanded when the user starts typing inside it.
Available in minor release 2018.2.727.250. It will also be available in the R3 2018 release.
The error message is not showing when the editor is empty and the ValidateAll method is called