On Mon, May 09, 2005 at 12:26:58AM -0400, David Wu wrote: > Hi all, I am wondering whether the following is a bug
Sorry for the late reply ... > I have a .fvwm2rc file with the following two lines > > Style * ClickToFocusRaises > Style xterm GrabFocus > > To reproduce the bug: > > 1. open any program and have mouse focus on it (perferably a browser, > something taking up a lot of screen size) > 2. start xterm > 3. xterm grabs focus, if the mouse happen to be over the xterm window, > repeat from step 1 until mouse is not over the xterm window and is over > the program opened in step 1 > 4 notice how xterm has focus and the mouse is not over it > 5 now click on the program opened in step one. notice that the window is > RAISED but *NOT* focused. > > if the policy states clicktofocusraise shouldnt the it raises and > focuses the window? this is very annoying. No, that is not a bug. When you use mouse focus, clicking in the window does *not* focus it (by design). Older versions did not allow to tune that behaviour, but the latest 2.5.x versions give you full control over all details of the focus policy. You want the styles: Style * FPClickToFocus, FPClickDecorToFocus Style * FPClickRaisesUnfocused, FPClickDecorRaisesUnfocused and probably Style * FPClickRaisesFocused, FPClickDecorRaisesFocused and maybe even Style * FPClickIconRaisesFocused Style * FPClickIconRaisesUnfocused Style * FPClickIconToFocus > the workaround is to move mouse over to xterm then move it back over to > the other program > > version is fvwm 2.5.12 compiled on Mar 18 2005 at 00:50:43 2.5.12 does have the new FP...-Styles. [snip] Ciao Dominik ^_^ ^_^ -- Dominik Vogt, [EMAIL PROTECTED]
signature.asc
Description: Digital signature
