Currently the Height is not changed, however the control should update its size when expanding/collapsing/adding new items and removing existing items.

When you work with mobile one of the major issues I have found is that the picker does not allow filtering so when you have more than a hundred of items the user can select on but you are displaying a thousand it’s kind of complicated, so a filtered picker would be awesome for developers that are working with Telerik controls

I have a RadLegend that is within a portion of the UI that has its visibility toggled with IsVisible. The logical tree is as follows (it's a custom styled tab UI):

MasterDetailPage -> Detail -> ContentPage -> StackLayout -> Grid (IsVisible bound to "ShowData") -> StackLayout (IsVisible bound to "ShowCategoryData") -> StackLayout -> RadLegend

Sometimes it's visible, sometimes it disappears after one of its parent control's visibility changes, sometimes it reappears. Not sure what the rhyme or reason is on when it happens. Seems to happen more on iOS than on Android, but I've seen it happen on both.

Full XAML for the page it happens on is attached.

Provide a ComboBox-like filtering functionality.

With the current feature set, this might be achieved by simply allowing all the items to be visible in the SuggestionsView when the Entry is focused (instead of showing no results until filtering has started)

Add the ability to create a TablView without any header. This could be usful in case you want to host a few ContentView in each tab and change grammatically the select tab.

Also, a SelectedItemIndex property will be useful as well.

Thanks,
Mano

Already available for MultiDayView

Xamarin.Forms library that allows to have for Google-Map-Like sliding panel from bottom of the screen. 

When using the Telerik project template, the assembly references are added using full paths.

This presents a problem for source control projects as Xamarin projects are frequently used across Mac and PC. When a windows file path to the UI for Xamarin installation folder is used, this is not compatible for a Mac machine.

Current implementation uses this type of path:

C:\Program Files (x86)\Progress\Telerik UI for Xamarin R2 2018\Binaries\[PlatformName]\Telerik.dll

This path would not be present on a Mac, however if you use a relative path instead, like this:

..\..\Progress\Telerik UI for Xamarin R2 2018\Binaries\[PlatformName]\Telerik.dll

 the developer on the Mac could place the Telerik installation in a similar folder path and both PC and Mac could use assembly references.



Alternative
Add an option to choose the Telerik NuGet package reference instead of assembly references.

A custom Searchbar that could be display over navigation bar. (Ex: See WhatsApp)

The purpose of this item is to track demand for support of the MacOS platform in the Telerik Xamarin controls. 

https://docs.microsoft.com/en-us/xamarin/xamarin-forms/platform/mac

The purpose of this item is to track demand for support of the GTK platform in the Telerik Xamarin controls. 

https://docs.microsoft.com/en-us/xamarin/xamarin-forms/platform/gtk?tabs=vswin

https://docs.microsoft.com/en-us/xamarin/xamarin-forms/platform/
Xamarin Forms is growing! Does your controls-set plans to grow with it??

I'm currently working on a new project, and had to drop the usage of telerik's products, because its lack of support to other platforms.

What are your plans on this subject?

It would be great if we could have support to (but not limited to): Android, IOS, UWP (Mobile and Desktop "win10"), WPF (For Desktop Applications on win7,8,10), GTK# (Linux) and macOS.

I'm sure I wouldn't be the only one to buy your products if you upgrade yours platforms support.

Thanks!

SlidedToIndex event is triggered from a non-UI thread which forces the users to use Device.BeginInvokeOnMainThread

As of 2018.2.620, UI for Xamarin will invoke approximate 600 warnings when compiling an Android project that uses SDK later than 23.

This is due to the fact that the UI for Xamarin.Android controls are built on API 23, which will surface warnings at compile time if the project consuming them is using a later version.

Although UI for Xamarin is compatible with newer version, and causes no impact on the outcome, these warnings obscure any meaningful warnings the user might have. 

This is a problem when projects are built in a CI/Cd pipeline and warnings are treated as important/significant for enterprise CD deployment (i.e. scrolling through 600 warnings to find any legitimate warnings is not practical).

Available in R3 2018 release.

When the Telerik Xamarin toolbox is in a partial-height tab (i.e. half the height), there isn't a scrollbar to see the off-screen controls.

Workaround: 
Make the toolbox full height of the tab to see all the controls. Here's a video demonstrating https://www.screencast.com/t/cUjIC0sx4 

Xamarin.Forms has made MergedWith obsolete in XF 3.1, you can now use the more traditional Source path to merge ResourceDictionaries.

Provide a path to the UI for Xamarin ResourceDictionaries. This can be done directly through the DLL itself or include the XAML files in the product distribution (or both).

Using Visual Studio for Mac, added packages using telerik nugget server, added radCalendar in xaml code. preview crashes and exception report window pops up.