9front - general discussion about 9front
 help / color / mirror / Atom feed
From: "Benjamin Purcell" <spew@cbza.org>
To: 9front@9front.org
Subject: Re: [9front] Mouse clipping patch
Date: Tue, 13 Jul 2021 17:22:45 -0400	[thread overview]
Message-ID: <75702e8a-d401-4c1a-9eae-2e5181e4e74a@www.fastmail.com> (raw)
In-Reply-To: <31017285-5870-4BF4-96E5-EDC5E307F6FF@gmail.com>

If rio becomes self-aware we all die.

On Tue, Jul 13, 2021, at 13:26, Xiao-Yong Jin wrote:
> 
> > On Jul 13, 2021, at 11:16 AM, José Miguel Sánchez García <soy.jmi2k@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.
> 
> Now you are breaking the fourth wall and making rio aware that there
> may (or may not?) be another world outside it.  By default rio
> passes input down to its children, after breaking this fourth wall,
> rio has to process the input somehow and determine if it wants to
> "give up" the focus to its parent.  What if its child that has the
> focus is a rio?  How does it know how many of its descendent rios
> have "given up"?

  parent reply	other threads:[~2021-07-14 16:19 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-12 19:50 José Miguel Sánchez García
2021-07-13  2:36 ` ori
2021-07-13  2:45   ` ori
2021-07-13 14:03     ` Stuart Morrow
2021-08-11  0:56       ` Stuart Morrow
2021-07-13  3:14   ` José Miguel Sánchez García
2021-07-13  8:25     ` hiro
2021-07-13 10:27       ` José Miguel Sánchez García
2021-07-13 14:05         ` Stuart Morrow
2021-07-13 15:27           ` kvik
2021-07-13 16:28             ` ori
     [not found]           ` <CAFSF3XPhDeKiKXdsL0Abnderm45Uc2GCPYsi6ygSaBkf7gDBmA@mail.gmail.com>
2021-07-13 15:09             ` José Miguel Sánchez García
2021-07-13 15:34               ` José Miguel Sánchez García
2021-07-14 12:04                 ` Stuart Morrow
2021-07-15  2:06                   ` Xiao-Yong Jin
2021-07-13 15:11             ` Stuart Morrow
2021-07-13 16:16               ` José Miguel Sánchez García
2021-07-13 16:27                 ` Stuart Morrow
2021-07-13 17:42                   ` José Miguel Sánchez García
2021-07-13 21:20                     ` hiro
2021-07-13 21:57                     ` ori
2021-07-14 11:55                       ` Stuart Morrow
2021-07-13 17:26                 ` Xiao-Yong Jin
2021-07-13 17:45                   ` Stuart Morrow
2021-07-13 18:29                   ` José Miguel Sánchez García
2021-07-13 21:32                     ` hiro
2021-07-13 21:22                   ` Benjamin Purcell [this message]
2021-07-13 16:21               ` hiro
2021-07-13 16:29             ` ori
2021-07-14  8:42               ` hiro
2021-07-14 11:52                 ` Stuart Morrow
2021-07-14 12:17                   ` hiro
2021-07-15  3:13                     ` ori
2021-07-14 12:53                   ` José Miguel Sánchez García
2021-07-15  7:36                     ` hiro
2021-07-14 14:26                 ` ori
2021-07-13 12:00     ` José Miguel Sánchez García
2021-07-13 12:43   ` kvik
2021-07-13 13:36     ` hiro
2021-07-13 13:40       ` hiro
2021-07-14 22:57 ` ori
2021-07-15  7:40   ` hiro

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=75702e8a-d401-4c1a-9eae-2e5181e4e74a@www.fastmail.com \
    --to=spew@cbza.org \
    --cc=9front@9front.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).