So you still have to press “fn” after pressing AltGr? Do you have a drawn keymap? Maybe I can just use yours, if it seems to make sense, I’m was hesitant to use anything that did not have a keymap I could look at whenever I get frustrated though,
No, that’s not how it works. fn isn’t a key that sends a keycode to the computer; instead it changes layers, so the other keys on the keyboard send different keycodes to the computer. And the keys in question trigger a macro that sends a sequence of key presses (and releases) like this: right alt, a, e. So all you do is hold down fn (or whatever key you configure to switch to the layer where you have your compose key macros), and tap p (or whatever), and you’ll get æ.
I went ahead and made a working version of what I think you want. You’ll have to change one line, to make the compose() function send your Compose key of choice:
This sketch adds a layer called BOKMAL with the compose key shortcuts. It changes two keys on the QWERTY layer: right ctrl becomes a layer-shift key – when it’s held, the new layer is active; the any key becomes a toggle: press it once, and the BOKMAL layer becomes active, press it again, and it deactivates.
Please feel free to ask me any questions about how it works.
2 Likes
I should have understood that you did not have to actually press the FN key from the beginning, thanks for the nice explanation.
And thanks for the code! It works wonderfully, now I just have to figure out what to do with the keyboardio key. I can probably do that by myself. Your “BOKMAAL” looks a bit like what I tried to make in the beginning.
thank you ever so much! This will be the perfect keyboard to learn programming on. I’ll probably make more posts in the future after I get good at typing on this keyboard, then the next goal is to get good at hacking it.
1 Like
Now I do: