Several samples aren't using a custom options pane

[Arlodotexe]

Background

Sample Options are the pane next to sample controls that allow users to manipulate the sample. This separate pane is either generated using attributes, or manually assigned with a UserControl of your choice, and an instance of the sample is provided for manipulation. This approach keeps the XAML and C# presented to the user clean and succinct.

Problems

In order to create sample options, samples in CommunityToolkit vNext and CommunityToolkit Labs currently use either:

• Generated option attributes, or
• Directly insert the UI for manipulating the sample into the sample itself.

The second method is problematic, as it makes the source code for the sample hard to read and can lead to an inconsistent user experience. This issue arises due to a lack of documentation and samples for using a fully custom options pane.

Solution

For components with option-related UI inside their samples, migrate to using a custom options pane instead. This will improve the readability of the source code and provide a more consistent user experience.