Hello,

I receive often a NullReferenceException in ListViewGroupHeader ArrangeOverride method.

The error happens only in UWP.

Unfortunately, I cannot create a project to reproduce the error.

Best regards,

Currently, hiding the 'more' button in the of the DataGrid filter Options panel is not possible.

This is a feature request to add such an option to the DataGrid column styling options (potentially as a property of the HeaderStyle).

The TabView control should support a swipe event to change the active item. Similar to the ListView with the IsItemSwipeEnabled-property.

Allow easy exporting of a chart to a Xamarin.Forms image object. This will allow the images to be shared using social media.

All parts of the TreeViewItem (indicator, text, checkbox) are defined as one big template. Therefore customization of only one part of the template still requires retemplating the whole item. 

When retemplating is applied to the treeviewitem and  20+ children in the nodes are loaded, the result is as follow: If you run that on iOS and expand a node you'll see that it crunches the UI for a few seconds and then loads the child nodes, but i also see on our application that it will crash some times and either way gives a bad feel to the UI on iOS

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 we call ScrollItemIntoView to scroll to one of the nodes at the bottom of the tree the app will crash with a "Unspecified Error".

I've set it to load 150 nodes into the tree and when you click the "Test" button it will error (using UWP). If you change it to only load 100 nodes or less it should work.

1.Start a swipe gesture to the right (as like when you navigate to next three days) but stop it by return your finger back (holding the finger on the screen);
2. Since the gesture was canceled, you stay at 15th to 17th of July;
3.. Tap on some event to open it on other screen. Then come back to the calendar;
4.. Now you see other dates on the calendar, less than before, somewhat like 11th to 14th or 8th to 10th. Each time when you open other screen, calendar changes its displayed date. To cancel this behavior do new navigation swipe gesture.

Workaround:  get the DisplayDate before the navigation and set it when navigating back

<telerikInput:RadTimePicker  SpinnerFormat="hh:mm tt" DisplayStringFormat="hh:mm tt" />
                                               

launched the time picker and only scroll the AM to PM without tapping on it, but value is not reflecting to PM in Time value. 

April 2020 Deadline

Apple will no longer accept applications published with anything less than Xamarin.Forms 4.5 after April 2020.

This is due to the UIWebView flag that is in Xamarin.Forms 4.4 and earlier

ITMS-90809: Deprecated API Usage- Apple will stop accepting submissions of apps that use UIWebView APIs starting from April 2020 . 

Solution

Please visit this documentation for full explanation. Just to share the highlights, Telerik UI for Xamarin will need to:

• Xamarin.Forms 4.5 or higher – Pre-release versions of Xamarin.Forms 4.5 can be used.
• Xamarin.iOS 13.10.0.17 or higher – Check your Xamarin.iOS version in Visual Studio. This version of Xamarin.iOS is included with Visual Studio for Mac 8.4.1 and Visual Studio 16.4.3.
• Remove references to UIWebView – Your code should not have any references to UIWebView or any classes that make use of UIWebView.

While in DayView (or any other appropriate view), allow for appointments to be draggable to another time slot for rescheduling. 

I have a SlideView with IsInfiniteScrollingEnabled property bound initially to false. As expected the swipe gesture and side button are locked to navigate from first to last slide.

but if I set the property to true and then back to false, the swipe event unexpectedly allows me to swipe from first to last slide. Also, the indicator remains in the first slide position even when the slide content is obviously the last one.

If I use the side button instead of the swipe gesture the behavior is as expected.