Conversation
KEYBOARD_KEY_CIDS only had 0x010a for ButtonId::KeyScreenCapture — the Signature-series CID. The MX Keys for Mac (046d:b361) reports the same function under a different control, 0x00bf (Solaar's Screen_Capture__Print_Screen), so a KeyScreenCapture binding on that keyboard was never diverted: the CID it actually needed wasn't in the table at all. Added the second (cid, ButtonId) pair alongside the existing one. Only one of the two is ever present on a given keyboard's control table — arm_keys already skips whichever CID the connected device doesn't report — so both entries coexist safely, the same pattern already used for the gesture button's multiple physical CIDs. Fixes AprilNEA#1254
|
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.
Summary
KEYBOARD_KEY_CIDS(crates/openlogi-device/src/session/keyboard.rs) only had0x010amapped toButtonId::KeyScreenCapture— the Signature-series CID. The MX Keys for Mac (046d:b361) reports the same physical function under a different control,0x00bf(Solaar'sScreen_Capture__Print_Screen), so aKeyScreenCapturebinding on that keyboard was never diverted — the reporter confirmed viaopenlogi diag controlsthat0x00bfis present and divertable, and via agent logs that nocaptured controlevent ever fired for it.(0x00bf, ButtonId::KeyScreenCapture)as a second entry. Only one of the two CIDs is ever present on a given keyboard's control table —arm_keysalready skips whichever CID the connected device doesn't report ("Missing or non-divertable controls are skipped so support degrades per key") — so both entries coexist safely. This mirrors the same multi-CID-per-ButtonIdpattern already used for the gesture button (GESTURE_SOURCE_BUTTONS'0x00c3/0x00d7/0x00d0).Changes
crates/openlogi-device/src/session/keyboard.rs: added the CID entry, with a comment explaining why the duplicate mapping is safe. Added a unit test asserting both CIDs resolve toKeyScreenCapture.Testing
cargo fmt --all -- --checkcargo clippy -p openlogi-device -p openlogi-agent -p openlogi-cli -p openlogi -p openlogi-hid -p openlogi-agent-core -p openlogi-desktop --all-targets -- -D warningscargo test -p openlogi-device -p openlogi-agent -p openlogi-cli -p openlogi -p openlogi-hid -p openlogi-agent-core -p openlogi-desktopopenlogi diag controlsoutput confirmed, cross-checked against Solaar'sspecial_keys.pyreference.Fixes #1254