Yeah I mentioned that in comment #3 but I don't think disallowing non-contiguous configs is the solution. That's an OK thing to do, but not a robust solution.
A robust solution would be to just let the cursor move freely within the bounding rectangle, and not care if any part of that is not covered by a monitor.
Doing that would solve this bug, and also solve the confusion that can arise from odd non-rectangular configs where you have to move the cursor through a narrow passage (smaller monitor) before it can find its way to the larger monitor. So keeping the cursor always on a screen can actually be more frustrating and awkward than allowing the edge cases where it might be invisible.
Yeah I mentioned that in comment #3 but I don't think disallowing non-contiguous configs is the solution. That's an OK thing to do, but not a robust solution.
A robust solution would be to just let the cursor move freely within the bounding rectangle, and not care if any part of that is not covered by a monitor.
Doing that would solve this bug, and also solve the confusion that can arise from odd non-rectangular configs where you have to move the cursor through a narrow passage (smaller monitor) before it can find its way to the larger monitor. So keeping the cursor always on a screen can actually be more frustrating and awkward than allowing the edge cases where it might be invisible.