-
Notifications
You must be signed in to change notification settings - Fork 8.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Persist Runtime TabTitle and Maximize/Focus/Fullscreen states #12073
Changes from all commits
f70126b
9f98052
b089426
d43bd9b
2408085
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -19,6 +19,11 @@ namespace winrt::Microsoft::Terminal::Settings::Editor::implementation | |
|
||
INITIALIZE_BINDABLE_ENUM_SETTING(FirstWindowPreference, FirstWindowPreference, FirstWindowPreference, L"Globals_FirstWindowPreference", L"Content"); | ||
INITIALIZE_BINDABLE_ENUM_SETTING(LaunchMode, LaunchMode, LaunchMode, L"Globals_LaunchMode", L"Content"); | ||
// More options were added to the JSON mapper when the enum was made into [Flags] | ||
// but we want to preserve the previous set of options in the UI. | ||
_LaunchModeList.RemoveAt(7); // maximizedFullscreenFocus | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. My only concern is that we should file a followup and reference it in the code -- otherwise we'll forget. We should get to this during the overhaul. Heck, the followup might even be "make the launch mode UI a collection of flags" |
||
_LaunchModeList.RemoveAt(6); // fullscreenFocus | ||
_LaunchModeList.RemoveAt(3); // maximizedFullscreen | ||
INITIALIZE_BINDABLE_ENUM_SETTING(WindowingBehavior, WindowingMode, WindowingMode, L"Globals_WindowingBehavior", L"Content"); | ||
|
||
// BODGY | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -919,6 +919,18 @@ | |
<value>Maximized focus</value> | ||
<comment>An option to choose from for the "launch mode" setting. Opens the app maximized and in focus mode.</comment> | ||
</data> | ||
<data name="Globals_LaunchModeMaximizedFullscreen.Content" xml:space="preserve"> | ||
<value>Maximized full screen</value> | ||
<comment>An option to choose from for the "launch mode" setting. Opens the app maximized and in full screen.</comment> | ||
</data> | ||
<data name="Globals_LaunchModeFullscreenFocus.Content" xml:space="preserve"> | ||
<value>Full screen focus</value> | ||
<comment>An option to choose from for the "launch mode" setting. Opens the app in full screen and in focus mode.</comment> | ||
</data> | ||
<data name="Globals_LaunchModeMaximizedFullscreenFocus.Content" xml:space="preserve"> | ||
<value>Maximized full screen focus</value> | ||
<comment>An option to choose from for the "launch mode" setting. Opens the app maximized in full screen and in focus mode.</comment> | ||
</data> | ||
Comment on lines
+922
to
+933
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Do we actually need these since we're removing them in Launch.cpp? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Technically this was the way that had the least amount of code. Basically the macro currently used attempts to look up every possible enum value in the localization files and so it would crash if it didn't exist. I could've written a different macro/manually write the code so it didn't try the values being filtered out. But since I added the text for the one option I was just lazy and left it in. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I appreciate this actually. Thanks. |
||
<data name="Profile_BellStyle.Header" xml:space="preserve"> | ||
<value>Bell notification style</value> | ||
<comment>Header for a control to select the how the app notifies the user. "Bell" is the common term in terminals for the BEL character (like the metal device used to chime).</comment> | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
typically I'd prefer a separate PR just for the sake of potential easy reverts, but in this case meh it's fine, this is a simple enough change
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're not wrong. I just happened to be looking to fix multiple open issues so the runtime text that took 2 minutes and the window state tracking that took an afternoon ended up in the same PR.