Raise-Firmware VS nano-trackball

I can point you to there https://github.com/Dygmalab/Raise-Firmware

Getting the Dygma Raise firmware to compile was mostly easy thanks to the Github instructions for the Dygma Firmware https://github.com/Dygmalab/Raise-Firmware. I'm on Windows and the documentation seems a little sparse for Windows compared to Mac/Linux which made me nervous that it might not work but it works great with Arduino IDE. The one hiccup I hit was a compilation error related to a "{build.version_flags}" not being defined. I worked around the issue by removing the reference to it in boards.txt. Looks like that was introduced in the linked commit, would be great if somebody from Dygma could take a look so others trying to build the firmware themselves don't also hit this: https://github.com/Dygmalab/Kaleidoscope-Bundle-Dygma/commit/8b526fca1841d70e30682128f0f35292d8cd7e94

 I was reading DygmaLab git repository and found this! It probably means ortholinear Raise is almost ready for sale? I find it interesting how they have 16 thumb keys in 2 rows.

By APIs do you mean the interface to the keyboard itself? The firmware used in v1 introduces “super keys” in place of “tapdance”, but if you are interacting directly with the keyboard you might want to take a look at the beta firmware on GitHub to understand the changes it makes https://github.com/Dygmalab/Raise-Firmware/blob/superkeys/Raise-Firmware.ino

You can ask our developer in our GitHub.

after this line you can put your code to alter it's behaviour or enable it in some keys of the default map above -> https://github.com/Dygmalab/Raise-Firmware/blob/master/Raise-Firmware.ino#L261

They are pushed to the repos in their own branch called fixFreeze2, to compile your own firmware you have to follow the instructions Here

To know the correlation between the position of the map sent and the actual keys in the keyboard, look here. There you should have everything you need, including the color map section. And all the documentation required is linked on the firmware repo 😊

Files and Links I used 1. Final Mod: https://www.printables.com/model/520579-ploopy-nano-btu-mod-with-zsa-moonlander-right-thum 2. Github for BTU Mod & Buying BTUs: https://github.com/gbrnt/ploopy-nano/tree/master/hardware/mechanicals-btu-mod 3. Ploopy Nano; github, kit on website 4. ML Thumb Pad Blanks: https://www.printables.com/model/232829-moonlander-thumb-pad-blanks 5. Original Mount Mod: https://www.printables.com/model/480064-ploopy-nano-mount-for-zsa-moonlander-keyboard

I have been using a Moonlander for a bit more than 2 years now and have been loving it! Up until a few months ago I used a Logitech M570 alongside it. Looking for a trackball at the office, too, I then went out and bought a Logitech M575 only to realize very quickly that it just is not the same. So my search for an alternative set in almost immediately. Luckily I was also following r/Trackballs and learned about the Ploopy Nano Trackball which I hoped would pair very nicely with my Moonlander. And indeed, it does! I am still getting used to the layout changes I had to make to accomodate the one missing thumb cluster but so far I am absolutely loving it!

Ploopy*

It’s a Ploopy Nano. Been using it, with any mouse buttons mapped to left keyboard half for about 6 months now and it’s really helped keep my hands pain free.

The Ballpoints predate my time in the Hardware group by a few years, but I'd be surprised if anyone that worked on those devices would have expected the color to be so nice on the device all these years later, and that the plastic wasn't too brittle to keep it in use today. Might just be easier to take something like the Ploopy Nano and make a case for it to meet your needs vs. trying to retro fit the Ballpoint.

alternatively, Ploopy Nano (no buttons) or Meishi Trackball

So far I've done 2 modifications in the form of Kaleidoscope plugins, both of which I've put up on Github for those curious: • Mouse Layer - This switches my homerow keys to mouse keys whenever mouse movement is detected: wallisc/Kaleidoscope-MouseLayer (github.com). I use to do this with Bazecor by creating a separate layer and manually switching to the layer using a layer shift, but found I used the layer so much that layer shifting became fatiguing for my finger. Then I heard of a modification in the ErgoMechKeyboards reddit where QMK was modified to trigger mouse keys on mouse which inspired me to try something similar. I'm a trackball user and I love this modification, it allows me to use the Ploopy Nano (https://ploopy.co/nano-trackball/) which has no mouse keys but I also enjoy it with my CST L-trac, which does have mouse keys but are stiff and generally less pleasant than the keyboard switches. For fun, I animate the color of all the keys I'm overriding with a rainbow shift effect, this is how it looks in action: https://imgur.com/a/ptOHkcS • Alt Tabber - This overrides certain keys when the left-alt is held. Primarily used for quick alt-tabbing: wallisc/Kaleidoscope-AltTabber (github.com). I have alt as a thumb key and using this I can change the F/J keys to turn into Tab so I can alt tab without moving my hand off the homerow. I also override 4->F4 because alt-f4 is handy. Currently I just set any overridden keys to red, but probably will update it to have some fun LED animations as well at some point Disclaimer: There's probably some inefficient code but at the very least it's fairly simple if people are just curious what a plugin code looks like.

I believe that one is the Ploppy Nano, you can get more information about it here: https://ploopy.co/nano-trackball/