most of the gaming mice with "onboard memory" will function this way. programming stored in the mouse.
- i have a cm storm recon that works like this. you program via their programming utility, it's written to the mouse, then you can use the mouse on other systems and it retains the programming (NOT being remapped by app on host computer)
- just read through the descriptions, it should say stored in the mouse, or onboard memory, etc...
there is also the "
Ploopy" mouse & trackball, which run the same firmware that we use on our keyboards (
QMK). they accomplished this by supporting the PMW3360 optical sensor in the keyboard firmware. they also support
VIA, an on-the-fly remapping utility for QMK which alleviates the need to reflash the mouse every time you want to change a button.
- if you're familliar with QMK, you can see how exciting this is.
- QMK firmware:
https://github.com/qmk/qmk_firmwarethere are also a handful of DIY mouse projects based around the PMW3360 optical sensor if you want to go that route. search around. some are running a less fully featured firmware than the ploopy ones, and i've seen others use arduino programming.