From: Matthew Mastracci <matt@aclaro.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: Host <-> guest interface port?
Date: Wed, 05 May 2004 09:17:17 -0600 [thread overview]
Message-ID: <4099057D.5010907@aclaro.com> (raw)
In-Reply-To: <20040505025800.GA9884@jbrown.mylinuxbox.org>
[-- Attachment #1: Type: text/plain, Size: 855 bytes --]
Jim C. Brown wrote:
>I volunteer to write the code for the Linux client if necessary. I'm studying
>the X11 clipboard mechanism anyways. I have a pretty good idea of how to get
>the clock of the host, also.
>
>Not sure how auto-capture/release of mouse would work tho.
>
>
Since the host knows exactly where the guest cursor is (the guest is
sending cursor location updates), it can release the mouse when the
guest cursor is against the edge of the screen. This works in reverse
as well - when the mouse is moved over the QEMU screen, the host
captures it (hiding the local cursor) and updates the guest location to
match. It's a seamless transition from real mouse to virtual mouse.
The guest can also hide and show the guest OS cursor as it is
captured/released. You'll only see the cursor in the guest if it is
captured by QEMU.
Matt.
[-- Attachment #2: matt.vcf --]
[-- Type: text/x-vcard, Size: 286 bytes --]
begin:vcard
fn:Matthew Mastracci
n:Mastracci;Matthew
org:aclaro Softworks, inc.
adr:;;1900 a - 11 St. SE;Calgary;Alberta;T2H 3G2;Canada
email;internet:matt@aclaro.com
title:Software Developer
tel;work:(403) 299-6612
x-mozilla-html:FALSE
url:http://www.aclaro.com
version:2.1
end:vcard
next prev parent reply other threads:[~2004-05-05 15:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-04 16:16 [Qemu-devel] Host <-> guest interface port? Matthew Mastracci
2004-05-04 22:12 ` Fabrice Bellard
2004-05-04 22:46 ` Michael L Torrie
2004-05-04 23:32 ` [Qemu-devel] " Matthew Mastracci
2004-05-05 18:31 ` Fabrice Bellard
2004-05-05 2:58 ` [Qemu-devel] " Jim C. Brown
2004-05-05 15:17 ` Matthew Mastracci [this message]
2004-05-06 21:48 ` [Qemu-devel] " Jim C. Brown
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=4099057D.5010907@aclaro.com \
--to=matt@aclaro.com \
--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).