How do I map modifier key?

[Billy Ng]

For HP-Unix 10.2, when I press the NumLock key on, the numeric keypad does not respond for numeric numbers (such as 1, 2 3...8,9,0). When I use the command "xmodmap -pk", it shows that the numeric keypads are assigned for the first two columns. For example, for number keypad 2, the first column is assigned for KP_Down, and the second is assigned for KP_2. (I get numeric 2 with pressing the Shift key, and "Down arrow" without the shift key).
Then, I try to add KP_2 again at the third column for Num_Lock. (Note that I assigned Num_Lock for mod1 key) However, with Num_Lock on, I still get the "Down arrow" key not numeric 2. Any suggestion?

[harry d brown jr]

You need to tell us how and what you are using to connect to your HP 10.20 box, like Exceed, Reflection, direct connect console, ...

live free or die
harry

[Billy Ng]

Direct Connect with a PS/2 keyboard. Thanks!!

[harry d brown jr]

What kind of server/workstation?

cde, dt, ... ??

live free or die
harry

[Billy Ng]

CDE running on a workstation...that's all I know...

[Billy Ng]

With a few experiments, I found something interesting. If I have "Num_Lock" and "Mode_switch" keys assigned at the same modifier key (say mod1), the numeric key pad works!!
However, this causes my terminal freezing, at which I can move my terminal window or any other window.
I tried to replace the Num_Lock key to the letter "p" for mod1. When I press and hold "p", the numeric key pad works but the windows are still frozen. Of course, the windows are not frozen after I release the "p" key.
So my finding is: when I have the modifier key on, it freezes the windows. Does anyone have any idea to deal with that??

[Wodisch]

Hi Billy,

not certain that you can accomplish that at all!
The reason is that HP uses the "NumLock" and the "Pause" keys as subtitutes for the (original hp terminal keyboards) "System" and "Menu" keys - which are used by e.g. "hpterm" and such...

FWIW,
Wodisch

[Billy Ng]

Thanks!

It is true that NumLock and Pause are used for something else, eg. menus of HP Term

From my last experiment (see my last message), I found that any "active" modifier key (mod1 - mod5) can cause the windows "sticking". "Sticking" means that windows are not movable and cannot come to the front. You can assign any key for the modifier key and will get the same effect. I am wondering if anyone has the same experience.

[Mike Stroyan · Accepted solution]

The Num_Lock key was not a modifier in the original X11 design. If you look at the usenet discussions that turn up with a search of
http://groups.google.com/groups?q=numlock+event+group:comp.windows.x.motif
you will see that there is a long history of discussions about Num_Lock.
The first generation of topics was around "How do I make Num_Lock into a locking modifier like CapsLock?"
The second generation of topics occured after some vendors made Num_Lock into a locking modifier. Then the questions shifted to "Why doesn't my mouse or key event do the same thing with Num_Lock on as with Num_Lock off?"
The sad truth is that the Xt/Motif event translation notation cares about modifiers, so every application would have to go to extra effort to ignore Caps_Lock and Num_Lock when deciding what to do with events. Many programs ignore certain events when a locking modifier is on. The CDE window manager is one of those programs, so it ignores your button presses when you make Num_Lock into a modifier and cause it to be on.

[Billy Ng]

Thank you so much for your response. =)
The google link is helpful. It explains all my problems. I will try out the suggested solution: modifying setting of window manager.