feat(linux/input): optional absolute mouse as relative motion - #5529
Open
danalec wants to merge 1 commit into
Open
feat(linux/input): optional absolute mouse as relative motion#5529danalec wants to merge 1 commit into
danalec wants to merge 1 commit into
Conversation
danalec
changed the title
Member
|
@danalec It won't pass until I approve the workflows. Anyway... Thank you for the PR submission, but it looks like you used AI to create this PR. Please read and follow our Contributing guidelines and specifically our AI Usage policy. Additionally, please update the PR to use the correct template. You can find it at https://github.com/LizardByte/.github/blob/master/.github/pull_request_template.md?plain=1 |
ReenigneArcher
added
the
ai
danalec
force-pushed
the
pr/abs-mouse-relative
branch
from
August 21, 2026 01:10
7fc91f8 to
25164e4
Compare
Contributor
|
This might also fix absolute touch input on KDE in a multi-monitor scenario as that currently sends the touch events to a fixed monitor (configurable in systemsettings) instead of selecting the correct monitor by absolute coordinates. |
danalec
force-pushed
the
pr/abs-mouse-relative
branch
2 times, most recently
from
August 26, 2026 03:02
639fe89 to
822ee0e
Compare
danalec
changed the title
danalec
force-pushed
the
pr/abs-mouse-relative
branch
4 times, most recently
from
August 26, 2026 04:48
808857e to
c4bbe39
Compare
Some compositors implement assistive features that only track relative pointer motion; Wayland's PointerMotionAbsolute moves the cursor but such features do not follow it (e.g. the COSMIC screen magnifier focal point, pop-os/cosmic-comp#2760). Add an absolute_mouse_as_relative option (disabled by default) that converts absolute client coordinates into relative deltas. The first absolute event still anchors the cursor absolutely. Subsequent events are turned into relative deltas driven by dead reckoning. The KMS capture path publishes the real cursor-plane position every frame; the estimate snaps to it while the client is idle, and a coordinate saturated at the client's own surface edge targets the matching host edge so movement cannot stall mid-screen. On backends without cursor feedback the conversion still works from dead reckoning alone.
danalec
force-pushed
the
pr/abs-mouse-relative
branch
from
August 27, 2026 18:09
c4bbe39 to
5787155
Compare
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Moonlight TV clients (and other absolute-motion sources) send absolute mouse
positions. The Linux backend forwards them as absolute uinput events, which
compositors treat as absolute pointer motion.
COSMIC's magnifier does not track the cursor on absolute motion:
PointerMotionAbsolutemoves the cursor but never callsupdate_focal_point(pop-os/cosmic-comp#2760; same symptom class as #1418/VirtualBox). Relative
motion updates the zoom on every event.
This adds an
absolute_mouse_as_relativeoption (disabled by default) thatconverts absolute client coordinates into relative deltas:
baseline.
cursor arrives at the compositor as relative pointer motion.
internal estimate snaps to it while the client is idle, and a coordinate
saturated at the client's own surface edge targets the matching host edge,
so movement cannot stall mid-screen. On backends without cursor feedback
the conversion works from dead reckoning alone.
Documented in
docs/configuration.md.Screenshot
Issues Fixed or Closed
Roadmap Issues
Type of Change
Checklist
AI Usage