-
-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mouse clicks (&mkp LCLK etc) stopped working? #2798
Comments
I have no idea the state of the MoErgo fork, I'd recommend trying against ZMK |
I think it might be that the HID report descriptor was updated between their previous firmware versions and 24.01 that they released recently. Given that, it is worth trying https://zmk.dev/docs/features/bluetooth#refreshing-the-hid-descriptor. Also note that the header include has changed: https://zmk.dev/docs/keymaps/behaviors/mouse-emulation#mouse-emulation-defines That being said, Pete is right, this is not the right venue to debug this. If you want to follow up please post on their Discord, I'll see it and respond. |
Thank you for the valuable inputs and apologies for opening the issue here. I performed a reset factory, but couldn't get it to work, not sure if am performing this corretly. I will discuss this in Discord as well. For now, I was able to build the previous version like this siadat/glove80-zmk-config@d9c8bd3#diff-4d2a8eefdf2a9783512a35da4dc7676a66404b6f3826a8af9aad038722da6823R11. |
Mouse clicking used to work a few weeks ago, but it stopped working when I built the same layout today. I use Glove80's layout editor and builder with the keymap pasted at the end.
The way I enabled clicks:
#include <dt-bindings/zmk/mouse.h>
&mkp LCLK
,&mkp MCLK
,&mkp RCLK
Afaict, Glove80 web layout builder (https://my.glove80.com/#/layout/) uses a fork of ZMK, probably https://github.com/moergo-sc/zmk. I wonder if the following PR changed anything related to this: #2477
I will see if I can reproduce it in https://github.com/siadat/glove80-zmk-config
Keymap file
The text was updated successfully, but these errors were encountered: