SetPointerMapping protocol braindeadedness

[Daniel Stone]

On Mon, Jul 03, 2006 at 02:55:16PM +0300, Daniel Stone wrote:
> Hi all,
> The protocol spec for SetPointerMapping says:
> 'A zero element disables a button.  Elements are not restricted in value
> by the number of physical buttons, but no two elements can have the same
> nonzero value (or a Value error results).'
> 
> Right now, we test for button values being n > 1 and n < 255.  I propose
> we trade one protocol violation for another: allow n == 0 to disable
> buttons altogether, but at the same time, also allow duplicate button
> mappings (e.g. 1 2 3 4 5 6 7 3, being valid, if you want button eight to
> behave like button three).
> 
> Does anyone know why this restriction was enforced in the protocol,
> and/or have any objections to this change?

In case you're curious: someone asked me how to make his under-thumb
button (8) behave like the middle button (3) and have them both work
as paste.  I didn't have a good answer.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 191 bytes
Desc: Digital signature
URL: <http://lists.x.org/archives/xorg/attachments/20060703/1ebc55b2/attachment.pgp>