When RadPdfViewer is used in a master-detail page, I should maintain the previous page index when I traverse between pages.

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.

For example the control ignores IsTabStop and TabIndex properties for keyboard tab navigation. It behaves differently on Android, iOS and UWP.

The staggered layout lays out items in a staggered grid formation. the layout is available as follow:

Telerik Ui for Xamarin.iOS ListView

Telerik UI for Xamarin.Android ListView

Telerik UI for UWP ListView

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..

Hello,

We are using Xamarin Forms and Telerik for iOS and Android.

We were asked several months ago to host our Xamarin Forms app on WPF.

Currently, SyncFusion is the only one to support WPF.

Will Telerik support WPF for Xamarin Forms someday ? Do you have any idea when ?

If you won't support it, I will be obliged to move to SyncFusion (WPF will be mandatory soon as we will migrate our WPF app on Xamarin : a merge of our products and our dev team)

We have both Telerik and SyncFusion. We decided to use Telerik for 95% of our controls (except the ListView where SyncFusion got more advanced features).
We prefer to stay on Telerik for as long as we can but won't have other choice to migrate to SyncFusion if Telerik will never provide WPF controls for Xamarin Forms.

Thanks a lot

Do you have plans to develop controls for the UNO platform?

There are other companies that have already stated that they are working on it, for example,  

https://www.syncfusion.com/blogs/post/collaboration-syncfusion-uno-platform.aspx 

Hi,

I am using DataForm for my project and in the process of implementing validation. For validation, I use DataAnnotation-NonEmptyValdator for the required fields.

Is there a way to change it dynamically in runtime?.

For example, I have 2 fields, the first field is always required. However, the second field is not always required, it depends on the selected item of the first field.

Thanks

Dan

On UWP and Android the item can be swiped beyond the SwipeOffset property. Add option to restrict the swiped distance to the SwipeOffset value.

Provide API which enables the group headers to remain in the view when scrolling until the next ones push them away.

RadChat has an InputAreaBackgroundColor property, but it would be nice to be able to have full control over the UI of the entire input area. For example, I have the following UI from my designers that I cannot currently implement using RadChat:

Adding an InputAreaControlTemplate would be much appreciated.

If you prepare a Xamarin.Forms app to respect iOS Dark Mode, it is apparent that the RadDataForm is only respecting the native elements for Dark Mode.

REPRODUCIBLE

For example, use my attached reproducible.  Notice how the text in the native editors has the appropriate light text, but the background is still stuck on light coloring.

If you try to use Editor style or GroupHeaderStyle, you can't use DynamicResource because the style's properties are not BindableProperties:

We really need these properties to be usable with DynamicResource, so this is a feature request more than a bug report. Update the properties to BindableProperties that with with DynamicResource.

WORKAROUND

A workaround for this would be to set everything you can to be transparent:

Thank you.