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

Multiple Keyboard Remappings #22455

Closed
MaxBrandner opened this issue Dec 4, 2022 · 4 comments
Closed

Multiple Keyboard Remappings #22455

MaxBrandner opened this issue Dec 4, 2022 · 4 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@MaxBrandner
Copy link

Description of the new feature / enhancement

Make it possible to have a Layout selection.

Scenario when this would be used?

When you are programming or writing or gaming. you can imagine people to want different layouts for all of those but you can only make one keyborad remapping at the moment. Make it possible to add multiple and switch between them

Supporting information

No response

@MaxBrandner MaxBrandner added the Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams label Dec 4, 2022
@matipojo
Copy link

matipojo commented Jan 3, 2023

+1.

More ever, if I have two keyboards (e.g., my laptop keyboard and an external keyboard) I want to remap only missing keys on my laptop (media controls) but not on my external keyboard.

@kaeside
Copy link

kaeside commented Mar 1, 2023

@MaxBrandner I believe this is where layers come into effect.

On keyboards that have QMK, you can set up a layer for regular typing and one for gaming or as many as you would like.

Referring to @matipojo comment, I believe that something like per keyboard settings would address this.

For example on MacOS you can set it so that only the laptop Apple keyboard switches cmd with ctrl, but any other keyboard would ignore that setting.

@crutkas
Copy link
Member

crutkas commented Jul 7, 2023

In a perfect world, this would be done via #1460 but until we have a proper way to detect keys based on keyboard, /dup #1881 would be how we'd do this. You'd create some type of profile.

@microsoft-github-policy-service
Copy link
Contributor

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@microsoft-github-policy-service microsoft-github-policy-service bot added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams labels Jul 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

4 participants