On 19 Aug 2002 11:13:13 +0200, Dominik Vogt wrote: > > On Sun, Aug 18, 2002 at 01:21:48AM +0000, Mikhael Goikhman wrote: > > On 17 Aug 2002 20:43:32 +0200, Giuseppe Della Ricca wrote: > > > > > > I have a doubt from the man page: > > > > > > GrabFocus causes a newly mapped window to > > > grab the focus, while GrabFocusOff turns > > > this off. GrabFocus is the default for > > > ClickToFocus windows and GrabFocusOff is the > > > default for MouseFocus and SloppyFocus win? > > > dows. Note that this option is switched > > > back to the default every time you change > > > the focus policy. You have to use it after > > > the initial ClickToFocus/MouseFocus/Sloppy? > > > Focus. > > > > > > to me (non native English) this means that if I issue: > > > > > > Style * ClickToFocus > > > > > > than I automatically get GrabFocus for free. But experimentally this is > > > not true (new windows are not raised/don't get focus). > > > > > > Everything is fine if I issue: > > > > > > Style * ClickToFocus, GrabFocus > > > > > > but GrabFocus should be the default with ClickToFocus, or not ? > > Ah yes. I wasn't aware of the old behaviour and changed it. > What should it do? Reset GrabFocus or leave it as it was?
The old (well, the current in 2.4.x) behaviour is resetting GrabFocus/Off on every ClickToFocus/SloppyFocus/MouseFocus/NeverFocus. I think we may change this, i.e. use the explicitely set GrabFocus if any. But then, I guess, we need a new command ClearStyle [option_list] to clear GrabFocus/Off flag, i.e. use the default for it... > > You forgot to say that you use the cvs version. > > > > I can reproduce this problem, i.e. ClickToFocus does not set GrabFocus, > > although I see in the code it does set. > > It now only sets the default. Once GrabFocus or GrabFocusOff is > used, the default is ignored. Well, try without config, do "Style some_xterm ClickToFocus", then start xterm -n some_xterm, no GrabFocus. So the default is always ignored. > > There is a more serious problem. With SloppyFocus/MouseFocus, GrabFocus > > only works now when the pointer is on the root and not in the window. > > I see no such problem. Can you narrow down the config to make > this happen? I already managed to find that this is because of FvwmEvent a week ago, but for some reason I thought it happens without it too. Minimal config: *FvwmEvent-NewWindow: PassId *FvwmEvent-NewWindow: add_window Something DestroyFunc Something AddToFunc Something + I Next (bla-bla) Nop FvwmEvent FvwmEvent-NewWindow Style mywindow GrabFocus # now from FvwmConsole or another focused xterm with pointer in it: Exec xterm -n mywindow Regards, Mikhael. -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
