From owner-freebsd-multimedia Sun Jun 21 17:29:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA03959 for freebsd-multimedia-outgoing; Sun, 21 Jun 1998 17:29:28 -0700 (PDT) (envelope-from owner-freebsd-multimedia@FreeBSD.ORG) Received: from bleep.ishiboo.com (user5583@bleep.ishiboo.com [199.79.133.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA03946 for ; Sun, 21 Jun 1998 17:29:21 -0700 (PDT) (envelope-from nirva@ishiboo.com) Received: (qmail 15884 invoked by uid 1000); 22 Jun 1998 00:29:21 -0000 Message-ID: <19980621202921.57824@bleep.ishiboo.com> Date: Sun, 21 Jun 1998 20:29:21 -0400 From: Danny Dulai To: Mike Smith Cc: Randall Hopper , hasty@rah.star-gate.com, multimedia@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: X-10 Mouse Remote patch References: <199806181306.PAA22009@sos.freebsd.dk> <199806211851.LAA03183@antipodes.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <199806211851.LAA03183@antipodes.cdrom.com>; from Mike Smith on Sun, Jun 21, 1998 at 11:51:06AM -0700 Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Quoting Mike Smith (mike@smith.net.au): > > And it has NO business in moused whatsoever, its a hack and it doesn't > > belong there. I'm sorry I havn't noticed this before, but its should be > > ripped out ASAP, I would never have allowed it in there if I had > > found out before. > > Actually, no. The MouseRemote is a mouse, amongst other things, and > it's specifically intended to be connected inline with mice. As such, > our protocol handler for mouse data streams is the correct place to put > it. Ripping it out without simultaneously coming up with an equally > functional and architecturally 'better' solution is not going to endear > you to anyone. > > I did actually propose to Randall the implementation of a stackable > 'interception' layer, again to be managed by moused, however with only > one device (so far) in this particular circumstance, it didn't seem > worth the effort. Right now, there is no way I can get the remote output that moused gives to /var/run/MouseRemote, and still run other mice on moused, AND having the remote's mouse functions disabled. The mouse remote's rf receiver gets far too much interference and causes my mouse pointer to jump around and buttons to be pressed randomly. The remote is uesless without turning off the mouse support. To solve this problem either add an option to moused to turn off mouse messages (and rename moused to something better), or use the model I suggested using remoted that splits mouse and remote events. Randall has expierenced the problems I'm getting, and I assume most others that have this remote do too. This is not a feature that '[isnt] worth the effort', its a mandatory feature for functionality. -- ___________________________________________________________________________ Danny Dulai Feet. Pumice. Lotion. http://www.ishiboo.com/~nirva/ nirva@ishiboo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message