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

Adding back Support for Keychron K3 v2 to sn32_develop #437

Open
wants to merge 8 commits into
base: sn32_develop
Choose a base branch
from

Conversation

macaholik
Copy link

Description

Added back support for Keychron K3 v2 ISO from the sn32_master branch

Types of Changes

  • Core
  • Bugfix
  • New feature
  • Enhancement/optimization
  • Keyboard (addition or update)
  • Keymap/layout (addition or update)
  • Documentation

Issues Fixed or Closed by This PR

Checklist

  • My code follows the code style of this project: C, Python
  • I have read the PR Checklist document and have made the appropriate changes.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • I have tested the changes and verified that they work and don't break anything (as well as I can manage).

@shirok1
Copy link

shirok1 commented Jan 5, 2025

Hello, I would like to port Keychron K6 support from old branch. Are there any reminders/instructions to follow? Or is it as simple as copying old code and paste them to the develop branch?

@macaholik
Copy link
Author

Hello, I would like to port Keychron K6 support from old branch. Are there any reminders/instructions to follow? Or is it as simple as copying old code and paste them to the develop branch?

You can find infos about how to add back support in this issue #420

*/
[MAC_FN] = LAYOUT_75_iso(
/* 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 */
_______, KC_F1, KC_F2, KC_F3, KC_F4, KC_F5, KC_F6, KC_F7, KC_F8, KC_F9, KC_F10, KC_F11, KC_F12, QK_BOOT, _______, RGB_M_P ,

Choose a reason for hiding this comment

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

small suggestion. From the docs the convention for QK_BOOT seems to to be Fn+Esc. This changes this which will likely confuse users that didn't bother reading the keymap thoroughly. I would propose to move it back to the the Esc key again.

@Swiftb0y
Copy link

@macaholik Thanks for picking this up. I've flashed the default keymap to my device and can confirm its working well so far.

Comment on lines +84 to +89
_______, KC_F1, KC_F2, KC_F3, KC_F4, KC_F5, KC_F6, KC_F7, KC_F8, KC_F9, KC_F10, KC_F11, KC_F12, QK_BOOT, _______, RGB_M_P ,
_______, _______, _______, _______, _______, _______, _______, _______, _______, _______, _______, _______, _______, _______, _______ ,
_______, _______, _______, _______, _______, _______, _______, _______, _______, _______, _______, _______, _______, _______ ,
_______, _______, _______, _______, _______, _______, _______, _______, _______, _______, _______, _______, _______, _______, _______ ,
_______, _______, _______, _______, _______, _______, _______, _______, _______, _______, _______, _______, _______, RGB_SAI, _______ ,
_______, _______, _______, _______, _______, _______, _______, RGB_HUD, RGB_SAD, RGB_HUI

Choose a reason for hiding this comment

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

Many of the RGB_* keycode have been deprecated since May so this would be a good time to update them.

"console": false,
"extrakey": true,
"mousekey": false,
"nkro": true,

Choose a reason for hiding this comment

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

NKRO doesn't seem to be enabled by default afaict. Is this supposed to do that?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants