d57fb84557
This pull request brings back the "Base Layer" page, now renamed to
"Defaults", and the "Reset to inherited value" buttons. The scope of
inheritance for which buttons will display has been widened.
The button will be visible in the following cases:
The user has set a setting for the current profile, and it overrides...
1. ... something in profiles.defaults.
2. ... something in a Fragment Extension profile.
3. ... something from a Dynamic Profile Generator.
4. ... something from the compiled-in defaults.
Compared to the original implementation of reset arrows, cases (1), (3)
and (4) are new. Rationale:
(1) The user can see a setting on the Defaults page, and they need a way
to reset back to it.
(3) Dynamic profiles are not meaningfully different from fragments, and
users may need a way to reset back to the default value generated
for WSL or PowerShell.
(4) The user can see a setting on the Defaults page, **BUT** they are
not the one who created it. They *still* need a way to get back to
it.
To support this, I've introduced another origin tag, "User", and renamed
"Custom" to "None". Due to the way origin/override detection works¹, we
cannot otherwise disambiguate between settings that came from the user
and settings that came from the compiled-in defaults.
Changes were required in TerminalSettings such that we could construct a
settings object with a profile that does not have a GUID. In making this
change, I fixed a bit of silliness where we took a profile, extracted
its guid, and used that guid to look up the same profile object. Oops.
I also fixed the PropertyChanged notifier to include the
XxxOverrideSource property.
The presence of the page and the reset arrows is restricted to
Preview- or Dev-branded builds. Stable builds will retain their current
behavior.
¹ `XxxOverrideSource` returns the profile *above* the current profile
that holds a value for setting `Xxx`. When the value is the
compiled-in value, `XxxOverrideSource` will be `null`. Since it's
supposed to be the profile above the current profile, it will also be
`null` if the profile contains a setting at this layer.
In short, `null` means "user specified" *or* "compiled in". Oops.
Fixes #10430
Validation
----------
* [x] Tested Release build to make sure it's mostly arrow-free (apart from fragments)
69 lines
2.9 KiB
XML
69 lines
2.9 KiB
XML
<?xml version="1.0"?>
|
|
<featureStaging xmlns="http://microsoft.com/TilFeatureStaging-Schema.xsd">
|
|
<!-- See doc/feature_flags.md for more info. -->
|
|
<feature>
|
|
<name>Feature_ReceiveIncomingHandoff</name>
|
|
<description>OpenConsole should be able to receive incoming connections</description>
|
|
<stage>AlwaysEnabled</stage>
|
|
<alwaysDisabledBrandingTokens>
|
|
<brandingToken>WindowsInbox</brandingToken>
|
|
</alwaysDisabledBrandingTokens>
|
|
</feature>
|
|
|
|
<feature>
|
|
<name>Feature_EditableActionsPage</name>
|
|
<description>The Actions page in the settings UI should allow users to edit actions.</description>
|
|
<stage>AlwaysEnabled</stage>
|
|
<alwaysDisabledReleaseTokens/>
|
|
</feature>
|
|
|
|
<feature>
|
|
<name>Feature_AttemptHandoff</name>
|
|
<description>conhost should try to hand connections over to OpenConsole</description>
|
|
<stage>AlwaysDisabled</stage>
|
|
<alwaysEnabledBrandingTokens>
|
|
<brandingToken>WindowsInbox</brandingToken>
|
|
</alwaysEnabledBrandingTokens>
|
|
</feature>
|
|
|
|
<feature>
|
|
<name>Feature_ConhostDxEngine</name>
|
|
<description>Controls whether conhost supports the DX engine and the UseDx registry key</description>
|
|
<stage>AlwaysEnabled</stage>
|
|
<alwaysDisabledBrandingTokens>
|
|
<brandingToken>WindowsInbox</brandingToken>
|
|
</alwaysDisabledBrandingTokens>
|
|
</feature>
|
|
<feature>
|
|
<name>Feature_DxEngineShaderSupport</name>
|
|
<description>Controls whether the DX engine is built with shader support.</description>
|
|
<stage>AlwaysEnabled</stage>
|
|
<alwaysDisabledBrandingTokens>
|
|
<brandingToken>WindowsInbox</brandingToken>
|
|
</alwaysDisabledBrandingTokens>
|
|
</feature>
|
|
|
|
<feature>
|
|
<name>Feature_UseNumpadEventsForClipboardInput</name>
|
|
<description>Controls whether the clipboard converter (and ConPTY InputStateMachine) uses Numpad events instead of UChar</description>
|
|
<stage>AlwaysDisabled</stage>
|
|
<alwaysEnabledBrandingTokens>
|
|
<!--
|
|
To reduce the risk of compatibility issues inside Windows, we're going to continue using the old
|
|
version of GetQuickCharWidth to determine whether a character should be synthesized into numpad
|
|
events.
|
|
-->
|
|
<brandingToken>WindowsInbox</brandingToken>
|
|
</alwaysEnabledBrandingTokens>
|
|
</feature>
|
|
|
|
<feature>
|
|
<name>Feature_ShowProfileDefaultsInSettings</name>
|
|
<description>Whether to show the "defaults" page in the Terminal settings UI</description>
|
|
<id>10430</id>
|
|
<stage>AlwaysEnabled</stage>
|
|
<!-- This feature will not ship to Stable until it is complete. -->
|
|
<alwaysDisabledReleaseTokens />
|
|
</feature>
|
|
</featureStaging>
|