>I do not have ClickToFocus set anywhere, and infact clicking on the dclock
>does not do any good. For that matter I do not have SloppyFocus set anywhere
>either. This truely looks like a bug to me. The mouse buttons do what
>they are supposed to though over the dclock, it is just the keyboard
>that either does not respond or responds in another window.
The dclock probably has set the hint :
WM_HINTS(WM_HINTS):
Client accepts input or input focus: False
xclock does this, so I bet dclock does too.
This means that the clock should not ever get the keyboard focus. Most window
managers ignore this property, because a number of applications set it
incorrectly. So, fvwm tried to move the focus from an xterm to the clock,
but found that the clock did not want focus. At this point one could argue
about whether the focus should move to root or back to the xterm, but I don't
think that it matters much. If want the standard broken behavior (give focus to
the clock), then you need to set
Style "*" Lenience
or just
Lenience
depending on which version of fvwm you have.
Rob
--
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 Tue Oct 31 1995 - 07:17:37 GMT