Luke Horwell

Results 365 comments of Luke Horwell

Unfortunately, key mapping on OpenRazer's side has pretty much remained the same since last time. Polychromatic still doesn't have a way to remap mouse buttons or keys. One of the...

Hi, you're welcome -- here I am just the front-end piece to the puzzle. By "binds" I presume you mean the ability to set commands / macros to different keys...

> So, can I remap keys, without GUI? [I was watching your other issue for the answer](https://github.com/terrycain/razer-drivers/issues/259#issuecomment-296959620), but it seems so, but only when the daemon is not running. Sorry,...

Any sort of key remapping functionality is still yet to be implemented in the [OpenRazer](https://GitHub.com/OpenRazer) daemon. Code contributions would be very helpful to them. See https://github.com/openrazer/openrazer/issues/167#issuecomment-274497165.

This "check device compatibility" check reads [this JSON list from OpenRazer's website](https://openrazer.github.io/api/devices.json). I can confirm `1532:0070` is missing, that's a bug. I believe the script that generates that JSON skips...

Makes sense. For the _unrecognised_ mouse, please take a look through [OpenRazer's troubleshooting guide](https://github.com/openrazer/openrazer/wiki/Troubleshooting) - particularly the kernel modules section to check the `razermouse` driver is working. That seems the...

It's possible already by choosing **Edit Metadata** and picking another graphic mapping (or grid), but only if the other device has the same dimensions (rows/columns). If you mean to create...

It would make sense to me to separate the key labels from the layout, since the current mechanism only encourages duplicate graphics with small changes, which will become a maintenance...

Possible, but generating the entire SVG would be impractical since there are non-keyboards too. I did some brainstorming, and this is my plan: ``` - Each graphic becomes a physical...

Thank you, I'm glad you love it! :smile: Mixing lighting effects as a layer system is planned for **v1.0.0**. I got a bit sidetracked when working on this feature (and...