On Mon, Aug 05, 2002 at 08:54:29PM +0200, Martin Renold wrote: > Hi, > > On Mon, Aug 05, 2002 at 02:09:08AM +0200, Dominik Vogt wrote: > > On Fri, Aug 02, 2002 at 09:07:37PM +0200, Martin Renold wrote: > > > The problem was that the "section" keysym I used is bound on the german > > > keyboard also to the "s"-key in combination with some unknown modifier > > > (I've never used this). It is the same with some other keys. > > > > Ah yes, I unserstand the problem. I've made a different patch > > that does not prevent this bindings in general but only when there > > are no "better" matches for the keysym (i.e. if there are no keys > > that generate the keysym without any modifiers or with just shift > > or caps-lock). Try this code in place of the "default" clause > > you modified in Bindings.c: > > It doesn't work (I acutally tried it), and I know why. Perhaps my > description of the problem wasn't exact enough. Have a look at > # xmodmap -pke | grep section > keycode 39 = s S ssharp section > keycode 49 = section degree notsign > > What I want to bind is keycode 49 with no modifier pressed. The loop > iterates through each keycode, and executes for keycode 39 the default > statement, and binds it. It doesn't care about the "better" match > (keycode 49), and binds both, with no modifiers, which makes the "s" key > unuseable. The result was, that without my patch, I was unable to bind > the section key properly. > > What I would accept is that it binds to the "s" key only if no other > keycode is able to produce the section keysym. I thought about that, and > I think it would be more expensive to implement.
Please try the next snapshot or current CVS code. That should resolve the problem. Bye Dominik ^_^ ^_^ -- Dominik Vogt, [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] -- 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 [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
