Skip to content

Fix Razer keyboard LED mappings#254

Merged
DarthAffe merged 4 commits intoDarthAffe:Developmentfrom
logicallysynced:Development
Feb 22, 2022
Merged

Fix Razer keyboard LED mappings#254
DarthAffe merged 4 commits intoDarthAffe:Developmentfrom
logicallysynced:Development

Conversation

@logicallysynced
Copy link
Contributor

This PR fixes the issue described in #253.

According to Razer's official documentation found here, Razer keyboards use a single mapping layout for all keyboard devices, regardless of if keys exist on the physical device or not.

RGB.NET has implemented multiple definitions to match with the physical layout of different types of keyboards (normal, laptop and blackwidow) which is actually offsets the keys on these devices, due to them all using the same layout. This PR removes those extra definitions and keeps the standard definition, which should work for all Razer keyboards.

I have tested this PR on the following types of Razer devices and confirmed this works:

  • Razer Blade 15 (Physical/Laptop)
  • Razer Blackwidow Chroma (Physical)
  • Razer Huntsman Elite (Virtual)

Note: sorry for the double commit of LedMappings.cs, I accidently wrote RazerDeviceProvider.cs over it, so needed to revert it.

@DarthAffe DarthAffe merged commit 35cf0a3 into DarthAffe:Development Feb 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants