-
-
Notifications
You must be signed in to change notification settings - Fork 38.8k
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 my personal keymap #420
Conversation
# Conflicts: # keyboard/kc60/keymaps/default/compiled.hex # keyboard/kc60/keymaps/ws2812/compiled.hex
Yeah! It looks like you have some conflicts in your .hex files - can you revert them and recompile? |
Also am I reading this correctly that there are changes to the default layout? The RGB stuff isn't on everyone's KC60 and shouldn't be part of the default layout. |
Yeah, it looks like there are some leftovers here from #419 - if you could take care of those as well, @stanleylai, that would be awesome! |
The stock KC60 files were reverted earlier, so no RGB code exists there anymore. But they seemed to have been grouped together with the RGB commits anyway. Reverted from 3f6fac4 this time, should hopefully be better and clearer. |
Awesome - thanks! :) |
* Added WS2812 support for KC60 * Reorganized WS2812 support into its own keymap * Fixed relative link in README * Moved WS2812 mention in README to the bottom * Fixed titling in WS2812 README * Reverted KC60 Makefile and default keymap back * Moved RGB specific config.h to ws2812 keymap folder * Added my personal keymap * Updated compiled hex * Reverted KC60 files to 3f6fac4 before pull request qmk#419
Are sharing personal keymaps a thing? Feel free to close this pull request otherwise.