In Xamarin.Forms, there is no multiline text box editor in RadDataForm.
Expose an IsEnabled property for editors that can be toggled after DataForm is rendered. Currently, only Data Annotations can determine whether or not a property's editor is read-only. If a specific editor's read only state needs to be changed dynamically (e.g. due to a selection in another editor), you would need to completely reload the DataForm.
With the current implementation in Xamarin.Forms, the control has no built-in support for enumerable properties. The approach is to create custom renderers and use the native editors. We need to expose default editors for enumerable and custom types.
Currently, on Android and UWP the date and time editors display popups with "OK" and "Cancel" buttons, so one can easily dismiss the control even if a value has been selected. This will still keep the null value in the dataform. On iOS value changes are propagated immediately to the dataform, so there is no way to keep the null value.
Add FontFamily option to DataFormEditorStyle and DataFormGroupHeaderStyle.
Add TextAttributes option to DataFormEditorStyle and DataFormGroupHeaderStyle (e.g. Bold).
There is an empty group title view above the editors even if there are no groups. The red area on the attached screenshot.
If the following data annotations are defined: [DisplayValueFormat(Date = "MM-dd-yyyy HH:MM tt")] [ReadOnly] DisplayValueFormat is not applied properly.
We need to simplify the way the editors can be customized. XAML only solution would be great.
When DisplayValueFormat is set to an Integer property, Zero value is not applied.
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.
When a field is of type Integer and is configured to use IntegerEditor, currently it is shown with a decimal point