Re: [9front] Mouse clipping patch

["José Miguel Sánchez García" <soy.jmi2k@gmail.com>]

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 <morrow.stuart@gmail.com> 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_