Bug #2111 - jumpy mouse on win32 multimon client
SourceForge user: nobody
1.1.7 on win2k
In a dual screen client setup A=1024768 and B=12801024,
when you change the mouse speed in the windows setup
control panel. The mouse mouvement is correct in screen
A, but the mouse jump randomly in screen B. This append
in both normal and relative mouse move mode.
sound related to SPI_GETMOUSE ?
-Cedric
#1
SourceForge user: crs23
Logged In: YES
user_id=21565
i'll assume A is the primary monitor. i'm not sure what
would cause that. SPIGETMOUSE seems like a good guess but
synergy gets/sets that stuff with every mouse move. that
is, it doesn't cache that state so it wouldn't be confused
just because you changed the state. it sounds more like
mouseevent(MOUSEEVENTF_MOVE,...) is behaving badly.
i'm setting the priority to 3 (low) because synergy doesn't
respect the client's mouse acceleration settings anyway so
the solution is to not change the settings.
#2
SourceForge user: nobody
Logged In: NO
I'm having a similar problem under XP - two clients, both
running XP SP1, everything worked perfectly to begin with.
I haven't touched the mouse settings on either PC. On PC A
(the server), the mouse moves fine; on PC B (the client),
it's really jumpy, although the local mouse moves as it should.
It's not a network bandwidth issue, as there's loads of
spare capacity.
-Alison
#3
SourceForge user: nobody
Logged In: NO
I experience a similar behavior on Windows XP Pro, SP2 as a
server, and XP SP1 on a client. The mouse is normal on my
server machine, but the "remote" mouse AND keyboard are
laggy on the client machine (as if it's only being sampled a
few times per second. The local mice/keyboards are fine.
Specs:
Server, P4-1.6Ghz, 256 Megs, 100mbit ethernet, XP PRO SP2
Client, P3,1.13Ghz, 512 Megs, 100mbit ethernet, XP PRO
Tablet PC Edition SP1
~ Mike
hollinger@gmail.com
#4
SourceForge user: crs23
Logged In: YES
user_id=21565
laggy mouse motion is not the same as the original bug.
a laggy mouse is usually due to running through SSH or a
firewall. you might be able to disable the Nagle algorithm
(turn TCP_NODELAY on) on the firewall and i know SSH can do
this.
Write comment