> 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.
for a second i actually forgot about #m having absolute coordinates,
but as later mails explain there's the warping hac
Quoth Paul Lalonde :
> It does look like this would need raw mouse state to get the DX/Dy data
> instead of absolute screen positions.
It's a little ugly, but the same mouse warping
hack that quake uses will serve here.
--
9fans: 9fans
Permalink:
https:/
mouse sharing is not end, there is also cut and paste integration - relatively
easy but not to be forgotten.
i think you could also play some fun tricks with drag and drop on other os’s
passing a (modified) path to the plumber (/n/remote-host/file-path).
finally plumbing a url on plan9 could
Do the other platforms do their own acceleration management? That makes
you want to feed deltas instead of absolutes.
On Mon, Sep 6, 2021, 1:13 PM Stuart Morrow wrote:
> On 06/09/2021, Paul Lalonde wrote:
> > It does look like this would need raw mouse state to get the DX/Dy data
> > instead o
On 06/09/2021, Paul Lalonde wrote:
> It does look like this would need raw mouse state to get the DX/Dy data
> instead of absolute screen positions.
You could detect when it's at the edge, make it invisible (as
screenlock does), make it visible (on the box that doesn't have the
mouse plugged in)
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 wrote:
> On 06/09/2021, Skip Tavakkolian wrote:
> > To be clear, the discussion is about sharing a Plan 9 term's
> > mouse/keyboard with non-
On 06/09/2021, Skip Tavakkolian 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 (freera
The usual way is to layer file-servers to build up the namespace that
you need. See tippy (https://github.com/9nut/plan9cmd) for a simple
/dev/mouse example.
The extended (freerange?) mouse would keep track of off-screen
movement and forward them to clients. To complete the picture, mouse
clients
> I can't think how Plan 9 would work as a server (as in, the machine
> with the mouse plugged in) for this (either for Synergy or an
> invented-here thing). /dev/mouse doesn't emit when you're off the
> screen. Maybe this is even the reason cinap never did a server, only
> a client.
doesnt matt
