wlmouse: high-speed, turbo, angle tune, button combinations, DPI stages, and artwork behind a receiver - #162
Open
ydw1904 wants to merge 2 commits into
Open
Conversation
The driver now reads four per-profile sensor settings from WLmouse mice, so the Processing card can offer them. Three are switches beside the ones already there; angle tune reuses the same -30..+30 select Pulsar Pro has, shown for any mouse that reports the field and left in the Pro card for Pulsar so it is not offered twice. Turbo is greyed out while high-speed mode is off, which is the firmware's own rule: it will not hold turbo on without it. The shared hyper-mode switch reads "High-speed mode" for WLMouse, the name their own tool uses, and stays "Hyper mode" elsewhere. Artwork resolves by name for WLmouse now. The shared 1K receiver enumerates under one product id whatever mouse is on it, so keying art by product id could never work for those; the driver reads the paired model and the name fallbacks pick up the render. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The driver now reports `dpiStages` and the `dpiStageEditor` hint, so the preview should show the stage list too — otherwise the one fixture for this family renders a card the real mouse no longer matches. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
ydw1904
changed the title
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
1 participant
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.
App side of OpenMouse-Project/mouse-protocol#52, which teaches the WLmouse
driver four sensor settings, the mouse behind a shared receiver, and the full
DPI stage table. Needs that PR merged and the protocol dependency bumped
before it typechecks.
Processing card
Three new switches beside the ones already there, plus angle tune reusing the
same -30..+30 select Pulsar Pro has — shown for any mouse that reports the
field, and left in the Pro card for Pulsar so it is not offered twice.
Turbo is greyed out while high-speed mode is off, which is the firmware's own
rule: it will not hold turbo on without it. The shared hyper-mode switch reads
"High-speed mode" for WLMouse, the name their own tool uses, and stays "Hyper
mode" elsewhere.
Artwork behind a shared receiver
The 1K receiver enumerates under one product id whatever mouse is paired with
it, so keying art by product id could never work for those — every one of them
came up as the generic placeholder. The driver now reads the paired model, so
this adds the name fallbacks that pick up the render.
Preview fixture
The
?preview=wlmousefixture gains the new fields and a DPI stage table, sothe one WLmouse device the app can render without hardware matches what the
real mouse now reports.
Testing
npm run buildclean and 114 tests passing, against a local build ofmouse-protocol#52.
the four settings all confirmed in the running app.
🤖 Generated with Claude Code