Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!uunet!mcsun!ukc!harrier.ukc.ac.uk!rlh2
From: rlh2@ukc.ac.uk (Richard Hesketh)
Newsgroups: comp.windows.x
Subject: Athena Text Widget not recognizing keys on certain keyboard (?)
Message-ID: <5213@harrier.ukc.ac.uk>
Date: 30 Jul 90 18:00:45 GMT
Reply-To: rlh2@ukc.ac.uk (Richard Hesketh)
Organization: Computing Lab, University of Kent at Canterbury, UK.
Lines: 27
We use here a varied collection of NCD X terminals, DEC and Sun workstations.
It has been noticed that using toolkit programs that require text entry
via the Athena Text widget that what *we* think the key is ..
i.e. the key immediately to the left of the spacebar .. does not work.
I assume that this is because the keyboard generates a different KeySym
(Alt in the case of the NCD's and something else for DEC's "Compose" key).
Now the rub comes because it confuses our users who are used to thinking
that the key to the left of the space bar is the "Meta" key for window
manager functions.
It seems obvious to me that we need to either use xmodmap to change what
KeySyms are generated for these different displays to generate the
KeySym required by the Text Widget; Or to provide
an #augment or #override translation line for Text widgets.
I prefer the xmodmap approach, however, I was wondering if anybody else
has coped with this problem? What is your solution? I'd be grateful
for any answers.
Thanks,
Richard Hesketh : @nsfnet-relay.ac.uk:rlh2@ukc.ac.uk
: rlh2@ukc.ac.uk ..!mcsun!ukc!rlh2
---
Computing Lab., University of Kent at Canterbury,
Canterbury, Kent, CT2 7NF, United Kingdom. Tel: +44 227 764000 ext 7620/3682