Repository navigation
Expand pointer speed range for Mouse and Remote - #863
Merged
Merged
Conversation
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
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.
Closes #862.
Expand the shared saved pointer speed from 5–225% to 5–1350% in 5% steps. Existing values, including 100%, keep their movement and acceleration behavior. The maximum yields about 648 pixels per second for Mouse's medium movement at the default 250 ms interval, reaching full speed after the configured ramp.
Validation on Node 24.19.0 and Rust 1.97.1:
npm run lint,npm test(219 UI, 5 Node),npm run buildpass.cargo fmt --check,cargo clippy --all-targets -- -D warnings,cargo test(521 unit, 1 ignored, 7 integration) pass.1917c07as a native ARM64 debug app in the running Windows 11 Parallels VM. With temporary F9/Space/Enter switch assignments, 1350% speed, 250 ms interval and acceleration off, Mouse opened, selected a direction, repeated movement, and stopped on the next switch press. A timed two-second move covered 656 DPI-virtualized cursor units; at the VM's 200% display scaling that is about 1312 physical pixels, matching the ~648 physical pixels/second target. The cursor stayed still after stopping. The original 225% speed and switch/Point preferences were restored, and the PR build was left running. Switch events were generated in the VM; no physical switch hardware was available for this check.1917c07found no actionable findings.