It would be interesting if the map control could read a shapefile or kml file and visualize the shapes, besides exporting the modifications of the map (shapes) to a shp format.
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.
I have an autocomplete that needs to fire some validations even when the user does not select anything from the suggestion view, i.e when the autocomplete Loses the Focus.
I saw that "Completed" event is in development, but that is not enough for me, I would need the "Unfocused" event.
Most PDF Viewers come with the ability to print, email, text etc the PDF that is loaded. For example, in the default iOS PDF viewer there is a "share" icon. When the "share" icon is tapped, multiple options and apps come up that allow users to "print", "message/text", "email" the PDF. It would be a great feature to have in the Xamarin UI PDF Viewer. It could just be part of the PDFViewer Toolbar options.
xamarin forms on wpf is now official, https://docs.microsoft.com/en-us/xamarin/xamarin-forms/platform/wpf we need to support telerik on there aswell..
Add a new image cropper control, which allows users to drag/zoom a selected image within a defined frame, so that the resulting image has a defined width and height. This should offer an experience similar to the Facebook app's screen for adding/updating your profile photo. The control should display the non-selected area of the photo with configurable opacity settings, and optionally allow for a resulting circular image.
Please let us know:
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.