Open GoogleCodeExporter opened 8 years ago
I'm encountering the same issue. Ubuntu 10.10 Desktop edition, Gmote 2.0.
GNOME. Exactly the same steps, exactly the same issue.
Original comment by tonypraw...@gmail.com
on 26 Jan 2011 at 2:38
Same, any changes?
Original comment by pavel.al...@gmail.com
on 22 Feb 2011 at 12:10
Same issue. Linux 2.6.35-28-generic #49-Ubuntu x86_64 GNU/Linux. GNOME. Dual
screen setup using TwinView. Mouse is stuck on the right-most side and only
moves vertically. Everything else seems to work fine.
Note also that I had the exact same issue with RemoteDroid, so the cause could
be deeper down.
Original comment by barleva...@gmail.com
on 10 Mar 2011 at 6:51
Same, stuck on the right side of the screen, moves vertically, not
horizontally. Ubuntu 11.04, Gnome 2.32.1.
Original comment by tcba...@gmail.com
on 29 May 2011 at 10:08
I have got the same problem the cursor only moves up and down the right side of
my screen.
Original comment by randysie...@gmail.com
on 29 Sep 2011 at 2:09
anyone found a fix to this yet?
Weird this is it was working for me. Have been playing a lot with nvidia
drivers (installing CUDA). May be related.
Also on TwinVeiw duel monitor setup. Also stuck to right most pixel column on
screen. Alo moves up and down, but not left-right. Most other features work,
although browsing to a file fails.
Original comment by phil.a.t...@gmail.com
on 11 Oct 2011 at 8:20
You guys are all using multiple monitors aren't you? I find the bug only
happens then. Use only 1 monitor, and the mouse works perfectly.
The bug appears to be in Java itself, function Robot.mouseMove() - even though
it is passed valid coordinates, the mouse jumps to the rightmost edge of the
combined screen.
A possible workaround could be using one Robot for each screen with each Robot
being created by the constructor that takes a GraphicsDevice, and then calling
the mouseMove() method only on the Robot for the appropriate screen.
Another good question is: does this happen on Windows? MacOS?
Original comment by damjan....@gmail.com
on 29 Nov 2011 at 7:09
The Robot() constructor says:
"Constructs a Robot object in the coordinate system of the primary screen."
But the primary screen is NOT necessarily the screen whose top-left corner has
coordinates (0,0).
This means that coordinates passed to robot.mouseMove() are NOT in the same
coordinate space as coordinates obtained from MouseInfo.getPointerInfo().
A translation is thus necessary from the mouse's absolute coordinates, to
coordinates relative to the primary screen.
The attached patch does that, and fixes the problem.
Otherwise, thank you for this awesome app, I love it, and hope it works better
for everyone with my patch :).
Original comment by damjan....@gmail.com
on 29 Nov 2011 at 8:47
Attachments:
[deleted comment]
great damjan that patch works wonders.
Just for the record, RandR 1.3 added an option to set the primary output. just
use
xrandr --output $DEVICE --primary
Gnome and KDE should have same gui to set primary monitor as well.
Original comment by hanwen.o...@gmail.com
on 9 Oct 2012 at 8:06
Can this please be fixed already?
Original comment by mtele...@gmail.com
on 20 Nov 2012 at 2:30
When will this patch land in the current release?
Original comment by e.rhys.t...@gmail.com
on 13 Jan 2013 at 10:06
how do i patch it. I am on Ubuntu 12.04 Java 7 and GmoteServer Linux 2.0.0
Original comment by H.E.Dur...@gmail.com
on 6 Mar 2013 at 12:11
I've applied the patch from post #8. The gmoteserver jar file and source are
available here https://github.com/ins0mniac13/gmote
Original comment by JustinKe...@gmail.com
on 2 Dec 2013 at 3:41
Original issue reported on code.google.com by
zole...@gmail.com
on 30 Sep 2010 at 10:12