README: More Technical: doesn't say where keymaps/ is #290
Comments
|
Thanks for the feedback! Done. |
ryaninvents
pushed a commit
to ryaninvents/qmk_firmware
that referenced
this issue
Aug 12, 2016
BlueTufa
pushed a commit
to BlueTufa/qmk_firmware
that referenced
this issue
Aug 6, 2021
- symptom, being unable to change any layer or (kc) style codes once they were set in the UI. - Use correct regenerated keycode, not the imported keycode, so export works correctly again Longer description: A coding error. When we import codes from a JSON file we parse them and set their original KC_CODE to that configurator can export them correctly again. e.g. TG(3) would be internally referred to as TG(layer). When exported it would save TG(3). The bug was on import. The key was correctly parsed as an layer key, but then it was incorrectly imported to be TG(3) instead of TG(layer). This caused the export to save the wrong data because the code could not be correctly looked up, so it was treated like an ANY key. This also affected any container keys, which would create a similarly bogus key mapping.
jiaxin96
pushed a commit
to Oh-My-Mechanical-Keyboard/qmk_firmware
that referenced
this issue
Dec 20, 2022
* Added support for Velocifire Sun20pro numpad * Cleaned up formatting * Added default keymap
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I got a little lost on step 4: it says to copy
keymaps/default/keymap.celsewhere, but it doesn't mention thatkeymaps/is in…/qmk_firmware/keyboard/ergodox_ez. Could the instructions be updated to nudge the user in the right direction of the proper subirectory?The text was updated successfully, but these errors were encountered: