Hello -- On 30 April 2010 15:31, Shriver, Daniel <[email protected]> wrote: >> 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
No, this isn't right. Here: Style window_at_bottom SloppyFocus, GrabFocus Style window_at_top NeverFocus, PositionPlacement x y Focus is a command, not a style option. But GrabFocus will cause the focus to warp to the window when it's mapped. You might have to sort the ordering out yourself as to when/where these windows are mapped, and in what order. I've given you an example of PositionPlacement, so that you can place this window which is on top of the window to receive focus in the right place. > When I reload my config file these "classes" aren't running yet (they get run > later) is that an issue when making style declarations? No, because FVWM applies the match once the window is mapped. -- Thomas Adam
