Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!zephyr.ens.tek.com!tektronix!percy!m2xenix!servio!marcs From: marcs@slc.com (Marc San Soucie) Newsgroups: comp.windows.x.motif Subject: Re: Motif window raising question Message-ID: <1991Jun19.164027.20216@slc.com> Date: 19 Jun 91 16:40:27 GMT References: <56516@nigel.ee.udel.edu> Organization: Servio Corporation Lines: 26 Roger Meunier (roger@zuken.co.jp) writes: > Try adding the following to your resource defaults file (e.g., ~/.Xdefaults): > > Mwm*keyboardFocusPolicy: pointer > > BTW, does anyone have a clue as to why this is not the de facto default? > Who out there enjoys having to *explicitly* tell the window manager which > window they want to work with? Well, I don't exactly enjoy it, but it's a lot less annoying than having to locate my bleeding pointer, shove it into a window and then leave the bloody thing there on top of my good stuff just so I can type into the window. I may be in the minority, but I cannot fathom how you pointer-driven types can live with that behaviour. Marc San Soucie Portland, Oregon marcs@slc.com P.S. One good reason to have click-to-type as the default is that it is a heck of a lot easier to explain to someone who has -no- prior window-system experience. When a new window pops up but because of geographical happenstance the pointer is not in the window, how does one explain the fact that one cannot type into the new window?