Path: utzoo!attcan!uunet!sco!mikep
From: mikep@sco.COM (Mike Patnode)
Newsgroups: comp.windows.x
Subject: The NumLock Key - R5 Request
Message-ID: <6968@scolex.sco.COM>
Date: 3 Jul 90 17:06:17 GMT
Sender: news@sco.COM
Reply-To: mikep@sco.COM (Mike Patnode)
Distribution: na
Organization: The Santa Cruz Operation, Inc.
Lines: 20


One of the largest problems we have run into is the lack of a standard
way to deal with the NumLock key.  Currently, there are at least three
different ways to approach the problem: per application, modifying
XLookupString(), modifying the server.   It would be very helpful if the
X Consortium could define how the NumLock key should be handled
and interpeted, as was done with Shift, Cntl and Caps Lock.   (See Page
352 of the Purple/Red Book - Section 5 of the Protocol)

The number of 286/386/486 machines which are/will be running UNIX and X
within the next few years should justify such a definition.

A method similar to the Caps Lock key would be my recommendation.


-- 
Mike Patnode					The Santa Cruz Operation 
SCO Software Engineer				400 Encinal Street
{ucscc,uunet}!sco!mikep	 mikep@sco.COM  	P.O. Box 1900
(408) 458-1422                                  Santa Cruz, CA 95061