From: "Jim C. Brown" <jbrown106@phreaker.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] rfb patch and mouse movement
Date: Mon, 17 Jan 2005 10:18:25 -0500 [thread overview]
Message-ID: <20050117151825.GA5861@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0501171524420.2732@wgmdd8.biozentrum.uni-wuerzburg.de>
On Mon, Jan 17, 2005 at 03:49:23PM +0100, Johannes Schindelin wrote:
> Hi,
>
> On Sun, 16 Jan 2005, Jim C. Brown wrote:
>
> > On Sun, Jan 16, 2005 at 01:41:09PM +0400, Brad Campbell wrote:
> > > G'day all,
> > >
> > > I'm having a few issues at the moment with mouse
> > > calibration under Windows XP.
> >
> > Every OS with mouse support, with the sole exception of ReactOS, has calibration
> > problems. (At least, those OSes I've managed to test.) Why the mouse is
> > perfectly calibrated in ReactOS, I have no idea.
>
> I have: ReactOS does not do mouse acceleration, thus one tick from the
> mouse always corresponds to one pixel movement on the screen, whereas X11
> on Linux normally accelerates the mouse, i.e. one thick means one pixel
> movement, but 10 ticks mean 20 pixels.
>
Then, in theory, if we could tell the guest X11 server to not do acceleration,
the problem would go away?
If so, that would also work for a Windows guest, tho the method of execution
would probably be difficult.
> > Does pressing Ctrl-Alt (or Ctrl-Shift??) to ungrab the mouse, then realiging
> > the host and guest pointers, and then regrabing the mouse work? This is what I
> > do w/ my no-sdl patch.
>
> This doesn't work yet with rfb9, because Ctrl-Alt doesn't alter the state,
> i.e. the mouse updates are still forwarded after pressing Ctrl-Alt, and
> even after a switch to the console or serial.
Is this due to a limitation of VNC (in which case we might say, Ctrl-A Ctrl-A
does the switch), or is it merely due to a lack of support in the code (that
someone else could add easily by adding a few lines of code)?
>
> I want to rework the auto-calibration, but time's sparse. Also, somebody
> on the list mentioned that he was working on this himself, but he didn't
> answer my emails.
>
> Ciao,
> Dscho
>
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>
--
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.
next prev parent reply other threads:[~2005-01-17 15:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-16 9:41 [Qemu-devel] rfb patch and mouse movement Brad Campbell
2005-01-16 14:35 ` Jim C. Brown
2005-01-17 4:23 ` Brad Campbell
2005-01-17 15:22 ` Jim C. Brown
2005-01-17 14:49 ` Johannes Schindelin
2005-01-17 15:18 ` Jim C. Brown [this message]
2005-01-17 18:02 ` Johannes Schindelin
2005-01-17 18:15 ` [Qemu-devel] " Ronald
2005-01-17 19:04 ` Johannes Schindelin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050117151825.GA5861@jbrown.mylinuxbox.org \
--to=jbrown106@phreaker.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).