Uh oh!
There was an error while loading. Please reload this page.
wlmouse: high-speed, turbo, angle tune, button combinations, DPI stages, and artwork behind a receiver - #177
Merged
Merged
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>
# Conflicts: # src/app/cards/AdvancedCards.tsx # src/app/cards/availability.ts # src/device/controller.ts # src/device/types.ts # src/ui/device-images.test.ts
…panel Two independent PRs (this one and an earlier control-panel change) each added their own applyAngleTuning export. Kept the version with the hasActiveClient guard and the real degree-symbol label; the other had neither and a literal '00b0' typo instead of '°'. Also bumps @openmouse/protocol to pick up the XM2w 4K v2 identification fix.
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Merge of #162 onto current control-panel, resolving conflicts across App.tsx/controller.ts/types.ts/availability.ts/device-images (additive fields from #163's VXE long-range-mode work) plus a real bug the merge introduced: two independent PRs each added their own
applyAngleTuningexport, causing a duplicate-function build error. Kept the version with thehasActiveClientguard and the real ° symbol; the other had neither and a literal 'oo b0' typo. Closes#162.