Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!wuarchive!uunet!bu.edu!nntp-read!jbw From: jbw@bigbird.bu.edu (Joe Wells) Newsgroups: comp.windows.x Subject: Re: Ncd keyboard num-lock Message-ID: Date: 22 Feb 91 19:27:32 GMT References: <9102150057.AA18369@pepper.com> Sender: news@bu.edu.bu.edu Organization: Boston University Computer Science Department Lines: 24 In-reply-to: dc@ncd.COM's message of 15 Feb 91 00:57:59 GMT dc@ncd.COM (Dave Cornelius) writes: >From: parmelee@wayback.cs.cornell.edu (Larry Parmelee) >Most of the NCD keys generate both a keypress and keyrelease event, >but the num lock (and I believe the caps lock) are "special" (broken :-) >and generate only one event for each for each actual physical press/ >release cycle. The locking modifiers toggle press and release by design. They are special, as you note, but this operation is not broken. Again, all this happens to be in software on the NCD, but that's really academic. Num_Lock isn't supposed to be a locking modifier unless it's listed in the modifier table! Even after removing "Num_Lock" from any mention in the modifier table with xmodmap, Num_Lock on an NCD still only sends either a KeyPress or a KeyRelease event, but not both. This is bogus! The only way around this is to rename the key, which should be unnecessary. I should be able to have the keys' X names be the same as the physical labels on the keys, and, at the same time, I should be able to make the keys do exactly what I want them to do. -- Joe Wells