Repository navigation
Add a radar speed setting for Mouse scanning - #1070
Merged
Merged
Conversation
The radar turned and grew at the point-scan Line speed, so it could not be made faster or slower on its own. Mouse scanning now has a Radar speed on the same five steps. It is saved as radarSpeed; null, as in settings saved before it existed, follows Line speed, and Follow line speed returns to that. Synced settings move to schema 4 for the new field. Version 1-3 documents read with the radar following Line speed, and older builds ask to be updated rather than overwrite a version 4 document. Closes #1069 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Follow line speed moves focus to the chosen radar speed rather than dropping it when the button goes. The radar note keeps the same text and adds that it follows Line speed only while it does, and Line speed says the radar follows it. A workflow test checks the radar moves at its own speed, or else at Line speed, and the docs note that Faster and Slower lines change the radar only while it follows Line speed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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 #1069
Summary
radarSpeed.null(and local settings files saved before this change, which lack the field) follows Line speed, so existing behaviour is unchanged. Follow line speed returns to that.radarSpeed: null; older builds report "Update Switchify PC" instead of overwriting a version 4 document (the same path as the schema 3 move for row groups).docs/point-scan.mdupdated, including that Faster/Slower lines affect the radar only while it follows Line speed.Compatibility
radarSpeed→None→ follows Line speed (radar_speed_follows_line_speed_until_chosen).radarSpeed, or a version 4 document missing it, is rejected; a version 3 merge base still loads (version_three_documents_read_with_the_radar_following_line_speed, plus the existingupdating_from_an_older_version_uploads_nothing_until_a_changeloop now covering 1..4).Validation
Node 24.19.0, rustc 1.97.1:
npm run prediction-model✅npm run lint✅npm test✅ 296 passednpm run build✅cargo fmt --check✅cargo clippy --all-targets -- -D warnings✅cargo test✅ 782 passed, 5 ignoredIndependent agent review at 56e759b (no bugs; focus, test and wording findings fixed in 2e73107) and re-review at 2e73107 (nothing actionable).
Not yet tried by hand in the running app.
🤖 Generated with Claude Code