Repository navigation
Update profile subpages - #20336
Update profile subpages#20336
Conversation
|
|
||
| // Optional resource name for a secondary label shown beneath the primary label in | ||
| // search results (i.e. "Nav_ProfileDefaults/Content" for the profile-defaults page links). | ||
| // Empty for most entries. | ||
| // NOTE: wrapped in USES_RESOURCE() (when set) for the same compile-time validation as ResourceName. | ||
| wil::zwstring_view SecondaryResourceName; |
There was a problem hiding this comment.
The SecondaryResourceName changes in this file conflict with #20199 . They both have basically the same implementation with a different variable name. The consumer in SearchIndex.cpp also needs to be updated.
I'll go in and make this match the one from the other one.
There was a problem hiding this comment.
Actually, turns out that it's a more complex merge conflict. I'll just have to deal with it when we start merging these PRs into main.
236afe3 to
3faedd8
Compare
This comment has been minimized.
This comment has been minimized.
|
Updated base branch (PR #20232) with a SettingsExpander collapse animation fix. Force pushed a rebase off of that. |
3ed0ad5 to
ae1f638
Compare
Removes most of the em-dashes in our repo. Any related to the Settings UI are covered in #20336.
| void _OnClick(const Windows::Foundation::IInspectable& sender, const Windows::UI::Xaml::RoutedEventArgs& args); | ||
| hstring _GenerateOverrideMessage(const Windows::Foundation::IInspectable& settingOrigin); | ||
|
|
||
| Windows::UI::Xaml::Data::INotifyPropertyChanged _subscribedTarget{ nullptr }; |
There was a problem hiding this comment.
will this create a reference cycle, where the page is holding a strong reference to the button and the button is holding a strong reference to the page? are we going to leak a bunch of SUI stuff when we close it? (honestly don't know)
There was a problem hiding this comment.
There's no reference cycle here, but there was a memory leak because the subscription was never revoked. Fixed that.
For reference (heh), the reference graph is more like:
- Page -- strong ref --> reset button
- reset button -- strong ref --> view model (aka
Target) - view model -- weak ref --> button (now
_targetPropertyChangedRevoker)
This comment has been minimized.
This comment has been minimized.
This comment was marked as resolved.
This comment was marked as resolved.
906e7b9 to
24f401c
Compare
|
Dustin L. Howett (@DHowett) this one should be good to go now. |
So, the way I've justified it to myself is that a task is part of a profile. A profile consists of three things: a task (what do we run, how do we run it?), behaviors (does OSC 777 work? what happens when the task exits? can the task write to the clipboard?) and appearance (you know this one) Everything on this page is part of the profile. So it doesn't seem wrong or even a violation of the terms we're currently using to add Task, as a header, inside the profile page. -- Conversely I could argue that the current setup is incorrect because it says "Welcome to the Profile editor, would you like to edit the Profile part of the Profile?" And inside that box is only the command line, starting directory, etc.; and then I can imagine a user asking "If that's the profile, what are these other things in the profile page?" |
|
FWIW, a proposed glossary:
Execution/launching turns a profile into a session, and the session is put into a pane. |
|
One place where this distinction matters is that when we get a handoff, all we have is a task (!) and we need to collect it with some sane behaviors and a sane appearance and pass it off as a session to be hosted in a pane. |
…/profile-rejuv # Conflicts: # src/cascadia/TerminalSettingsEditor/MainPage.cpp # src/cascadia/TerminalSettingsEditor/Resources/de-DE/Resources.resw # src/cascadia/TerminalSettingsEditor/Resources/es-ES/Resources.resw # src/cascadia/TerminalSettingsEditor/Resources/fr-FR/Resources.resw # src/cascadia/TerminalSettingsEditor/Resources/it-IT/Resources.resw # src/cascadia/TerminalSettingsEditor/Resources/ja-JP/Resources.resw # src/cascadia/TerminalSettingsEditor/Resources/ko-KR/Resources.resw # src/cascadia/TerminalSettingsEditor/Resources/pt-BR/Resources.resw # src/cascadia/TerminalSettingsEditor/Resources/qps-ploc/Resources.resw # src/cascadia/TerminalSettingsEditor/Resources/qps-ploca/Resources.resw # src/cascadia/TerminalSettingsEditor/Resources/qps-plocm/Resources.resw # src/cascadia/TerminalSettingsEditor/Resources/ru-RU/Resources.resw # src/cascadia/TerminalSettingsEditor/Resources/zh-CN/Resources.resw # src/cascadia/TerminalSettingsEditor/Resources/zh-TW/Resources.resw
Dustin L. Howett (DHowett)
left a comment
There was a problem hiding this comment.
I can't be the last approver, but I do approve everything before this
| Automation::AutomationProperties::SetName(NewKeyBinding(), RS_(L"EditAction_NewKeyBinding/Header")); | ||
| } | ||
|
|
||
| // The browse buttons live inside data templates, so we can't reference them by name. |
There was a problem hiding this comment.
i feel like we could just use their Uids in the resw file
…26 22:10:12 (#20688) Co-authored-by: Console Service Bot <consvc@microsoft.com>
|






Summary of the Pull Request
Updates the individual profile pages to include:
SettingsResetButton: a new "reset value" buttonDetailed Description of the Pull Request / Additional comments
IInheritableViewModel: interface exposingHasSetting(),ClearSetting(), andSettingOverrideSource()Profiles_UnfocusedAppearance.h/cpp/idl/xaml: the new unfocused appearance pageFormatAccessibleName()andColorToHexString()to deduplicate code that creates accessible names for SettingsExpanders across the entire SUIValidation Steps Performed
PR Checklist
Related to #17000