Replies: 2 comments 1 reply
-
|
It's right. m16 and m18 have completely different keyboard, so it's not compatible. m16 have detection profile defined by me (i have this gear), but m18 doesn't have it yet. You can define it yourself using manual detection and share for other owners. You can also remove old mappings from m16 - go "Devices" tab, select inactive keyboard device, press "Clear device" button. Furthermore, you can also back up your settings before this using |
Beta Was this translation helpful? Give feedback.
-
|
This comment was edited from the original, and I think this is "complete." Does this work? I expanded the Tron's by two columns due to the size difference with m16 R1, but I am not sure if Dell had to actually put in more zones. I suspect they did to keep the Tron's to have consistent brightness between size versions. |
Beta Was this translation helpful? Give feedback.
-
|
@T-Troll , I appreciate your work even more. Your approach to "escaping" is pretty cool. I actually thought the line below was incorrect, but actually it is escaping the line so the comma is recognized as a comma character, and not a actual column in the CSV.
--snip-- So I think there is no problem found. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I basically moved my boot drive to my new to me m18 R1 i9-13900HX with Cherry MX Keyboard, but it seems that the key lights are from the previous AWCC. I tried to detect, and when I had the m16, it showed m16, but now it doesn't detect.
I still have the keymapping from the m16 in the tool, but how to apply it?
Beta Was this translation helpful? Give feedback.
All reactions