> From: "Karsten M. Self" <http://www.ix.netcom.com/~kmself> > Date: Fri Apr 10, 5:39pm > > robert wrote: > > > > Hi. I was wondering if you ever found a solution to this. I've wanted > > something like this for years, but never got it working properly. > > > > Thanks. > > No, but I haven't been trying very hard lately (mostly just using the > system). Are you using FVWM or FVWM2? Vanilla FVWM. > I downloaded the latter and > launched the stock config a couple of times, though I haven't tweaked > it. I think fvwm2 is more configurable in some ways. Hmm. I am reluctant to convert my .fvwmrc to a new one unless I can be guaranteed that it will have the behavior you describe and _not_ Microsoft's interface behavior... > Good luck. Thanks. > > > From: "Karsten M. Self" <http://www.ix.NOSPAMHERE.netcom.com/~kmself> > > > Date: 1997/09/23 > > > > > > Some additional info. I'm *not* looking for ClickToFocus policy -- I > > > want pointer or lazy focus. What I'd like, though, is to know whether > > > it is possible to simultaneously pass WM display hints (raise/lower) and > > > interact with the client, at the same time, with a single command. > > > > > > Karsten M. Self wrote: > > > > > > > > I'm tweaking my system.fvwmrc, would like to enable user to click > > > > anywhere in application window to raise app. Which is easy to do > > > > > > > > # mouse1 W N Raise > > > > > > > > What doesn't work is that I'm then unable to select and copy from > > > > xterm and family, or press menu selections, etc. All click actions > > > > are intercepted by the "raise" function. Is there a way around this? > > > > I thought that this was possible under Motif (mwm/vuewm on HPUX), > > > > though I may be disremembering things. > > > > > > > > Thanks. --- robert | Software, Inc. email:http://dummy.us.eu.org/robert | 800 West Cummings Park, Ste 4950 http://www./~robertb | -6504 voice: x100 | fax: 781-932-2558