9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Paul Lalonde <paul.a.lalonde@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] porting projects...
Date: Mon, 6 Sep 2021 12:47:21 -0700	[thread overview]
Message-ID: <CA+POUVgz2PLGiUA+SDmeF++FPDujs3FUCLe7QCsqQJbd=x6oKQ@mail.gmail.com> (raw)
In-Reply-To: <CABB-WO_t7VUfoHSmhSGJ+ObJfhpPSrA_WO-qL77cQcYnbY3nmw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1053 bytes --]

It does look like this would need raw mouse state to get the DX/Dy data
instead of absolute screen positions.

On Mon, Sep 6, 2021, 12:36 PM Stuart Morrow <morrow.stuart@gmail.com> wrote:

> On 06/09/2021, Skip Tavakkolian <skip.tavakkolian@gmail.com> wrote:
> > To be clear, the discussion is about sharing a Plan 9 term's
> > mouse/keyboard with non-Plan 9 machines/displays.
>
> I know. See previous post.
>
> > The usual way is to layer file-servers to build up the namespace that
> > you need.
> I know.
>
> > The extended (freerange?) mouse would keep track of off-screen
> > movement and forward them to clients.
> 
> How's it supposed use information the operating system doesn't give it.
> 
> When I have said /dev/mouse and screen in this thread, I've meant
> #m/mouse and the actual display.

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Td6b6b3e98268ecde-M57c04c24bece9e2a94b3e355
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

[-- Attachment #2: Type: text/html, Size: 2438 bytes --]

  reply	other threads:[~2021-09-06 19:47 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-03 23:49 Conor Williams
2021-09-04  3:23 ` Lucio De Re
2021-09-04  3:50 ` Jens Staal
2021-09-04  5:41   ` Conor Williams
2021-09-04  8:04 ` Philip Silva via 9fans
2021-09-04 15:24   ` Sigrid Solveig Haflínudóttir
2021-09-05  7:53     ` Philip Silva via 9fans
2021-09-04  9:22 ` Steve Simon
2021-09-04 16:17   ` hiro
2021-09-04 18:55     ` Michael Misch
2021-09-04 20:35       ` Steve Simon
2021-09-04 21:15         ` hiro
2021-09-04 21:56           ` Stuart Morrow
2021-09-05  6:16             ` Conor Williams
2021-09-05  8:11             ` hiro
2021-09-06 11:29             ` cinap_lenrek
2021-09-06 17:12             ` Skip Tavakkolian
2021-09-06 19:32               ` Stuart Morrow
2021-09-06 19:47                 ` Paul Lalonde [this message]
2021-09-06 20:12                   ` Stuart Morrow
2021-09-06 20:26                     ` Paul Lalonde
2021-09-06 21:50                       ` Steve Simon
2021-09-06 22:09                   ` ori
2021-09-06 22:17                 ` hiro
2021-09-20  1:23                   ` Conor Williams
2021-09-20  7:57                     ` Jens Staal
2021-09-20  8:10                       ` Conor Williams
2021-09-04 14:22 ` ori

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='CA+POUVgz2PLGiUA+SDmeF++FPDujs3FUCLe7QCsqQJbd=x6oKQ@mail.gmail.com' \
    --to=paul.a.lalonde@gmail.com \
    --cc=9fans@9fans.net \
    /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).