keycode > 117 problem.

keycode > 117 problem.

Post by Torsten Studen » Wed, 01 Oct 1997 04:00:00



I'm trying to configure my xmodmap so that's possible to use the keys
F13-F20, Help, Do on a DEC-keyboard, but their keycode is partly >
117, which leads to the following problem:


xmodmap:  commandline:0:  bad keycode value (out of range)
xmodmap:  1 error encountered, aborting.

xmodmap's handle.c uses max_keycode, but I don't know where this
variable is set, I looked up /usr/X11R6/include/xlib.h, but didn't find a
hint to max_keycode beside it's definition.  :-(

Simply overriding this if-clause does not work.

Do you have any hint how to persuade the Xserver to accept a
keycode .gt. 117?

        Torsten

--
 ---------------------------------------------------------------------
| Mail  address: FB 8 Physik, BUGH Wuppertal, 42097 Wuppertal, Germany|

| Phone (W-tal): +49-202-439-2740  or +49-177-2 38 38 56              |
| Fax          : +49-202-439-2811  pgp public-key available (finger)  |
 ---------------------------------------------------------------------

 
 
 

keycode > 117 problem.

Post by Kaleb S. KEITHLE » Wed, 01 Oct 1997 04:00:00



> I'm trying to configure my xmodmap so that's possible to use the keys
> F13-F20, Help, Do on a DEC-keyboard, but their keycode is partly >
> 117, which leads to the following problem:


> xmodmap:  commandline:0:  bad keycode value (out of range)
> xmodmap:  1 error encountered, aborting.

> xmodmap's handle.c uses max_keycode, but I don't know where this
> variable is set,

You didn't look very hard I guess. If you do a `grep max_keycode *.c` in
the xmodmap sources I think you'll see where it is set.

Quote:> I looked up /usr/X11R6/include/xlib.h, but didn't find a
> hint to max_keycode beside it's definition.  :-(

> Simply overriding this if-clause does not work.

> Do you have any hint how to persuade the Xserver to accept a
> keycode .gt. 117?

You have to remember that X is a protocol. Clients, like xmodmap, find
out what the max_keycode is from the server. The way most servers are
written, once it has told the client that the max_keycode is 117, no
amount of protocol is going to change that.

If you're using the XFree86 server, you can get the source and expand
the default keymap in the sources and recompile. As far as that goes, if
you're using the XFree86 server you could cobble up your own XKB keymap
definition that has the extra keys you want and tell the server to use
that keymap.

--

Kaleb S. KEITHLEY

 
 
 

1. jdk 117 v1a -> any other choice?

I still cannot run any industrial strength threaded apps with either the
green or native
thread libraries.  Also, AWT seems terminally hosed.  (For some wierd reason
if
I hide a window, and show it again, it won't get any keyboard input.)
sun.audio stuff is broke,
but I can live with that.  (Also, window positioning for me is always hosed
with fvwm with
redhat desktop.)

Anyway, as I don't have the time/resources to help out on the 117 project,
does anyone
know of any working java implementations for linux?

Conversely, if the blackdown guys are reading this, I'll send you source to
one of my
client/server applications that break 117 (and no, it is not my code.)

B.

2. Daemon on demand question

3. QIC-117 kernel compilation problems

4. Email text problems.

5. Problems with mmap under 2.1.117 SMP

6. damnitall - gimp problems

7. 2.1.117 + ATM-patch compile problem

8. Remote rsh commands failure

9. problem with kernel 2.1.117

10. Problems rebuilding kernel with QIC-117 tape support

11. Build problems in 2.1.117: no crt1.o file?

12. 2.1.117 + ATM-patch compile problem

13. Multimedia keyboard with keycodes > 256 problem