Files
hyprland-headless-stream-pl…/src/hhstream_pointer/__init__.py
T
HermenixandClaude Opus 5 0d414d76bc pointer: the lease, and a driver process that only executes
There is one cursor on this compositor build and every virtual pointer
writes to it, so aiming at a session is a matter of serialising input, not
of binding harder. Two pieces, and the split between them is the point.

`hhstreamd/pointer.py` is the lease: one holder, an idle TTL and a hard cap
on an injected clock, tracked buttons, and the window-local-to-normalised
arithmetic that makes "click 40px into this window" mean something on an
output that is not at the layout origin. Pure, so the expiry tests move
time instead of sleeping.

`hhstream_pointer/` is the driver: its own process because a Wayland client
needs its own connection and a blocked one must not stall the broker. It
holds no lease state -- it is told what to do and does it. The manager is
bound at version 2 and pointers are created with
`create_virtual_pointer_with_output`; a version-1-only manager is reported
and refused rather than quietly aiming at the global layout.

The wlr protocol module is vendored scanner output under `_protocol/`, so a
checkout builds without a code generator; `_protocol/regenerate.py` says how
to refresh it and why pywayland's own scanner entry point cannot be used.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011txKimbdkqPFpq6m8KDELu
2026-10-02 00:15:50 +00:00

14 lines
687 B
Python

"""The pointer driver: a Wayland client that moves one cursor on command.
Its own process, for two reasons that are not negotiable. A Wayland client
needs its own connection to the compositor, and the broker is not one. And a
Wayland round-trip can block indefinitely — on a compositor that is busy, or
wedged — so running it inside the broker would let a stuck cursor stall every
other session's lifecycle.
It holds **no lease state**. It is told what to do and does it; the broker owns
the lease. See ``docs/CONTRACT-sessions.md`` §3.4. A driver that could be
trusted to serialise would eventually be trusted to, and there is exactly one
cursor to get that wrong with.
"""