[comp.windows.open-look] cmdtool uses keycodes not keysyms?

km@mathcs.emory.edu (Ken Mandelberg) (11/10/90)

I use xmodmap to set the keysym for the SS1 backspace key (keycode 50)
and the delete key (keycode 73) to Delete (keysym 0xffff). xmodmap -pk
and xev both confirm this. However, I can have a cmdtool on my desk in
which punching the backspace key gives a different result than punching
the delete key (generally ^H for punching backspace while delete triggers
an erase).

What cmdtool does is clearly effected by its state (scrolling on or off for
example), but not in a way that I can reliably detect the pattern. Sometimes
I have two cmdtools on my desktop that appear to be in the same state but
treat the two keys differently.

Whatever the grand plan (or bug) in cmdtool is, it is clear that in some
cases its using keycodes not keysyms. This is on OWR2.

Anyone know the details?

-- 
Ken Mandelberg      | km@mathcs.emory.edu          PREFERRED
Emory University    | {rutgers,gatech}!emory!km    UUCP 
Dept of Math and CS | km@emory.bitnet              NON-DOMAIN BITNET  
Atlanta, GA 30322   | Phone: (404) 727-7963