varl/qmk_firmware
1
0
Fork 0
forked from forks/qmk_firmware
Code Pull requests Activity
qmk_firmware/keyboards/massdrop/ctrl/keymaps/foxx1337
History
foxx1337 2ac2695cb5
[Keymap] foxx1337 for Massdrop CTRL with raw HID (#8692) 
* [Keymap] foxx1337's personal keymap

* Add keymap based on ctrl default
* Add 5 minute rgb matrix timeout

* Add foxx1337 layout defaults

* Add raw HID communication protocol

* Add rgbmatrix to the raw HID protocol

* Add readme

* Modernize ctrl, shift, alt mods detection

* Add GPL like copyright headers
2021-11-05 13:36:27 +11:00
..
config.h [Keymap] foxx1337 for Massdrop CTRL with raw HID (#8692) 2021-11-05 13:36:27 +11:00
hid_protocol.c [Keymap] foxx1337 for Massdrop CTRL with raw HID (#8692) 2021-11-05 13:36:27 +11:00
hid_protocol.h [Keymap] foxx1337 for Massdrop CTRL with raw HID (#8692) 2021-11-05 13:36:27 +11:00
keymap.c [Keymap] foxx1337 for Massdrop CTRL with raw HID (#8692) 2021-11-05 13:36:27 +11:00
README.md [Keymap] foxx1337 for Massdrop CTRL with raw HID (#8692) 2021-11-05 13:36:27 +11:00
rgb_matrix_user.inc [Keymap] foxx1337 for Massdrop CTRL with raw HID (#8692) 2021-11-05 13:36:27 +11:00
rules.mk [Keymap] foxx1337 for Massdrop CTRL with raw HID (#8692) 2021-11-05 13:36:27 +11:00

README.md

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