Date: Thu, 10 Apr 1997 11:36:10 +0900 From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp> To: "Louis A. Mamakos" <louie@transsys.com> Cc: freebsd-current@freefall.freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: moused enhancement (was: Re: make world) Message-ID: <199704100236.LAA07337@zodiac.mech.utsunomiya-u.ac.jp> In-Reply-To: Your message of "Wed, 09 Apr 1997 12:59:33 -0400." <199704091659.MAA19396@whizzo.transsys.com> References: <Pine.OSF.3.95q.970407165836.15555A-100000@protocol.eng.umd.edu> <19970409032758.35315@usn.blaze.net.au> <199704091659.MAA19396@whizzo.transsys.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>I've had very mixed results getting stuff merged into the tree - the >Brooktree 848 changes I've done got merged because someone with commit >privs was also actively involved in the process. The socket-timestamp >kernel code got in. But after two attempts to get simple changes to >/usr/sbin/moused in (which would keep my mouse working when doing >'make world', sigh) and a one-liner to Although I am not responsible for `moused', I have been aware of your GlidePoint patch. (I may be guilty, but only *partially* :-) I looked at your patch (PR bin/3028) and understand that it adds ALPS GlidePoint support. XFree86 also has GlidePoint support (since 3.1.2F?). As far as I can understand, your support code and XFree86's are not functionally equivalent. Yours is for GlidePoint on the PS/2 mouse port and XFree86's code is for GlidePoint attached to a serial port. Your code makes `moused' pretend the left mouse button is pressed when the user `taps' GlidePoint's surface, whereas XFree86 regards the `tap' action as the fourth button press. Ok, we can argue that it isn't necessary that `moused' and XFree86 behave in exactly the same way. But, isn't this difference rather confusing to the user? In order for a user to use GlidePoint with X, he has to choose: 1) attach GlidePoint to the PS/2 mouse port and specify `glidepoint' to `moused'. Tell X, in XF86Config, to access `/dev/sysmouse' and the protocol is `mousesystems'. 2) attach GlidePoint to a serial port, don't use `moused'. specify `glidepoint' in XF86Config. If GlidePoint is attached to a serial port and the user intends to use `moused', he shouldn't specify `glidepoint' as the protocol, rather he has to choose `microsoft' or `mouseman'. `Tap' feature won't be recognized in this case. If GlidePoint is attached to the PS/2 mouse port and the user don't use `moused', he shouldn't specify `glidepoint' as the protocol in XF86Config, rather he has to say `ps/2'. `Tap' feature won't be recognized in this case. IMHO, more complete support for GlidePoint is necessary for both `moused' and XFree86. One solution on `moused's side may be to incorporate serial GlidePoint support code from XFree86 into `moused'. What do you think? One other thing. ALPS produces several models of GlidePoint devices. I know that some models (such as Desktop GlidePoint model GP101) need specific support code, but the others (such as GlidePoint model GP001) don't; they internally generate a left button press event when the user taps the surface of the device. Kazu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199704100236.LAA07337>