Hello,
> If you want to debug this, you should
> start in the files fvwm/bindings.c and libs/Bindings.c.
Umm, you was right - I did not have the keycode mapping - at the
time of fvwm starting, that is :-( My environment starts a keyboard
mapping application, so I see the mapping when running my test
application, but this is of course after fvwm parsed the bindings.
So I know how to solve my problem, but this IMHO revealed another
one. There are environments that use to change the keyboard
mapping on the fly (and not via the keyboard specification
in the X server) - Slovakia (where I live) is one of such regions.
The fvwm binds its keys according to keycodes. So when the
keycode->keysym mapping changes, fvwm does not know about it.
On the slovak keyboard this could mean that Alt-Z on the
local keyboard must be specified as Alt-Y in the fvwm config.
I inspected the code and I don't see any easy solution. While
there is no problem to catch the KeymapNotify event, the user's
specification of the mappings is lost after the parsing and
cannot be reconstructed from the linked list of bindings.
I thought of remembering of the Key commands and replaying
them on the KeymapNotify, but all the possibilities of interaction
using FvwmConsole etc. make this no easy task.
I can live with what I have (I just change the map before the window
manager starts or reissue the "Key" command after each mapping change),
but if you have some idea, how this could be addressed in the fvwm
itself, let me know.
Thanks
--
Stano
--
Visit the official FVWM web page at <URL:http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm-workers" in the
body of a message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]
