Zach White
Zach White
Love what I'm seeing so far. One thing to keep in mind is that we'll want a light mode too for better accessibility.
Glad you were able to figure that out @karl-run! If you want to use more than one keyboard in the future here's something that builds on what you learned- you...
The helix board requires special flags passed to the make command which the API can't support. I'm afraid someone will have to some work to make it work on configurator.
`x` and `y` in KLE is a different concept. In KLE `x` and `y` default to 1 and 0 respectively and represent the offset from the previous key. In QMK...
``` "keymaps": { 'LAYOUT': ["yshrsmz","DivergeJM","losinggeneration","333fred","kim-kim","danielhklein","pitty","jojiichan","default"], 'LAYOUT_60_ansi': ['layout1', 'layout2'] } ```
https://github.com/qmk/qmk_api/issues/11 has been completed.
Some of the issues we've identified to solve: * [ ] Custom keycodes, such as `RAISE` and `LOWER` don't work * [ ] Some keyboards don't have default keymaps in...
I just came across this issue because I'm setting up flit for the first time on my first project. I thought I wanted a bypass flag when I got here,...
It would go into keymap.py. There is currently no way to specify a custom keycode in configurator exports. This issue is a step towards being able to specify custom keycodes...
It should go above the layer definition but yes you're on the right track there. The next step will be to extend a configurator export with `"custom_keycodes": ["CUSTOM1", "CUSTOM2"]` and...