Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel!munnari.oz.au!uunet!elroy.jpl.nasa.gov!decwrl!csus.edu!netcom.com!hasty From: hasty@netcom.com (Amancio Hasty Jr) Subject: Re: Motif on X386??? Message-ID: <090m_#b.hasty@netcom.com> Date: Wed, 19 Aug 92 00:25:25 GMT Organization: Netcom - Online Communication Services (408 241-9760 guest) References: <1992Aug17.140857.3882@lgc.com> <1992Aug18.015024.8369@fcom.cc.utah.edu> <1992Aug18.174802.9845@BitBlocks.com> Lines: 33 In article <1992Aug18.174802.9845@BitBlocks.com> bvs@BitBlocks.com (Bakul Shah) writes: >terry@cs.weber.edu (A Wizard of Earth C) writes: > >>I also saw problems with menus not coming active unless you let go of the >>button popping up the menu, then quickly pressed it again (not in the menu >>area) to get the menu selection bar to follow the mouse. > >Make sure you are using the latest com.c driver (with select() >bug fixed). But even then there is some problem with the mouse >code in X386 as the very first button press is not seen until >after you either release the button or move the mouse a bit. > >If you wish to track this problem down, check out file >$X11R5/mit/server/ddx/x386/x386Io.c. Routine x386MseEvents() >seems to be the culprit. > Rich (rich@rice.edu) already fix this problem in the next upcoming release of X386 1.2E 1.0.2 for 386bsd 0.1, please ask him for the fix. The problem in a nutshell is that X386Io.c is not setting the cflag. the fix was also previously posted by me. Additionally, there are problems with the X server not grabbing the keyboard, this problem has been also resolved. So just ask Rich when he is going to release X again. Hopefully, it will be soon. I just hate to see the same problems being reported over and over again even though there has been previous postings relating to the problem with suggested fixes. >-- Bakul Shah <bvs@bitblocks.com> Amancio Hasty