This paragraph mentions doing 'something' for a custom ListViewItemPresenter:
> For a custom ListViewItemPresenter, use the name of your class as the string within the object element syntax for XAML. You'll probably have to map an xmlns definition with a prefix to refer to your class definition. For more info, see XAML namespaces and namespace mapping.
However, it's not very clear what the intent for the developer to do is. It's be great if this could be clarified with a more complete example with code and XAML provided to show how to do this and what the benefits of a custom ListViewItemPresenter are.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
ID: e61659b2-ba24-5f14-c375-6c6497b06bc4
Version Independent ID: 40496455-80e3-fdb8-f18c-be3bc3fbf136
predavid-zz
commented
5 years ago
This paragraph mentions doing 'something' for a custom ListViewItemPresenter:
> For a custom ListViewItemPresenter, use the name of your class as the string within the object element syntax for XAML. You'll probably have to map an xmlns definition with a prefix to refer to your class definition. For more info, see XAML namespaces and namespace mapping.
However, it's not very clear what the intent for the developer to do is. It's be great if this could be clarified with a more complete example with code and XAML provided to show how to do this and what the benefits of a custom ListViewItemPresenter are.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.