Available in minor release 2017.3.1214. It will also be available in the R1 2018 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.

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

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