I was messing around with the keyboard software, in https://keyboard.frame.work/, and I accidentally replaced the Function Lock in Layer 1. Pretty sure it was set as a Custom button, and not a default, so I cannot replace it.
For me it says Custom(65), does that help?
Yes! That was it. Just needed to put that in the ‘Any’ button. Thanks
Framework should really have some guide, or documentation at least, about how they have layers setup. As there are parts that most people would never know, without either frustrating trial and error, or looking at and understanding the firmware code.
Custom(65) is used instead of a regular layer change key because the regular ones do not save the current active layer to memory. A custom key like Framework added is the only way to have the FnLock state be persistent, preserved between reboots.
Internally you can see that Framework gave the custom key the name FN_LOCK, a nice understandable name. Via, the GUI seen at keyboard.frame.work, unfortunately shows the key as Custom(65)
, because Via is annoying & not the most user friendly for some reason. Note that Via is not made by the same dev team as qmk. QMK being the open source firmware that runs on the FWL16 keyboard.
I’ve passed your feedback along.
This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.