From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: *** X-Spam-Status: No, score=3.3 required=5.0 tests=BULK_RE_SUSP_NTLD,DKIM_INVALID, DKIM_SIGNED,FROM_SUSPICIOUS_NTLD,PDS_OTHER_BAD_TLD,RCVD_IN_DNSWL_NONE autolearn=no autolearn_force=no version=3.4.4 Received: (qmail 25545 invoked from network); 9 Dec 2020 00:16:45 -0000 Received: from ewsd.inri.net (107.191.116.128) by inbox.vuxu.org with ESMTPUTF8; 9 Dec 2020 00:16:45 -0000 Received: from out1.migadu.com ([91.121.223.63]) by ewsd; Tue Dec 8 19:14:09 -0500 2020 Message-ID: <0837C1671575B6BA0BF49EF1E2851C00@hog> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=a-b.xyz; s=key1; t=1607472890; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to; bh=kJCxQs3/CVcWuxVDwJE6GXD+obrDrKKtlcvhxLRuLmM=; b=KPgi5/WN7oF/JXeaP4MQMvMSuVLBNvQ87SKEThGdEakJi+MU0tCfRo8OSMsavCCe6LQ+j/ bIg4TIEcszUv6uNW6rj+ugdf/FtT53eVbRfJFDC/DgzVbfDSk294v/XAJ74Y7amhz/NRBR eQ6HPxqz0L1WxaF0X1OGyhqChIbvtuXabOFcRQ/ASf2n2Ag6DleGOLhLPtwxqsbL4U6NjV hOMkp11eakHtsaLsTihqJR6OWEXV1sGBhmXkPSzWAWT/XQctx3CHP+W1r+YfYpd9hcA0V9 VMNMmQRwWYnRZcBXR9sdFJBaU+B32ewvO6ihacSaRTvFhlQndbJ6cRolUiTDrA== To: 9front@9front.org X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: kvik@a-b.xyz In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Migadu-Flow: FLOW_OUT X-Migadu-Auth-User: kvik@a-b.xyz Date: Wed, 09 Dec 2020 00:14:50 GMT List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: shader-scale module-oriented backend Subject: Re: [9front] nusb/kb mouse handling Reply-To: 9front@9front.org Precedence: bulk Quoth umbraticus@prosimetrum.com: > Nice. So you'd be in favour of b4 starting at 32, skipping over the > scrollwheel's 8/16. The owner of the "logitech 5 button mouse" could > follow your lead if he still wants b4 mapped to b2, or we could extend > the buttonmap functionality described in mouse(3) ... The way I see this, the driver should report unmapped input events and let the rest of the input system decide what they mean. The problem with mapping in mouse(3) is with it applying to all devices, making it useless for dealing with per-device oddities. I don't have a big idea on how to handle the general input issue. Mousetrap works to make my Huge usable but I'm not convinced that it's the way things oughta be. The main problem is nothing in Plan 9 knows how to deal with these extra input events. If I'm remembering correctly we'r even filtering out anything above 0x10 in mouse(3) or rio.