Robert U
Robert U
It sounds like this is clearly a bug on the macOS side. While very unfortunate I'm not sure if there's something that can be down from the ZMK side. Maybe...
Which version of zmk are you running? I don't use Mac but apparently some connection issues have been fixed in the latest upgrade to zephyr 3.5 (see the blog post...
Also does the issue occur without the passkey option?
In either case probably better to ask on the zmk discord since the macros here don't affect the connections directly.
Behind the scenes, `ZMK_UNICODE_PAIR` is simply a Mod-morph that binds two ZMK Macros. I don't use Mac OS so I can't really help with this. I know others have reported...
The syntax looks fine. What's the update that you are referring to, and did it work before? Also do the other macros in your keymap work fine? It might be...
Unfortunately, without native ZMK support for unicode, it won't be possible to "hotswap" the OS. The best you can do is to create two separate layers with the corresponding unicode...
Just for completeness, to activate macOS, you would do: ```cpp // activate macOS-mode for helper script #undef OS_UNICODE_LEAD #undef OS_UNICODE_TRAIL #define OS_UNICODE_LEAD ¯o_press &kp LALT //
I tried to reproduce that error with fvwm 2.5.30 and various screen resolutions, but everything works fine there. I'll try to set up the newest version of fvwm some time...
They work on the led-branch. You will just need to add the bindings to where you want them on your keymap.