Skip to content

fix(windows): defer mouse motion instead of dropping it - #517

Closed
tdnl wants to merge 3 commits into
feschber:mainfrom
tdnl:fix/windows-capture-deferred-motion
Closed

tdnl wants to merge 3 commits into
feschber:mainfrom
tdnl:fix/windows-capture-deferred-motion

Conversation

@tdnl

@tdnl tdnl commented Sep 29, 2026

Copy link
Copy Markdown

Motion events are deltas, so dropping one when the event channel is full loses that movement. After a lock/unlock this happens constantly and the remote cursor becomes hard to control.

Accumulate unsent motion and send it with the next event.

tdnl and others added 3 commits September 29, 2026 15:52
Motion events are deltas, so dropping one when the event channel is
full loses that movement. After a lock/unlock this happens constantly
and the remote cursor becomes hard to control.

Accumulate unsent motion and send it with the next event.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Logging from the hook thread for every deferred event slows it down.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Logs "[diag] hook:" lines from the Windows mouse hook and "[diag]
service:" lines from the capture loop at debug level, to find where
motion is lost after a Windows lock/unlock. Not meant to be merged.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@tdnl tdnl closed this Sep 30, 2026
@tdnl
tdnl deleted the fix/windows-capture-deferred-motion branch September 30, 2026 10:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant