Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!crdgw1!barnett From: barnett@grymoire.crd.ge.com (Bruce Barnett) Newsgroups: comp.windows.open-look Subject: Re: dbxtool weirdness Message-ID: Date: 25 Apr 91 21:42:39 GMT References: <1991Apr24.183505.18899@gtc.com> <1991Apr25.143849.20688@nynexst.com> Sender: news@crdgw1.crd.ge.com Reply-To: barnett@crdgw1.ge.com Organization: GE Corp. R & D, Schenectady, NY Lines: 21 In-reply-to: schwartz@nynexst.com's message of 25 Apr 91 14:38:49 GMT In article <1991Apr25.143849.20688@nynexst.com> schwartz@nynexst.com (S. H. Schwartz) writes: > My dbxtool uses click-to-type. Note that the default window is the > source code window, so you have to click on the command window to > change where input goes. Having done that, input focus stays there and > follows the mouse. What he is talking about is even if you set your defaults to be focus follows mouse, when you try to set a breakpoint, or select a variable in the source window - THE INPUT FOCUS GOES THERE. This window in normally read only. You can't change anything in the window unless you enable the edit mode. So if it's read only, WHY does it put the input focus into the window than can't take any input????? When you want to execute a command in the command window, you have to click in the command window first. This is very frustrating to people who have used focus-follows-mouse for years. Everytime you do something in the read-only source window, you have to click back in the command window. Grr! -- Bruce G. Barnett barnett@crdgw1.ge.com uunet!crdgw1!barnett