Mouse map manual override

Open
#1,145 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
frontend

Research direction

No files or tests are named. Start by locating TinyPilot's mouse-coordinate mapping and the existing reported-screen-resolution handling; determine where a user-supplied remote screen size would be configured. Done means users can provide a different screen size and the mouse position is mapped to the target cursor accordingly.

Written by the indexing model from the issue text.

Description

enhancement

Some users have found that their TinyPilot mouse does not have the same position as their target machine's mouse cursor. And the offset isn't fixed either. This suggests that the screen's reported resolution and the resolution being used by the mouse are different. i.e., the screen may output at 720p, but the mouse is working with the assumption that the resolution is 1080p for some reason.

Can we give users a way to tell TinyPilot that the remote screen is actually a different size than the device is reporting and map the mouse accordingly?

Dominant language
Python
Stars
3.5k
Forks
291
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from tiny-pilot/tinypilot

All issues in tiny-pilot/tinypilot

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.