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.

When SlideView contains ContentViews, it does not always update SelectedIndex (or visible item) after swiping on iOS

Hi!

We are using your component SlideView on Main Page of our app. Unfortunately when we upgraded Xamarin Forms to 4.0 version we are facing exception - System.NotSupportedException: Unable to activate instance of type Telerik.XamarinForms.PrimitivesRenderer.Android.SlideViewRenderer from native handle 0x75 (key_handle 0x60775bd). ---> System.MissingMethodException: No constructor found for Telerik.XamarinForms.PrimitivesRenderer.Android.SlideViewRenderer::.ctor(System.IntPtr, Android.Runtime.JniHandleOwnership) ---> Java.Interop.JavaLocationException: Exception of type 'Java.Interop.JavaLocationException' was thrown.

Steps to reproduce:

1) Open app with SlideView and BottomNavigationBar

2) Navigate to any another tab

3) Back to main page tab

4) App is crashing with this exception.

It could be important information to reproduce this but it doesn't happend on every tab. We have five tabs in app (Main Page and 4 additional) and it crashes only on navigation between main page and last tab.

I guess that could happend when SlideView disposes or reloads.

Request

Android follows a "bottom-up" approach to gesture/touch handling. It would be nice if the RadSlideView would allow any swipe gesture that it cannot handle itself to propagate upwards so that another view can have a chance to handle it.

Example

Given the following XAML:

<ParentView>
        <ParentView.GestureRecognizers>
            <SwipeGestureRecognizer Direction="Left"
                                    Command="{Binding ForwardCommand}" />
            <SwipeGestureRecognizer Direction="Right"
                                    Command="{Binding BackwardCommand}" />
        </ParentView.GestureRecognizers>

        <RadSlideView />
</ParentView>

Expectation:

• When the user is at the beginning of the items in the RadSlideView and swipes right, then the BackwardCommand should execute. (The RadSlideView should detect that it is at the beginning of its item source and allow the right swipe gesture to propagate upwards to the ParentView.)
• When the user is at the end of the items in the RadSlideView and swipes left, then the ForwardCommand should execute. (The RadSlideView should detect that it is at the end of its item source and allow the left swipe gesture to propagate upwards to the ParentView.)

The second item is visible, but the index does not seems updated, after the second swipe again the second item is visible, but now the index is updated and the next swipe leads to the third item.

Switching the views is executed by setting SelectedIndex property of the SlideView.

Available in minor release 2018.3.1109. It will also be available in the R1 2019 release.

Refer to the attached reproducible,

The DataTemplateSelector should be returning RedTemplate and BlueTemplate every other item. However, the SlideView is not making calls to the selector and incidentally reuses the wrong template for multiple items in a row,

Available in minor release 2018.2.821. It will also be available in the R3 2018 release.

After an item is removed from the ItemsSource, if you swipe, the indicators are not properly updated.

When the SlideView is bound to a collection containing 1000 items it takes long time (15 seconds) to visualize the control.

Available in the R2 2018 release.

Available in the 2018 R2 SP release.

First item content doesn't update when starting with an empty ObservableCollection even though an indicator is present.

Steps to repro:

1- Starting with an empty ObservableCollection<T> ItemsSource 
2 - Add two items (notice 1st item's content stays empty)
3 - Slide to the 2nd item (notice content is visible)
4 - Slide back to 1st item (notice content is now visible)

Attached a runnable repro.

Available in minor release 2018.1.405. It will also be available in the R2 2018 release.