Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!rpi!crdgw1!barnett From: barnett@crdgw1.crd.ge.com (Bruce G. Barnett) Newsgroups: comp.windows.open-look Subject: Re: dbxtool under Openwindows 2.0 Message-ID: <13718@crdgw1.crd.ge.com> Date: 13 Nov 90 17:26:51 GMT References: <192@tivoli.UUCP> Reply-To: barnett@crdgw1.steinmetz.ge.com (Bruce G. Barnett) Distribution: comp.windows.open-look Organization: GE Corp. R & D, Schenectady, NY Lines: 39 In article <192@tivoli.UUCP> robbie@tivoli.UUCP () writes: |In article I write: |>I miss this feature also. :-) |I missed it too, try this in your .Xdefaults file. It should fix everybody up. | |OpenWindows.SetInput: followmouse No. I assumed the original poster knew about the followmouse property. I am talking about the SunView feature that lets you have multiple insertion carets, one for each textedit area. In the SunView mailtool, there are two carets: One for the folder/filename, and one in the text subwindow. When you move the mouse into the appropriate area, the gray diamond becomes a black triangle. In the SunView dbxtool, there are two text subwindows with two insertion points. If you move the mouse into the subwindow, that window shows the current insertion point. OpenLook does not have this feature. Even with followmouse. You must Click in each subwindow to specify *which* subwindow gets the focus. If I have followsmouse on, and click in the source window of dbxtool, I lose the keyboard focus in the command window. I cannot move the mouse into the command window and type a command. I must click in the appropriate subwindow to specify which window is getting the focus. Net Result: I must click to type when using dbxtool even though I have follows mouse enabled. If I try to type a command and the focus is in the wrong window, I get an alert saying I am trying to modify a read only window. I reported this to Sun a while ago, and the person said this is in the specification of OpenLook. Perhaps we can convince them it is a bug, because normally the source window does not get a text insertion caret.