- Notifications
You must be signed in to change notification settings - Fork2
SyncfusionExamples/xamarin.forms-listview-inside-scrollview
Folders and files
| Name | Name | Last commit message | Last commit date | |
|---|---|---|---|---|
Repository files navigation
When theSfListView is loaded inside theScrollView with the height of total items, scrolling will not occur in the SfListView only whenAllowSwiping is set totrue. The SfListView does not pass touch to the parent ScrollView in UWP, because swiping is handled in it.
When the SfListView is loaded inside the ScrollView the following scenarios, the height of the total items is set toHeightRequest of the SfListView.
If the position of the SfListView is not in view when loading inside the StackLayout with more than one children, the SfListView will not be loaded. Because, the StackLayout passes the height for theSfListView as 1.
When loading the SfListView inside theGrid with row definition asAuto in UWP, Grid passes the height for the SfListView to be 1.
<local:ExtScrollView x:Name="scrollView" > <sync:SfListView x:Name="listView" ItemsSource="{Binding BookInfo}"/></local:ExtScrollView>When the SfListView is loaded inside the ScrollView with sticky header and sticky group header, it changed to scrollable. The empty space remains after the SfListView items, when the device orientation is changed to horizontal. Because, the total extend is set to theScrollView in horizontal orientation
public class ExtScrollView: ScrollView{ protected override void LayoutChildren(double x, double y, double width, double height) { this.Content.HeightRequest = height; base.LayoutChildren(x, y, width, height); }}To know more about MVVM in ListView, please refer our documentationhere
About
Sample showcases how to load Xamarin.Forms Listview inside Scrollview.
Topics
Resources
Uh oh!
There was an error while loading.Please reload this page.
Stars
Watchers
Forks
Releases
Packages0
Uh oh!
There was an error while loading.Please reload this page.
Contributors7
Uh oh!
There was an error while loading.Please reload this page.