does that actually require recompiling? i would have expected that via/vial would be able to do that
1 Like
Yes. Via only change keybind, not Numlock behavior.
You also canât do advanced layering with Via. No tap dance, for instance. No script, no numlock (which is just script), etc.
And Via (web interface) actually straight up dont work with even the main qwerty keyboard, which have 4 layers, and they enter different layer depend on the current layer of the keyboard through a script (for the Fn lock) â one with the F1 through F12 on base layer, one with the Fn key pressed on the base layer, one with the media control (volume, settings, etc), and one for the Fn key pressed on the media control. You can map normal keys all you want, but if you want to change this 4-layer toggle behavior, you need to recompile.
Missed opportunity for the ARGB macropad, you can use backlight on a key for the numlock.
Fortunately, the QMK documentation is decent enough. But the QMK toolbox donât work with frameworks, and the framework keyboard github repo is kind ofa nightmare, with like, 10 forks off of different stages, and 10,000 other boards to get you distracted.
Not saying it isnât a mess, but once you know what you need, it feels no harder than normal. Regarding the 10k other boards, well, thatâs how QMK from source always is. You just make a shortcut to the folder for the keyboard(s) youâre working on & you never see the rest.
The firmware version thatâs shipping still looks to be v0.2.9, so:
clone -b v0.2.9 https://github.com/FrameworkComputer/qmk_firmware.git
Custom QMK firmware? - #14 by MJ1
Clear eeprom step: Custom QMK firmware? - #31 by MJ1
2 Likes