On Thu, Apr 29, 2010 at 02:37:29PM -0400, Shriver, Daniel wrote: > We have 2 GUI's that run on a screen, one with a tiny window that sits on > top of another which takes up all the screen real estate. > > We want keyboard events to always go to the GUI (on bottom) that takes up > the screen. Mouse events should behave normally (if they are inside the > small window they go to that app, otherwise they go the app that sits on > bottom). > > Is this possible with FVWM or not?
No -- change your application to do it instead. That is, if this tiny window that's on top of the window you want to receive the events has focus, get it to grab the keyboard and send the events on to the underlying window. Make the top-level window transient, if you can. > If I set the tiny GUI app (on top) to "NeverFocus" and the other one to > "SloppyFocus" would that work (you say it "might")? Yes -- providing you then focus the underlying window when you need to type anything -- clearly mouse-events when you move it into the top window which has NeverFocus will still be interpreted, but because it never receives focus, the window underneath it is still focused, so you can emulate what you want here. And I really do mean "emulate" -- to fix this properly, do it in your application as it seems a very specific need. > Also I'm confused about how to identify the applications to FVWM (most > examples use the "name" of the application, but where is this name coming > from, how is it set: Do I have to launch the application from inside FVWM > to assign its name, or is the "name" what I see in a "ps -ef" for that > application?) FVWM will search for the name, resource and class of a window. Typically the Class is the name I would use. See FvwmIdent, xwininfo(1), xprop(1), etc. And don't top post. -- Thomas Adam -- "It was the cruelest game I've ever played and it's played inside my head." -- "Hush The Warmth", Gorky's Zygotic Mynci.
