Hi all and happy New Year ! I am having a problem with the focus policies inside fvwm-crystal. I can choose between a few focus policies from the menu, and each time I choose a ClickToFocus based policy and have NumLock that is on, the focus is lost as soon than I make a window or page change, and the only way to get back the focus is to put NumLock to off.
For me, this is a real problem because it can be very time consuming and/or frustrating for a new fvwm/fvwm-crystal user to figure out than it have to press the NumLock in order to get back the focus. It can also be misleading and drive him/her to conclude than the focus policy in fvwm-crystal is completely out of order. It is 3 basic focus policies into fvwm: ClickToFocus, MouseFocus and SloppyFocus. NumLock, CapsLock and ScrollLock do interfere with ClickToFocus, but not with the other focus policies. According to the FAQ, a workaround is to use the IgnoreModifiers command. Another one is to use xmodmap to remove NumLock, CapsLock or ScrollLock. Well, for me those 2 workaround doesn't address the real problem that is than NumLock do interfere with ClickToFocus. What is the rationale for this behaviour ? And will it be possible to change this behaviour into fvwm ? Note than Maciej Delmanowski, the original fvwm-crytal author, did try to use the IgnoreModifiers command, but this was reverted back because this was causing more trouble than good. Ciao, Dominique Michel -- "We have the heroes we deserve."
