Comment 39 for bug 389519

Revision history for this message
In , Peter-s-d (peter-s-d) wrote :

Just my two cents worth...

Bezel spanning seems like an interesting idea, but it is sufficiently different that it should be handled differently. Perhaps allow defining bezel area(s), defaulting to zero but configurable to the whole virtual desktop. Perhaps treat a bezel area as a "null monitor". Only allow the pointer to enter areas covered by at least one monitor or bezel. That way on a properly configured system there would never be any "real" discontinuities. I guess that that is an argument for letting the bezel area default to the virtual desktop. When it is mis-configured make the pointer jump to the next real monitor.

In most circumstances it would still be undesirable to have the pointer hidden by a bezel. When the pointer is hidden, mark ALL real screens with a half pointer at the point nearest the virtual pointer. (Or something that indicates, "it went over there".) That way you would have some hope of finding the dam thing. Have a configuration option to let it drift to the nearest real screen.

Only experts and fools deliberately configure discontinuous screens. Print a warning to the log and let the users decide which category they belong to.

Anyone editing an image that spans multiple discontinuous monitors is either really expert or really optimistic. For a start, they can't see what they are doing.