>...
>Button1Motion through Button5Motion, but that's it) and you do not get
>state bits in other events for any but the first five buttons.  But I
>see no other restrictions.  (Am I still missing something?)
>
>After all, didn't we just hear from someone who was using a pointer
>with ten buttons (counting the two which are really a wheel)?
>
>/~\ The ASCII				der Mouse
>\ / Ribbon Campaign
> X  Against HTML	       mouse@rodents.montreal.qc.ca
>/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B
>
	Do we know he isn't using the X Input extension.  In the NetBSD tree
and most other copies I've seen, it is built and enabled by default.  Then
there is no effective limit (I think there might be an 8 bit limit, but it
might also be 16 bits - I'd have to look at the code).  I think the idea was
to allow both the capabilities of some of the bitpads that had both keys with
glyphs as well as simple buttons and devices like the "SpaceBall" which was
a 4-D controller that fit nicely into your hand (and cost a small fortune).
The X Input extension was done mostly by Erik at SGI, the original mouse
"hack" was done at IBM where the PS/2 was just about to be released, with a
built-in port, and the "IBM" mouse (instead of the Microsoft flavors, either
serial or "Inport") which had just two buttons (since that was the standard
MS had already brought to market and which most DOS code was already written
for) - about two years passed in between and at SGI we had to support all the
things that had had specific GL extensions, like the virtual reality glove
and the other devices mentioned -- The lower numbered releases of X11 were a
learning experience for everyone involved;  By R4 it was most of the way there,
and there hasn't been a R7 even though R6 was over ten years ago.  And there
almost certainly will never be a X12 despite X10 having been commercialized
by several companies (I think Dec even sent some customers X6).


	Paul Shupak
	track@plectere.com