Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!think.com!mintaka!ai-lab!fibula!ringrose
From: ringrose@fibula.ai.mit.edu (Robert Ringrose)
Newsgroups: comp.sys.sgi
Subject: Re: shift-click, control-click, and alt-click
Message-ID: <15445@life.ai.mit.edu>
Date: 30 Apr 91 20:15:24 GMT
References: <9104292244.AA26782@smaug.physics.mcgill.ca> <15418@life.ai.mit.edu> <15432@life.ai.mit.edu>
Sender: news@ai.mit.edu
Organization: MIT Artificial Intelligence Laboratory
Lines: 18


Problem solved.  It turns out that, although in the manual it states that
the keyboard is a special device which "reports an event only on a
downstroke, taking into account the <ctrl> and <shift> keys", you can still
read the status of the control, shift, and alt keys as buttons.

The catch is that you can still read them as buttons - they are defined in
device.h, so apparently (my) manual only gives a partial listing of the
defined buttons.

You can't check for shift-click as a single, queue-able event, but this
is close enough for what I need to do.

	- Robert
(Thanks to Andrew Myers and Lee Campbell for pointing me in the right
direction)

"There's always one more bu6."