Both built-in and custom cells can be used/defined in XAML or code. There are built-in cells to choose from, or you can define your own custom cell. The following screenshot shows a ListView with grouped data:ĭata items in a ListView are called cells. Groupsĭata in a ListView can be grouped for easier navigation. Headers and footers can be bound to a separate data source from the ListView's data source. Header and footer components display at the beginning and end of a list, separate from list's data. These components are defined in the following sections.
The ListView control has a number of components available to exercise the native functionality of each platform.
The TableView control can support multiple cell types, so it is a better option when you need to display multiple data types.įor more information about binding data to a ListView instance, see ListView data sources. This requirement is because only one type of cell can be used for each row in the list. The ListView class doesn't support defining list items in XAML, you must use the ItemsSource property or data binding with an ItemTemplate to define items in the list.Ī ListView is best suited for a collections consisting of a single data type. For example, the iOS settings app, which has a mostly predefined set of options, is better suited to use a TableView than a ListView. The TableView control is a better option whenever you have a non-bound list of options or data because it allows predefined options to be specified in XAML. The ListView control shouldn't be confused with the TableView control. The ListView class supports context actions and data binding. Use casesĪ ListView control can be used in any situation where you're displaying scrollable lists of data. For more information, see Xamarin.Forms CollectionView. It aims to provide a more flexible, and performant alternative to ListView. CollectionView is a view for presenting lists of data using different layout specifications.
0 kommentar(er)
