Using a custom *map and changing behavior of lock LEDs #699
Unanswered
RaoulDuke-Esq
asked this question in
Q&A
Replies: 2 comments 1 reply
-
you need |
Beta Was this translation helpful? Give feedback.
1 reply
-
You can use Also you may need to override default behaviour using Refer to There is some discussion about this around this comment. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi Hasu,
I'm loving ibmpc_usb and have been using the online GUI but I'm ready to take it to the next level. I tried creating a keymap_raoulduke-esq.c in my local fork and using make -f Makefile.atmega32u4 [KEYMAP=raoulduke-esq] but it said it could not find the keymap. How do I successfully build the firmware with a custom keymap when the default behavior is to use a unimap?
Once I've got my custom keymap working, I wanted to make my ibmpc devices use the lock lights as layer status indicators (i.e. Layer 0 active = NumLock light on; layer 1 active = CapsLock on, etc.). I use a Mac so numlock doesn't have a role, I don't use Capslock, and there's no scroll lock either so I figured layer lights would let me see these gorgeous green LEDs. Could you give me an example of how to use the a hook with my converter to make this happen?
Beta Was this translation helpful? Give feedback.
All reactions