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.

Sign up for GitHub

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

Jump to bottom

WindowsTerminalUniversal won't receive Alt KeyUp's #6465

Closed
zadjii-msft opened this issue Jun 11, 2020 · 1 comment
Closed

WindowsTerminalUniversal won't receive Alt KeyUp's #6465

zadjii-msft opened this issue Jun 11, 2020 · 1 comment
Labels
Area-Input Related to input processing (key presses, mouse, etc.) Area-TerminalControl Issues pertaining to the terminal control (input, selection, keybindings, mouse interaction, etc.) Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Tag-Fix Doesn't match tag requirements Priority-3 A description (P3) Product-Terminal The new Windows Terminal.
Milestone
Terminal Backlog

Comments

@zadjii-msft
Copy link
Member

Follow up from #6461. That PR fixed Alt ups for the Win32 hosted Terminal, but we're still stuck without the Alt Ups on UWP. Since we don't have a traditional WndProc there, we can't just shuttle those events through.

We do however have a Dispatcher that we can use.

You should be able to get the alt key through the accelerator key event on the dispatcher. I think that's how system XAML consumes it.
@zadjii-msft zadjii-msft added Area-Input Related to input processing (key presses, mouse, etc.) Issue-Bug It either shouldn't be doing this or needs an investigation. Area-TerminalControl Issues pertaining to the terminal control (input, selection, keybindings, mouse interaction, etc.) Product-Terminal The new Windows Terminal. Priority-3 A description (P3) labels Jun 11, 2020
@zadjii-msft zadjii-msft added this to the Terminal Backlog milestone Jun 11, 2020
@ghost ghost added the Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting label Jun 11, 2020
@DHowett DHowett removed the Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting label Jun 11, 2020
@zadjii-msft
Copy link
Member Author

lol WindowsTerminalUniversal is dead. I'm closing this.

@ghost ghost added the Needs-Tag-Fix Doesn't match tag requirements label Dec 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Area-Input Related to input processing (key presses, mouse, etc.) Area-TerminalControl Issues pertaining to the terminal control (input, selection, keybindings, mouse interaction, etc.) Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Tag-Fix Doesn't match tag requirements Priority-3 A description (P3) Product-Terminal The new Windows Terminal.
Projects
None yet
Milestone
Terminal Backlog
Development

No branches or pull requests
2 participants
@DHowett @zadjii-msft