In a multi-monitor setup, i.e. with multiple displays connected, if the screens are different sizes, or they're configured strangely, the overall virtual screen space can be non-rectangular.
Currently, the mouse moves across screens seamlessly where they connect, but if it moves into the dead space, it triggers Manual Takeback mode, because the mouse stops following the position it tries to set it to, so it assumes the user moved a physical mouse.
Instead it should take non-rectangular bounds into account and collide with the borders. If it hits a dead zone horizontally, it should continue to move vertically, and visa versa, as well as being able to move back away from the dead zone of course.
Assorted notes:
- Switching to sending relative mouse movements would impact this feature, but not necessarily help fix it (though it seems like it would help with other things). It might be an orthogonal change, but deserves some consideration. Consider switching to go-based mouse driver with relative movements first.
- Multi-monitor support was introduced in Tracky Mouse 2.8.0
- The above diagram was drawn in JS Paint using Tracky Mouse!
In a multi-monitor setup, i.e. with multiple displays connected, if the screens are different sizes, or they're configured strangely, the overall virtual screen space can be non-rectangular.
Currently, the mouse moves across screens seamlessly where they connect, but if it moves into the dead space, it triggers Manual Takeback mode, because the mouse stops following the position it tries to set it to, so it assumes the user moved a physical mouse.
Instead it should take non-rectangular bounds into account and collide with the borders. If it hits a dead zone horizontally, it should continue to move vertically, and visa versa, as well as being able to move back away from the dead zone of course.
Assorted notes: