neko VS ebitenui

I think it's relatively straightforward? Each mouse should be generating input events, it's "just" a matter of "Mouse1 += (100x, 200y)", "Mouse2 += (-3x, -5y)" and keeping track of a virtual cursor/pointer position that the "real" cursor should jump to depending on which mouse is generating input events.

...and for the use cases, having an extended desktop (eg: airplay to HDTV mounted on the wall) and being able to have your primary "desktop" mouse 100% glued to your main screen, but a secondary "click the play next video button on the tv" mouse is genius!

I'm pretty sure if somebody were sufficiently innovative they could paint a bullseye/target around the virtual cursors with some sort of minor performance penalty (a-la: xNeko - https://github.com/crgimenes/neko).

I'll just throw this out there. I am building a ui framework for use with ebitengine. It's at 300ish stars and I love when people throw out PRs. If your interested in helping out, feel free to check it out and join the discord: https://github.com/ebitenui/ebitenui

If you're interested I could use help with my library. There are all levels of changes I could use help with from novice engineer to architect level. Feel free to reach out and we can discuss it a bit. https://github.com/ebitenui/ebitenui

I've contacted the https://github.com/ebitenui/ebitenui maintainer and we may add the missing bits, so it's easier to make the cross-platform/input-device interfaces.

If you're familiar with Golang you can check this gui system out for ideas. It is very similar to what your suggesting. https://github.com/ebitenui/ebitenui