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.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 29612 invoked from network); 13 Jul 2021 23:24:56 -0000 Received: from 1ess.inri.net (216.126.196.35) by inbox.vuxu.org with ESMTPUTF8; 13 Jul 2021 23:24:56 -0000 Received: from mail-pf1-f180.google.com ([209.85.210.180]) by 1ess; Tue Jul 13 13:43:15 -0400 2021 Received: by mail-pf1-f180.google.com with SMTP id b12so20296336pfv.6 for <9front@9front.org>; Tue, 13 Jul 2021 10:43:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=K6wuLjI3uETn3ib/zsVPNNSr4YbmpyLNhZ6hOATYdJc=; b=am3r6TpIdn8mNOkJAMBNDi3c1Y+mUBmFRGoRtWNnM9Aer8ahOK4RyIKp2Rw/udrlM6 SsbrFscWcK9uQ8HJ+PJwKdDE0FSoe14DChBYaZIGadBQ2q+E5VmB/PuS37xowE4vSvxw qW+54yMaCG4r7OFcraA5kicNWJ7JqVrE0uZhAx/f13oPBS8o4rxsyIck9s1cXwQFKpJT xVxGLpGZYTC4ZVSgJkePjK89wECL0gwnm/zsR8IrWWwcrem790jyqz8uclU1zZUMcQw/ /ZwKkNxcgqDYv1nx1tPkC0OmQLzVZKn744OGHgIs9hTiwKbK9Tw9OnJi1mSyhVvxDVbJ 8Q4Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=K6wuLjI3uETn3ib/zsVPNNSr4YbmpyLNhZ6hOATYdJc=; b=jTT/JXcWb6GvKHASbCuGnuw9+/6AXz2gCJtPz3NmD85qCNVcxjhS67fBjDX9h5/Osh 2FlIRBsHVBaA6cXMvGJvnipy24S+cbnzigaHtnUtXtPcs6AkoLJePLpcjrcjbspkSOGG Ur+Mc6kHYEuRHwVC9ToQy0TCcm5q+hwmiAFeO2/DyMwhEw8+6Xtpf2JBbX+r3Vf6Wb8K T8XQA4uklZ63BaOr0fyZVvlEQGI8Nc1TqrI7uThocIL3DtKaEmENAF9A9rU9ajV8Oh7F q/Dvg0kye6FjUS7CwsGKvzNgrOzXAPuXpelf8lLNdBe4AcHZ6J7U7co7KlR2th/W9t+F 1mRA== X-Gm-Message-State: AOAM533+AawtI6UOng+SqMNDCB99FYo16A7epkxfAqZ5xNCKg/sFt7aE gdwix7GbOLSxSqb9FJo2WQXKfeATf7JkchHk8zS5U1Ma X-Google-Smtp-Source: ABdhPJyfNpDjsu3tVJqMexZAZ2CxsKNPvWW1VDdR1x+8XEvrnDBvsTTSWA0p0w1ymDnMlhESE6dYaqZdKmYvw3AZp6k= X-Received: by 2002:aa7:943b:0:b029:321:809a:f0b with SMTP id y27-20020aa7943b0000b0290321809a0f0bmr5832957pfo.32.1626198188003; Tue, 13 Jul 2021 10:43:08 -0700 (PDT) MIME-Version: 1.0 References: <8CE29EA89CBA8F74C1D4D8EEF2528473@eigenstate.org> In-Reply-To: From: =?UTF-8?B?Sm9zw6kgTWlndWVsIFPDoW5jaGV6IEdhcmPDrWE=?= Date: Tue, 13 Jul 2021 19:42:56 +0200 Message-ID: To: 9front@9front.org Content-Type: text/plain; charset="UTF-8" List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: CSS injection reduce/map frontend Subject: Re: [9front] Mouse clipping patch Reply-To: 9front@9front.org Precedence: bulk The concept of focus itself is a rio invention, so it's natural that the way of giving it up is also rio-specific. Again: mouse comes with two sets of inputs: the pointer location and the buttons. The pointer location can decide the receiver end of the mouse events (well, not quite in the case of rio, because its focus doesn't follow the mouse, but you get the idea). On the other hand, keyboard can't "point" to where the input should be processed, so the concept of a "current window" fills that hole. It's natural that, if we have invented a synthetic way of "pointing to" a window with the keyboard (focus), we should also have a way of "pointing out" of a window with the keyboard (a "uncurrent" key). Maybe I'm overthinking it, but that's how I feel about it. Needless to say, feel free to offer any other alternative to escape the mouse clip. Feedback is very welcome :) On Tue, Jul 13, 2021 at 7:32 PM Stuart Morrow wrote: > > > Innermost-focused rio gets the control, with a key for "giving up" the > > focus (going then a "level" up in the stack) is what i propose. > > But it's so _untransparent_