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

Why is NKRO_ENABLE disabled by default? #555

Closed
lindhe opened this issue Jul 24, 2016 · 1 comment
Closed

Why is NKRO_ENABLE disabled by default? #555

lindhe opened this issue Jul 24, 2016 · 1 comment

Comments

@lindhe
Copy link
Contributor

lindhe commented Jul 24, 2016

Why is NKRO_ENABLE set to off by default? Is there any disadvantage I should know of, before considering enabling it? It feels like an all good thing, so I was baffled it was off by default.

Thanks for your great work with this repo; it's a joy reading through good documentation.

@ezuk
Copy link
Contributor

ezuk commented Jul 27, 2016

In a nutshell, because it makes Windows cry. :) If you plug an NKRO-enabled keyboard into a machine running Windows, it may not recognize it.

Many thanks for your kind words on the repo and the docs! We've put a ton of work into those, so always makes me happy when people notice. :) Closing this issue for now, please reopen if you have any further questions.

@ezuk ezuk closed this as completed Jul 27, 2016
jiaxin96 pushed a commit to Oh-My-Mechanical-Keyboard/qmk_firmware that referenced this issue Oct 18, 2023
feat: vial keymap for mechwild/puckbuddy
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants