Skip to content
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

Add input scope startup setting #17953

Merged
merged 2 commits into from
Sep 24, 2024
Merged

Conversation

lhecker
Copy link
Member

@lhecker lhecker commented Sep 23, 2024

This adds a "defaultInputScope" setting, hooks it up to our TSF,
and exposes it as a setting in the UI under the startup page.
In order to stay close with the other language setting, I moved that
one from the appearance to the startup page as well.
20 out of the 26 files in this PR are boilerplate unfortunately.

Closes #17816

Validation Steps Performed

  • Install and use the Chinese IME
  • Launch WT
  • Chinese input ✅
  • Change setting to alphanumericHalfWidth
  • Restart WT
  • English input ✅

@microsoft-github-policy-service microsoft-github-policy-service bot added Issue-Task It's a feature request, but it doesn't really need a major design. Area-TerminalControl Issues pertaining to the terminal control (input, selection, keybindings, mouse interaction, etc.) Product-Terminal The new Windows Terminal. labels Sep 23, 2024
</ComboBox>
</local:SettingContainer>

<!-- Language -->
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not language, but different

Suggested change
<!-- Language -->
<!-- Default Input Scope -->

Comment on lines +422 to +423
InterlockedDecrement(&referenceCount);
return self->Release();
Copy link
Member

@DHowett DHowett Sep 24, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mind explaining this change? I can't fully grok it.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This ensures that self (aka parent aka the Implementation instance) stays alive for the duration of the request.

@DHowett DHowett merged commit fc606d2 into main Sep 24, 2024
20 checks passed
@DHowett DHowett deleted the dev/lhecker/17816-tsf-input-scope branch September 24, 2024 21:14
DHowett pushed a commit that referenced this pull request Sep 26, 2024
This adds a "defaultInputScope" setting, hooks it up to our TSF,
and exposes it as a setting in the UI under the startup page.
In order to stay close with the other language setting, I moved that
one from the appearance to the startup page as well.
20 out of the 26 files in this PR are boilerplate unfortunately.

Closes #17816

* Install and use the Chinese IME
* Launch WT
* Chinese input ✅
* Change setting to `alphanumericHalfWidth`
* Restart WT
* English input ✅

(cherry picked from commit fc606d2)
Service-Card-Id: PVTI_lADOAF3p4s4AmhmszgTTKAE
Service-Version: 1.21
DHowett pushed a commit that referenced this pull request Sep 26, 2024
This adds a "defaultInputScope" setting, hooks it up to our TSF,
and exposes it as a setting in the UI under the startup page.
In order to stay close with the other language setting, I moved that
one from the appearance to the startup page as well.
20 out of the 26 files in this PR are boilerplate unfortunately.

Closes #17816

## Validation Steps Performed
* Install and use the Chinese IME
* Launch WT
* Chinese input ✅
* Change setting to `alphanumericHalfWidth`
* Restart WT
* English input ✅

(cherry picked from commit fc606d2)
Service-Card-Id: PVTI_lADOAF3p4s4AmhmQzgTTKAI
Service-Version: 1.22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-TerminalControl Issues pertaining to the terminal control (input, selection, keybindings, mouse interaction, etc.) Issue-Task It's a feature request, but it doesn't really need a major design. Product-Terminal The new Windows Terminal.
Projects
Development

Successfully merging this pull request may close these issues.

Has the automatic switching input method function been canceled?
3 participants