qmk_firmware/keyboards/massdrop/ctrl/keymaps/foxx1337
Ryan 5e4b076af3
Remove legacy keycodes, part 5 (#18710)
* `KC_SLCK` -> `KC_SCRL`
* `KC_NLCK` -> `KC_NUM`
2022-10-15 22:29:43 +01:00
..
config.h Remove RGBLIGHT_ANIMATION and clean up effect defines for L-Q (#18727) 2022-10-15 09:55:40 -07:00
hid_protocol.c [Keymap] foxx1337 for Massdrop CTRL with raw HID (#8692) 2021-11-05 13:36:27 +11:00
hid_protocol.h Change DRIVER_LED_COUNT to {LED,RGB}_MATRIX_LED_COUNT (#18399) 2022-09-23 22:46:23 +10:00
keymap.c Remove legacy keycodes, part 5 (#18710) 2022-10-15 22:29:43 +01:00
README.md [Keymap] foxx1337 for Massdrop CTRL with raw HID (#8692) 2021-11-05 13:36:27 +11:00
rgb_matrix_user.inc Change DRIVER_LED_COUNT to {LED,RGB}_MATRIX_LED_COUNT (#18399) 2022-09-23 22:46:23 +10:00
rules.mk [Keymap] foxx1337 for Massdrop CTRL with raw HID (#8692) 2021-11-05 13:36:27 +11:00

Massdrop CTRL default layout with raw HID protocol

This represents my current layout, with filtered out effects, personal defaults, added inactivity timeout (for rgbmatrix) and a HID protocol example.

To test that this is working, there's a user application I'm using to help with development on my GitHub.

Currently all the HID operations defined in the protocol are callable from the user application:

  • hello: gets the string "CTRLHID 1.0.0"
  • lights: toggles the rgbmatrix on/off
  • led n #RRGGBB: colors the specified led. Valid n from 0 to 117 (87-117 are on the edge)
  • leds start #RRGGBB #RRGGBB #RRGGBB ...: colors the range of leds from start
  • mode n: switches to the specific rgbmatrix mode. Use the last one, 11, to test the led operations listed above