🚀 go-pugleaf

Could you please forward this to kelem@aero2 or perhaps attempt
an answer yourself.

Many thanks.

We (at Villanova University) are trying to port magic (using AED767s) to
a Pyramid 90X.  We are having the following problem:

The buttons on the 4 button puck (on a Summagraphics Bit-Pad One) do not
appear to be working correctly.  They appear to function in close to a normal
fashion if the top button is pressed and held while pressing the other buttons.

Some code added to "aedReadTablet" (in grAed4.c) seems to indicate that the
right codes are being seen by the system when the buttons are pressed.

Code added to "grAedMouseDevice" (also in grAed4.c) seems to indicate that
the appropriate codes are being received by it.

The difference (between having the top (yellow) button down always or not)
is that grAedMouseDevice is called *only* when a button is pressed when
the top button is not being held down, and is called on both transitions
when the top button is being held down.

I haven't been able to find where the differences occur; the bitpads work
fine with caesar and kic, so we assume that they are appropriately set up.

Any help would be much appreciated!!!

Thanks, 

Ed Hepler

at Full Time Job (GE Space Center, Valley Forge, Pa.)
..!houxm!edison!elh
(215)354-1775
or at part time teaching job (Villanova Univ., Villanova, Pa.)
..!houxm!packard!topaz!pyrnj!vu-vlsi-1!elh

PS: We *have* applied the AED767 bug fix of July 1, 1985 by kelem@aero2
which concerned magic on AED767s (even though a few lines of our
transmission seemed garbled)