Skip to content

Fix the mouse polling test: read only the raw input header - #19

Merged
PrimeBuild-pc merged 1 commit into
mainfrom
fix/mouse-polling-test
Oct 13, 2026
Merged

PrimeBuild-pc merged 1 commit into
mainfrom
fix/mouse-polling-test

Conversation

@PrimeBuild-pc

Copy link
Copy Markdown
Owner

The mouse polling test in Devices & latency → USB and input always ended with "Not enough movement was captured".

GetRawInputData was called with RID_INPUT and a buffer the size of RAWINPUTHEADER (24 bytes on x64). A mouse RAWINPUT is 48 bytes, so every call returned -1 and no sample was recorded. RID_HEADER reads only the header, which is all the test needs (type and device handle).

Checked with a standalone probe that registers raw input and injects 20 mouse moves: RID_INPUT failed on 27/27 messages, RID_HEADER succeeded on 27/27.

Build OK, 247/247 tests.

@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

GetRawInputData was called with RID_INPUT and a buffer sized for the header
alone; a mouse RAWINPUT is 48 bytes, so every call failed and the test always
reported too little movement. RID_HEADER reads the 24-byte header it needs.
@PrimeBuild-pc
PrimeBuild-pc merged commit d67c7c3 into main Oct 13, 2026
1 check passed
@PrimeBuild-pc
PrimeBuild-pc deleted the fix/mouse-polling-test branch October 13, 2026 21:34
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