Date: Sun, 21 Jan 2001 22:04:25 -0500 From: "Donald J . Maddox" <dmaddox@sc.rr.com> To: "Paul M . Lambert" <plambert@plambert.net> Cc: "Donald J . Maddox" <dmaddox@sc.rr.com>, questions@FreeBSD.ORG Subject: Re: Xfree 4.0.2 - mouse fixed... not really... Message-ID: <20010121220425.A16638@cae88-102-101.sc.rr.com> In-Reply-To: <20010121184344.A18067@slappy.plambert.net>; from plambert@plambert.net on Sun, Jan 21, 2001 at 06:43:44PM -0800 References: <20010120145322.A90461@cae88-102-101.sc.rr.com> <200101202013.f0KKDgu34319@usr03.cybercity.dk> <20010120152136.B349@cae88-102-101.sc.rr.com> <200101202026.VAA79619@usr02.cybercity.dk> <20010120153429.A402@cae88-102-101.sc.rr.com> <200101202057.VAA92424@usr01.cybercity.dk> <20010120160610.A390@cae88-102-101.sc.rr.com> <200101202151.WAA84032@usr04.cybercity.dk> <20010120170446.A998@cae88-102-101.sc.rr.com> <20010121184344.A18067@slappy.plambert.net>
next in thread | previous in thread | raw e-mail | index | archive | help
It seems that you are saying simply that the 'protocol SysMouse' keyword is broken, but 'protocol MouseSystems' works just fine. If this is true, then it is certainly broken, since SysMouse should be *exactly* the same as MouseSystems. Nevertheless, that being said, my posting was a followup to some discusssion the original poster and I were carrying on in private mail until said poster suddenly decided to take it back to the list. In our other conversations, it became clear that the poster did not understand the difference between a mouse device, driver, or protocol. The email you replied to was about my fourth attempt to explain it. On Sun, Jan 21, 2001 at 06:43:44PM -0800, Paul M . Lambert wrote: > > Certainly. > > However, the original poster is, I think, seeing a behavior I myself > am also seeing: > > Under XFree86 3.3.6, I had moused running with -t ps/2 and using /dev/psm0. > This allowed console mouse access, and provided /dev/sysmouse. I had > XFree86 looking at /dev/sysmouse and using SysMouse as the protocol type. > This all worked very nicely. > > Under XFree86 4.0.2, if I have moused running with -t ps/2 and using > /dev/psm0, and tell XFree86 to use /dev/sysmouse and SysMouse, as I > did in 3.3.6, it _fails to work correctly_. If I click the first mouse > button, for example, the mouse-down event appears to register (i.e. if > I click a widget that shows the mouse-down and mouse-up separately, I > see the mouse-down). However, I don't see the mouse-up until such time as > I move the mouse. > > For example, with Netscape 4.76 running, I can move the pointer to the > back button in the Netscape window. Then, i can press and release the > first mouse button (normal 'click' action). The Back button depresses, > and remains there. I have let go of the mouse button, but the Netscape > button remains depressed until eventually the Back menu comes up. If I > move the mouse (i.e. the _pointer_) before the menu appears, then the > Back button in the netscape window releases from the depressed position > and acts as though I have pressed it normally. > > Needless to say, this is a real pain; it makes, for example, clicking > and dragging difficult, as it appears that any mouse movement is also > seen as releasing the mouse buttons. It's really frustrating. > > If I kill moused, and tell XFree86 to use /dev/psm0 directly, it works > just fine. If I leave moused running and tell XFree86 to use /dev/sysmouse > and the MouseSystems driver, it also works just fine. > > This is not correct behavior. I think this is the behavior that this > person had seen. > > --plambert > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010121220425.A16638>