On Sat, Aug 25, 2001 at 04:10:41AM -0500, brendan_at_cs.uchicago.edu wrote:
> Possible bug:
>
> (maybe i just configured something wrong)
>
> F1 and F2 do what F11 and F12 were bound too, irrespective of their own
> bindings. F11 and F12 work as expected. I know the keymaps are ok because
> I had ctwm doing the exact same config earlier today, so i know hitting
> F1 really is sending and F1.
>
> Here are all of my Key definitions:
>
> Key F1 A N Iconify
> ...
> Key F11 A N Restart
> ...
>
> My fvwm version is 2.4.0
That's because Shift-F1 is the same as F11. It is not possible to
always do the right thing with key bindings automatically. Your
xmodmap (X keyboard mapping table) probably looks like this:
key code key symbol key symbol (with shift)
------------------------------------------------------
67 0xffbe (F1) 0xffc8 (F11)
95 0xffc8 (F11)
The F11 key generates the key code 95 while the F1 key generates
key code 67. With no modifiers pressed, this is interpreted as
the key name "F11" or "F1". But if the F1 key is pressed together
with shift, it generates "F11" too. Therefore the code in fvwm
treats the F1 key as if it were labeled F11 in this case.
Sometimes this is a good idea (namely on the numeric key pad) and
sometimes it isn't (in your case). I have written a patch that
will be part of the upcoming 2.4.1 release. It deals with the
given situation, but can only handle the shift and caps-lock
modifier keys.
A simple workaround is to swap the order of the Key commands in
your config file. With
Key F11 A N Restart
Key F1 A N Iconify
The F1 key overrides the binding created by the F11 key, so that
both keys should work as expected.
Bye
Dominik ^_^ ^_^
--
Dominik Vogt, dominik.vogt_at_gmx.de
Reply-To: dominik.vogt_at_gmx.de
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Sat Aug 25 2001 - 08:37:58 BST