KeyChord should just use the existing WinRT types instead of defining our own #1188

Open
opened 2026-01-30 22:18:33 +00:00 by claunia · 0 comments
Owner

Originally created by @zadjii-msft on GitHub (May 17, 2019).

Was looking at this in conjunction with resolving suggestions for #805. The XAML framework uses Windows::System::VirtualKey and Windows::System::VirtualKeyModifiers...is there a reason that Terminal should create their own types here that are now maintaining modifiers and enum values for something that already exists? Retrieving the keybindings with a KeyChord that has it's own values is proving to be challenging using them anywhere in the UI due to different types and not being able to cast them accordingly well.

Originally posted by @timheuer in https://github.com/microsoft/terminal/pull/748#issuecomment-493255788

Originally created by @zadjii-msft on GitHub (May 17, 2019). Was looking at this in conjunction with resolving suggestions for #805. The XAML framework uses ```Windows::System::VirtualKey``` and ```Windows::System::VirtualKeyModifiers```...is there a reason that Terminal should create their own types here that are now maintaining modifiers and enum values for something that already exists? Retrieving the keybindings with a ``KeyChord`` that has it's own values is proving to be challenging using them anywhere in the UI due to different types and not being able to cast them accordingly well. _Originally posted by @timheuer in https://github.com/microsoft/terminal/pull/748#issuecomment-493255788_
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#1188