Add miscellaneous simple settings to the settings UI

[carlos-zamora]

Summary of the Pull Request

Adds the following settings to the settings UI:

• $profile.RainbowSuggestions
• $profile.CellWidth
• $global.SearchWebDefaultQueryUrl
• $global.EnableColorSelection
• $global.ShowAdminShield
• $global.EnableUnfocusedAcrylic

Additionally, the following settings have graduated from experimental 🎓:

• $profile.rightClickContextMenu
• $profile.RainbowSuggestions

Part of #10000

[carlos-zamora]

Noticed that this setting is compatibility.enableUnfocusedAcrylic. Any ideas why it's in the compatibility namespace? To me, it makes sense to have in the appearance page, but the compatibility namespace is making me second guess that it should be in the new compatibility page. Should we remove the compatibility prefix?

[DHowett]

I think it was more "OS compatibility" - unfocused acrylic is actually a different implementation of acrylic than usual. It has caused some issues in the past.

[carlos-zamora]

Demo

Interaction page

• $global.SearchWebDefaultQueryUrl
• $global.EnableColorSelection

Appearance page

• $global.ShowAdminShield
• $global.EnableUnfocusedAcrylic

Profile > Advanced

• $profile.RainbowSuggestions

Profile > Appearance

• $profile.CellWidth

[DHowett]

Suggested change

	<value>Experimental: Add key bindings to color selected text</value>
	<value>Experimental: Add key bindings to highlight selected text and to search for and highlight all instances selected text</value>

wording could use work, but more accurate

[carlos-zamora]

Changed to "Experimental: Add key bindings to highlight selected text and to search for and highlight all instances of selected text" (there was a missing "of")

I think that works. We can iterate on it if we get feedback.

[carlos-zamora]

Urgh, we have a problem:

It's because of the SettingContainer styling. See inline comments below

<Style TargetType="local:SettingContainer">
    <Setter Property="Margin" Value="0,4,0,0" />
    <Setter Property="IsTabStop" Value="False" />
    <Setter Property="MaxWidth" Value="1000" />
    <Setter Property="Template">
        <Setter.Value>
            <ControlTemplate TargetType="local:SettingContainer">
                <Grid AutomationProperties.Name="{TemplateBinding Header}"
                      Style="{StaticResource NonExpanderGrid}">
                    <Grid.ColumnDefinitions>
                        <ColumnDefinition Width="*" />
                        <ColumnDefinition Width="Auto" />
                    </Grid.ColumnDefinitions>
                    <!--  This StackPanel is the problem! I'm guessing the StackPanel makes it so that wrapping property
                        isn't applied because we _technically_ never wrap (even though wrap is set on the text block).
                        This doesn't occur with the HelpTextBlock below. Surprised this issue never came up for
                        localization!  -->
                    <StackPanel Style="{StaticResource StackPanelInExpanderStyle}">
                        <StackPanel Orientation="Horizontal">
                            <TextBlock Style="{StaticResource SettingsPageItemHeaderStyle}"
                                       Text="{TemplateBinding Header}" />
                            <Button x:Name="ResetButton"
                                    Style="{StaticResource SettingContainerResetButtonStyle}">
                                <FontIcon Glyph="&#xE845;"
                                          Style="{StaticResource SettingContainerFontIconStyle}" />
                            </Button>
                        </StackPanel>
                        <TextBlock x:Name="HelpTextBlock"
                                   Style="{StaticResource SettingsPageItemDescriptionStyle}"
                                   Text="{TemplateBinding HelpText}" />
                    </StackPanel>
                    <ContentPresenter Grid.Column="1"
                                      HorizontalAlignment="Right"
                                      VerticalAlignment="Center"
                                      Content="{TemplateBinding Content}" />
                </Grid>
            </ControlTemplate>
        </Setter.Value>
    </Setter>
</Style>

[DHowett]

let's put experimental on the next line. or since it's a subtitle, Experimental Setting

[DHowett]

(or explain the whole setting in there. Experimental: conhost-like Color Selection Adds blah blah blah to blah blah and also blah blah

[carlos-zamora]

Alright, I've reworded such that the header is shorter and I added additional details as the help text. Here's the result:

[DHowett]

hey @lhecker why is this STRING and not COMPILE?

[carlos-zamora]

I blame Copilot haha. Changed to COMPILE

[DHowett]

ಠ_ಠ

[lhecker]

Sorry, didn't see this. FMT_STRING used to be for doing compile-time checks but runtime formatting (compact assembly). Nowadays compile-time checks are always done.