Path: utzoo!attcan!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!bloom-beacon!EXPO.LCS.MIT.EDU!rws
From: rws@EXPO.LCS.MIT.EDU
Newsgroups: comp.windows.x
Subject: Re: Sun Type 4 Keyboad and X
Message-ID: <8906091558.AA02886@expire.lcs.mit.edu>
Date: 9 Jun 89 15:58:54 GMT
References: <1446@stan.Solbourne.COM>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 14


    The problem is that the num_lock key
    is defined as a function key, not as a modifier.

That's not really the problem at all.  The real problem is that neither the
Xlib nor the Xt key handling routines recognize Num Lock semantics.  If you got
past that, you might get to the semantics of IsMiscFunctionKey (but I doubt
it).

    (RWS - If you are out there, WHY?)

Am I responsible for everything?  Probably because whoever defined the macro
had never touched an IBM keyboard before.  If you think it's wrong, please
file a bug report.