All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jim C. Brown" <jbrown106@phreaker.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] VNC patch, the 3rd version
Date: Sun, 30 May 2004 22:00:07 -0400	[thread overview]
Message-ID: <20040531020007.GA29335@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0405291818370.856@wgmdd8.biozentrum.uni-wuerzburg.de>

On Sat, May 29, 2004 at 08:18:10PM +0200, Johannes Schindelin wrote:
> Hi,
> 
<s>
> There is a problem with the synaptic patch: If I read it correctly, the
> absolute flag cannot be set to 1. There is simply no line which can do
> that.
> 

Correct. To do that on a real touchpad you have to set bit 7 of the mode bit
to 1. My patch doesn't support setting the mode bit.

> Jim, if you read this, can you help a mediocre programmer and enlighten me
> how to use your work?
> 

For now what you need to do is:

The simple yet ugly hack would be to, on line 732 of pckbd.c, check if bit
7 of val is set. If so, set absolute mode on.

if (val & 0x80) s->touchpad.absolute = 1; /* TODO: real support for changing the mode byte */

I'm trying to figure out how to implement this elegantly and support all
possible modes. As you can tell by my silence, I haven't figured this out yet.

> Another idea which hit me: I am not convinced that without guest drivers,
> the synaptic patch helps VNC's mouse.

It doesn't. Without guest drivers, the real touchpad emulates a normal mouse.
Unless absolute mode is turned on, the patch doesn't add much.

With absolute mode, it still doesn't add much due to missing functionality
such as guestures. How would I emulate guestures with a 2-button mouse
is the question here. (Emulating a third button or scrolling with a real mouse
that has a real scrollwheel is not that hard, but with a mere 2 button mouse
the problem becomes much harder.)

> So why not use the
> graphical feedback when using the mouse to determine where the guest
> cursor is now (and how far it lags behind/runs in front)? I know, it is
> less than clean, but it would be fun! I think I will try it if nobody
> yells at me.

Good luck. This will not be easy at all (for example, what if the guest OS is
showing a screenshot, which happens to include the image of the mouse pointer
-- and remember that each GUI has a different looking mouse pointer, and most
have several, which can be swapped in at random from the viewpoint of qemu) but 
if you can pull it off it could be a useful feature.

> 
> 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.

      reply	other threads:[~2004-05-31  2:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-28  1:19 [Qemu-devel] Overoptimization Alexander E. Patrakov
2004-05-28 10:13 ` Herbert Poetzl
2004-05-28 10:58   ` Alexander E. Patrakov
2004-05-28 11:08     ` Herbert Poetzl
2004-05-28 13:50       ` [SOLVED] " Alexander E. Patrakov
2004-05-28 22:15         ` Lionel Ulmer
2004-05-29 18:18         ` [Qemu-devel] VNC patch, the 3rd version Johannes Schindelin
2004-05-31  2:00           ` Jim C. Brown [this message]

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=20040531020007.GA29335@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.