Date: Fri, 19 Jun 1998 09:48:33 +0900 From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp> To: Randall Hopper <rhh@ct.picker.com> Cc: Danny Dulai <nirva@ishiboo.com>, multimedia@FreeBSD.ORG, hackers@FreeBSD.ORG, Amancio Hasty <hasty@rah.star-gate.com>, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: X-10 Mouse Remote patch Message-ID: <199806190048.JAA11026@zodiac.mech.utsunomiya-u.ac.jp> In-Reply-To: Your message of "Thu, 18 Jun 1998 17:04:24 -0400." <19980618170424.B8162@ct.picker.com> References: <19980601194116.A25497@ct.picker.com> <199806180122.KAA04952@zodiac.mech.utsunomiya-u.ac.jp> <19980618015038.40458@bleep.ishiboo.com> <19980618062844.E3160@ct.picker.com> <19980618124731.02987@bleep.ishiboo.com> <19980618130510.A7551@ct.picker.com> <19980618161154.03428@bleep.ishiboo.com> <19980618170424.B8162@ct.picker.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>As I mentioned, the end effect of the RF noise surfaces only as regular
>mouse button and motion events (AFAIK). And mouse button and motion events
>aren't passed through the MouseRemote socket (they're passed through
>/dev/sysmouse tty); only the Mouse Remote-specific key events are passed
>through the MouseRemote socket.
>
>So if you connect your Mouse Remote up like this:
>
> Std Mouse -> COM1 -> X Windows/syscons
>
> Mouse Remote -> COM2 -> moused -> /var/run/MouseRemote
>
>You can care less about the spurious mouse button/motion events because
>they're not even being used (nobody's slurping sysmouse), but rather
>they're just being tossed into the bit bucket. All you care about and are
>getting from COM2: is the remote-specific key events via the MouseRemote
>socket.
The above description is not exactly correct. If you ever want to use
mouse in syscons, you must run moused and let X access the mouse
through /dev/sysmouse. If you don't need the mouse pointer in
syscons, you can let X directly access the mouse.
You have either
Std Mouse -> COM1 -> moused -> /dev/sysmouse -> X/syscons
or
Std Mouse -> COM1 -> X
If you run moused on COM2, mouse events it detects will also go to
/dev/sysmouse.
/-> /dev/sysmouse -> X/syscons
Mouse Remote -> COM2 -> moused -
\-> /var/run/MouseRemote
Then, if you run two copies of moused, you get
Std Mouse -> COM1 -> moused -
\
-> /dev/sysmouse -> X/syscons
/
Mouse Remote -> COM2 -> moused -
\-> /var/run/MouseRemote
If you move the standard mouse and mouse part of Mouse Remote, you
will see "combined" motion of the mouse pointer on screen. However,
mouse events from the standard mouse and the Mouse Remote are NOT
messed up, because events from two devices are interpreted
independently by the two copies of moused.
Apart from possible RF interference, there is a case you may think
your mouse pointer is jumpy. You may perceive the above "combined"
motion as "jumpy", because you think the mouse pointer has moved when
you don't touch the mouse, but, in fact, you may have touched or moved
the other device accidentally.
Kazu
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199806190048.JAA11026>