Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update optimize-gridview-and-listview.md #3175

Merged
merged 1 commit into from
Jun 16, 2021
Merged

Update optimize-gridview-and-listview.md #3175

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions windows-apps-src/debug-test-perf/optimize-gridview-and-listview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -237,7 +237,7 @@ The general strategy for the [**ContainerContentChanging**](/uwp/api/windows.ui.
}
```

4. If you run the app now and pan/scroll quickly through the grid view then you'll see the same behavior as for as for **x:Phase**.
4. If you run the app now and pan/scroll quickly through the grid view then you'll see the same behavior as for **x:Phase**.

## Container-recycling with heterogeneous collections

Expand Down Expand Up @@ -315,4 +315,4 @@ When recycling an item (**ListViewItem**/**GridViewItem**), the framework must d

When there is an uneven distribution of items that use different item templates then new item templates will likely need to be created during panning, and this negates many of the gains provided by virtualization. Additionally, an item template selector only considers five possible candidates when evaluating whether a particular container can be reused for the current data item. So you should carefully consider whether your data is appropriate for use with an item template selector before using one in your app. If your collection is mostly homogeneous then the selector is returning the same type most (possibly all) of the time. Just be aware of the price you're paying for the rare exceptions to that homegeneity, and consider whether using [**ChoosingItemContainer**](/uwp/api/windows.ui.xaml.controls.listviewbase.choosingitemcontainer) (or two items controls) is preferable.