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

Added support for EnvKB 60F V2 #24642

Open
wants to merge 5 commits into
base: develop
Choose a base branch
from

Conversation

Envious-Data
Copy link
Contributor

Separated boards into folders mirroring board revisions, added support for V2 of the board.

Description

Moved V1 and V2 into their own folders, added V2 keymap.c, keyboard.json and a readme.me in each folder.
Compiled and tested the generated UF2 files on both versions of my keyboards to ensure they work as intended.

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

  • Added support for EnvKB60F V2

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).

fixed a small oversight in keymap.c
@zvecr zvecr changed the base branch from master to develop November 26, 2024 18:35
keyboards/enviousdesign/60f/v2/readme.md Outdated Show resolved Hide resolved
keyboards/enviousdesign/60f/v1/readme.md Outdated Show resolved Hide resolved
keyboards/enviousdesign/60f/readme.md Outdated Show resolved Hide resolved
keyboards/enviousdesign/60f/readme.md Outdated Show resolved Hide resolved
keyboards/enviousdesign/60f/v2/keymaps/default/keymap.c Outdated Show resolved Hide resolved
KC_TAB, KC_Q, KC_W, KC_E, KC_R, KC_T, KC_Y, KC_U, KC_I, KC_O, KC_P, KC_LBRC, KC_RBRC, KC_BSLS,
KC_CAPS, KC_A, KC_S, KC_D, KC_F, KC_G, KC_H, KC_J, KC_K, KC_L, KC_SCLN, KC_QUOT, KC_NUHS, KC_ENT,
KC_LSFT, KC_NUBS, KC_Z, KC_X, KC_C, KC_V, KC_B, KC_N, KC_M, KC_COMM, KC_DOT, KC_SLSH, KC_RSFT,
KC_LCTL, KC_LWIN, KC_LALT, KC_SPC, KC_SPC, KC_SPC, KC_RALT, KC_RWIN, _______, KC_RCTL
Copy link
Member

@zvecr zvecr Nov 26, 2024

Choose a reason for hiding this comment

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

  • Keycode in layout: Press the key mapped to QK_BOOT. In the pre-supplied keymaps it is on the second layer, replacing the Tab key.

KC_TRANS on a base layer seems like an unusual choice given it doesnt align with the readme comment and the v1 has a 2nd layer?

keyboards/enviousdesign/60f/v1/readme.md Outdated Show resolved Hide resolved
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.

4 participants