FVWM Bug Tracking notification

new message incoming/852

Message summary for PR#852
        From: [EMAIL PROTECTED]
        Subject: Keysyms for special keys are not recognized
        Date: Thu, 07 Feb 2002 06:34:01 -0600
        0 replies       0 followups

====> ORIGINAL MESSAGE FOLLOWS <====

>From [EMAIL PROTECTED] Thu Feb 07 06:34:02 2002
Received: from karazm.math.uh.edu ([129.7.128.1])
        by malifon.math.uh.edu with esmtp (Exim 3.20 #1)
        id 16YnkY-0005wt-00
        for [EMAIL PROTECTED]; Thu, 07 Feb 2002 06:34:02 -0600
Received: from malifon.math.uh.edu (IDENT:[EMAIL PROTECTED] [129.7.128.13])
        by karazm.math.uh.edu (8.9.3/8.9.3) with ESMTP id GAA22084
        for <[EMAIL PROTECTED]>; Thu, 7 Feb 2002 06:34:02 -0600 (CST)
From: [EMAIL PROTECTED]
Received: from localhost ([127.0.0.1] ident=65534)
        by malifon.math.uh.edu with esmtp (Exim 3.20 #1)
        id 16YnkX-0005wp-00
        for [EMAIL PROTECTED]; Thu, 07 Feb 2002 06:34:01 -0600
To: [EMAIL PROTECTED]
Subject: Keysyms for special keys are not recognized
Message-Id: <[EMAIL PROTECTED]>
Date: Thu, 07 Feb 2002 06:34:01 -0600

Full_Name: Stanislav Meduna
Version: 2.2.5
CVS_Date: 
OS: Red Hat Linux 7.2
X_Server: XFree86 4.1.0
Submission from: (NULL) (212.88.180.5)


There are keyboards that provide special keys such as Power, WakeUp or
Standby. These keys return special keycodes that can be mapped to the
keysyms XF86PowerOff, XF86Standby, XF86WakeUp - see e.g. the XKB
definitions in /usr/X11R6/lib/X11/xkb/symbols/inet.

I did this mapping and I see the keysyms returned correctly when watching
them with xev. They are not mentioned in keysyms.h, but the XStringToKeysym
function also recognizes names such as XF86PowerOff and returns the
corresponding keysym.

I would now like to hook some actions to these keys. Unfortunately the fvwm
does not seem to recognize these keysyms and my bindings are ignored.

I am able to do this in the sawfish wm and I am successfully using other
keybindings in the fvwm, so I think that the problem is really in the fvwm.
The keysyms are a bit special in that they have the highest two bytes
non-null. My uneducated guess is that the keysym values get stripped to 16
bits somewhere.


--
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]

Reply via email to