Constraining cursor to RandR crtcs

[Alexej Davidov]

On Mon, 02 Apr 2007 10:58:22 -0700
Keith Packard <keithp at keithp.com> wrote:

> Let's figure out what the default policy needs to be; we can hard code
> that for now and then look at making it more configurable later.

All of the solutions are somewhat problematic and I guess there's no
silver bullet. You really need some configurable WM to set it up to
best fit whatever special screen alignment is used.

But as for a default: allow the pointer to move through dead zones.
While it can be annoying to lose the pointer, I think this is the most
intuitive solution. About warping: it can be fun to take bets where the
pointer will be, when you move across screen boundaries but probably
not very productive. And about confining the pointer to visible space:
the real screens are not necessarily at the same positions as the
virtual screens. Think about a beamer attached to a laptop. How would
you find out, where you can move the pointer across borders?

Pointer position indicators at screen edges when the pointer is in a
dead zone, as suggested in another post, would be useful, though.

Regards,
A.