From owner-freebsd-hackers Thu Jun 18 23:03:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA02295 for freebsd-hackers-outgoing; Thu, 18 Jun 1998 23:03:24 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bleep.ishiboo.com (user7830@bleep.ishiboo.com [199.79.133.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA02274 for ; Thu, 18 Jun 1998 23:03:20 -0700 (PDT) (envelope-from nirva@ishiboo.com) Received: (qmail 2616 invoked by uid 1000); 19 Jun 1998 06:03:20 -0000 Message-ID: <19980619020320.00367@bleep.ishiboo.com> Date: Fri, 19 Jun 1998 02:03:20 -0400 From: Danny Dulai To: Amancio Hasty Jr Cc: yokota@zodiac.mech.utsunomiya-u.ac.jp, hackers@FreeBSD.ORG, hasty@rah.star-gate.com, multimedia@FreeBSD.ORG, rhh@ct.picker.com Subject: Re: X-10 Mouse Remote patch References: <199806190543.WAA20703@netcom18.netcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <199806190543.WAA20703@netcom18.netcom.com>; from Amancio Hasty Jr on Thu, Jun 18, 1998 at 10:43:24PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting Amancio Hasty Jr (hasty@netcom.com): > I don't follow your logic given that the X10 remote mouse is also a mouse > what is unique about other than the IR and extra key functions is that > it can co-exist in the same port with another mouse. > > You can use the X10 remote mouse just as your sole mouse for your system. You can, only because it is a superset of a mouse. moused imo should do mouse stuff, and not non mouse stuff. Thats why remoted should split the functionality of this multipurpose remote into mouse portions and non mouse portions (possibly even copying the mouse data over to the remote side too). The mouse portion seems to be microsoft compatible. If you just forward the mouse data to the remotemouse device and the non mouse related stuff to the x10remote device (after post processing), you are taking that subset of functionality and making it possible for programs that are not made to use or expect the extra features. With the current model, what happens if some new remote is available and it lacks the mouse? You'd either need a new device or a moused that post processes its protocol and sends the data to /var/run/MouseRemote, and does NO mouse stuff at all to /dev/sysmouse. moused that does no mouse stuff.. heh. This way, remoted would deal with this and future remotes instead of cluttering moused. -- ___________________________________________________________________________ Danny Dulai Feet. Pumice. Lotion. http://www.ishiboo.com/~nirva/ nirva@ishiboo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message