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=0.0 required=5.0 tests=none autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 29490 invoked from network); 13 Jul 2021 03:21:10 -0000 Received: from 1ess.inri.net (216.126.196.35) by inbox.vuxu.org with ESMTPUTF8; 13 Jul 2021 03:21:10 -0000 Received: from mimir.eigenstate.org ([206.124.132.107]) by 1ess; Mon Jul 12 22:52:51 -0400 2021 Received: from abbatoir.myfiosgateway.com (pool-74-108-56-225.nycmny.fios.verizon.net [74.108.56.225]) by mimir.eigenstate.org (OpenSMTPD) with ESMTPSA id 05aee2f0 (TLSv1.2:ECDHE-RSA-AES256-SHA:256:NO) for <9front@9front.org>; Mon, 12 Jul 2021 19:45:55 -0700 (PDT) Message-ID: <23937AA2E442EF4F276AF2CCD3AC7DCA@eigenstate.org> To: 9front@9front.org Date: Mon, 12 Jul 2021 22:45:54 -0400 From: ori@eigenstate.org In-Reply-To: <8CE29EA89CBA8F74C1D4D8EEF2528473@eigenstate.org> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: service-oriented full-stack service Subject: Re: [9front] Mouse clipping patch Reply-To: 9front@9front.org Precedence: bulk Quoth ori@eigenstate.org: > > But also, do we need to do it? Is there any case > where we want to constrain the grab to anything > other than the whole window? What if the ctl > messages were just > > trap > release > > with no further parameters? > Also: in addition to dropping rect parsing and validation, we can keep the clip across resizes, since there's no ambiguity around where it should go: the client has no choice.