Currently in 2019 R2 and earlier, the "options" button at the bottom of the filtering UI allows the user to rearrange and toggle the visibility of columns in the DataGrid.
I request to have a property or setting on the DataGrid or the DataGridColumn that will prevent the user from changing the visibility or ordering of columns. from that UI (just like you can prevent user filtering or user sorting)
Currently, the only way to set the TextColor for the RadNumericInput is to extract the ControlTemplate and set the TextColor of the internal NumericInputEntry component.
A simple and quick fix is to add a TextColor BindableProperty to the RadNumericInput control and use a TemplateBinding on the NumericInputEntry style
Currently, there is no ItemTemplate for the SegmentedControl, therefore we need to use an IEnumerable<string>. Please add support for ItemTemplate, or DisplayMemeberBinding property, so that we can bind to an IEnumerable<T>.
When the control is hosted inside RadPopup, the application crashes. This is due to the fact that nesting popups is not supported.
Consider changing the implementation of the RadAutoCompleteView to use different control for visualizing suggestions and NoResults message.
Currently we are working with Telerik xamarin forms application,We are using radlistview.I want to scroll and select item with up and down arrow keys.Can we have any sample on this.
Thanks & regards
In Xamarin.Forms, there is no multiline text box editor in RadDataForm.
On UWP and Android the item can be swiped beyond the SwipeOffset property. Add option to restrict the swiped distance to the SwipeOffset value.
Currently, the Avatar property is a string for a path, this is problematic and only support two scenarios (file and uri paths).
I'm requesting that this be changed to be of type ImageSource, which matches the paradigm used by all other Image controls in Xamarin.Forms. This would allow stream and byte sources as well as file and uri paths.
This doesn't have to be a breaking change, you can use an implicit conversion just like Xamarin.Forms Image source does. The only disruption would be if anyone assigned the string value in code instead of a binding.