mirror of
https://github.com/feschber/lan-mouse.git
synced 2026-05-15 14:15:52 -06:00
[GH-ISSUE #313] [MacOS][Feature Request] Support Universal Control devices associated with the target MacOS device #162
Labels
No labels
Xorg
documentation
enhancement
macos
pull-request
question
windows
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/lan-mouse#162
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @johnhamelink on GitHub (Jul 25, 2025).
Original GitHub issue: https://github.com/feschber/lan-mouse/issues/313
Hi there,
I wonder how feasible it would be to allow lan-mouse to extend the bounds of control to devices connected via the Universal Control feature of MacOS...
For context, I hack on iPad apps at work as part of my job, and it'd nice to be able to use my mouse and keyboard to control the iPad without having to reach over to physically hold the iPad.
I have three devices: a Linux laptop on the left with a mouse & keyboard attached, a MacBook Pro in the middle, and an iPad to the right. When I use the MacBook's mouse and keyboard, I can use lan-mouse to control the Linux machine, and I can control the iPad with Universal Control. But I don't want to use the MacBook to do this, I just want to use my Linux machine's mouse and keyboard for everything :)
Can lan-mouse work with multi-display target systems currently? And how feasible might it be for lan-mouse's input to be forwardable to the Universal Control system on MacOS, such that I can use my Linux machine to control the iPad via the MacOS target I'm connected to?
In the meantime, I'll reluctantly plug my peripherals into the MacBook 😄
Thanks!
@feschber commented on GitHub (Oct 29, 2025):
I think this would work, if I emulate input via driver kit as virtual devices instead of the accessibility API (which is how it is currently done)