4 ms·

If you've got a keyboard with QMK firmware, and mousekeys were enabled for it... you can just turn it on with https://www.caniusevia.com/ https://www.caniusevia

If you've got a keyboard with QMK firmware, and mousekeys were enabled for it... you can just turn it on with https://www.caniusevia.com/ https://www.caniusevia.com/ . One of my machines didn't have a mouse, so my next keyboard was a Keychron Q2 https://www.keychron.com/products/keychron-q2-qmk-custom-mechanical-keyboard https://www.keychron.com/products/keychron-q2-qmk-custom-mec... - I thought I was going to have to recompile the firmware for this but it's already on: https://github.com/Keychron/qmk_firmware/blob/master/keyboards/keychron/q2/ansi/rules.mk#L5 https://github.com/Keychron/qmk_firmware/blob/master/keyboar... ...you just need to map keys. It was very easy, so now fn-arrow and fn-return work as a mouse on anything I've attached it to so far. I got an rpi recently, only connected this, and was able to navigate the startup ui with no mouse.

gryn 3y ago
works on ZMK firmware too just not the main repo, but one of the forks mentioned in the main repo. the advantage with this is that it's cross platform.
- rgoulter 3y ago
  I think the biggest disadvantage to "do it in firmware" is it requires an external keyboard. (& the good ones which let your thumbs use more than one key are more expensive or diy). Using the keyboard to drive the mouse isn't a nice experience. -- But, it's nice to have in situations like "I use a bluetooth mouse, on desktop, and bluetooth isn't set up/working". I've found that useful for live ISOs.