Randall S. Winchester writes:
> When I startup "dclock", and move my mouse over the window, the border
> does not change color, as a sign of focus change. If the dclock is very near
> an xterm then I can move from the xterm to the dclock and the focus is still
> in the xterm. This is very odd behaviour. Other WM's do not have this
> problem. Any ideas?
>
This is actually a desirable feature that ONLY FVWM has. I suspect that you
have enabled SloppyFocus policy and have the Style for dclock to include
ClickFocus.
What this means to the user is that:
Sytle: The only way to get focus in a clickFocus window is to actually
click on it. The rationale behind this is that there are certain windows
(clocks, xloads etc) that you do not want to get focus arbitrarily when the
pointer moves over it.
SloppyFocus: when the pointer moves from a window onto the root window (or
a window with click focus) the focus stays in the window you are
leaving. This is a really great feature because you can be working in a
window and have the mouse bumped and you will still be typing in the window
you think you are.
I beleive the sample .fvwmrc files set this behaviour. Look for the
following lines in your .fvwmrc file if you do not like the behaviour.
Style "*lock" NoTitle, NoHandles, Sticky, WindowListSkip,ClickToFocus
Style "*" SloppyFocus
-Greg
---------------------------------------------------------------------
Greg Veres (gveres_at_cgl.uwaterloo.ca) | You got your whole life to
Computer Graphics Lab, University Of Waterloo| do something and thats not
http://www.cgl.uwaterloo.ca/~gveres | very long. - Ani Difranco
--
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Mon Oct 30 1995 - 14:45:36 GMT