David,
I packaged x2x for the Debian GNU/Linux distribution some time ago, and
have now received a few bug reports, which I'm now forwarding to you.
I'm afraid I don't presently have the time or the X programming
knowledge to try to fix them myself, but I thought you would probably
be interested to have the reports anyway.
Since these are in Debian's bug tracking system, they are also available
on the Web, at <URL:http://www.debian.com/Bugs/db/pa/lx2x.html>. I'm
CC'ing this to {15851,15870,15899,20694}-forwarded@bugs.debian.org so
that the bug tracking system can keep a record of what's happening, and
to Joey Hess, who reported the bugs. If you reply, please could you
leave at least one of the @bugs addresses in your CC line so that your
message is filed in the bug system too. Thanks.
First, there were a couple of wishlist items:
"It's possiblt to have monitors stacked on top of each other (I know
people who do..), so -north and -south options would be nice."
"It'd be useful if the -wait parameter was given, if it loses
connection to the remote display, for it to retry connecting to the
remote display."
There was a bug about the caps lock key:
"Run x2x -to foo
If the keyboard on machine "foo" has caps lock on, everything you
type over there, using x2x, is in upper case. This is highly
confusing, because caps lock in _not_ on on the keyboard you are
typing on. I assume the same holeds for num lock as well."
And another bug, which I haven't been able to understand very well.
It was reported like this:
"I run x2x like this: x2x -to box:0.0 -west
Once I move the cursor over to the left onto the other display, I
can get it stuck. I put the mose in the far left side of that
display. Then I move the mouse to the right as fast as possible.
Sometimes the cursor moves partway, but then becomes stuck there,
and does not get back over to my native display, and cannot be
moved. To unstick, I just move the mouse back some to the left.
It seems to be releated to moving the mouse too fast."
"It's as if, once I warp over to that screen and try to move back,
x2x is seeing that hey, I moved my mouse to the right 100 pixels,
all at once. So it sends that event over to the other screen. But,
my mouse cursor is less than 100 pixels from the right hand edge of
the screen, so x2x has told the X server to warp the mose off the
side of the screen. I assume that then the X server disregards what
x2x told it to do, they get out of sync, and my mouse pointer
appears to freeze for a while. This might all be wrong, it's just my
guess.
> Other things: are both your displays the same size (in pixels)?
> Are they both Debian boxes?
Yes.
> Which servers do they run, and what sort of mouse are you using?
The from display (ie, the one that DISPLAY is set to when I run x2x;
the one the mouse is phsically connected to), is running s3 server.
The other is running the svga server.
My mouse is a standard mousesystems 3 button serial mouse."
I hope this will be of some use to you. Please ask if you want more
information.
Cheers,