> No, I don't mean that -- you just need to ensure the bottom window has focus > -- as soon as it does, and the pointer moves into the top window which has > NeverFocus set as a style condition, the underlying window will receive all > keyboard input, irrespective of where the pointer is at that point.
So what I've tried is: Style <1> NeverFocus Style <2> Focus NoWarp And Style <1> NeverFocus Style <2> Focus NoWarp, SloppyFocus Where: <1> is the word I got for "class" in FvwmIdent for the GUI I want to never have the keyboard and <2> is the one I always want to have the keyboard Unfortunately, I still seem to not get keyboard events in <2> until I move the pointer off of it. When I reload my config file these "classes" aren't running yet (they get run later) is that an issue when making style declarations?
