qmk_configurator VS ckb-next

Handedness? Not sure what do you mean by that. I'm using the config.qmk.fm website for the key configuration

I'm using https://config.qmk.fm/ to create a firmware for Iris rev.7 including mouse keys, and then use QMK toolbox on MacOs to flash the firmware, but while everything else works in all layers, the mouse keys do not move the cursor at all. Any ideas?

How can I use https://config.qmk.fm/ to map certain specific keys such as € or @, that are not direct or available in the framework ?

"documentation": "\"This file is a QMK Configurator export. You can import this at . It can also be used directly with QMK's source code.\n\nTo setup your QMK environment check out the tutorial: \n\nYou can convert this file to a keymap.c using this command: `qmk json2c {keymap}`\n\nYou can compile this keymap using this command: `qmk compile {keymap}`\"\n",

I didn't want to really start another thread because the question I have is so similar I think. I was somehow able to use config.qmk.fm to map a really generic colemak-dh keymap, I read the qmk noob section so I looked up how to use github/git completely lost, I have the Corne 3x6 I didn't build it I purchased it secondhand so Ive been doing some research on ergonomic mapping Miryoku generally seems to be a solid choice

I'd recommend you jump on QMK configurator, select the Charybdis of desired size, and start making your layers 😉

My keyboard was working fine prior to flashing. I have a solderable dz60 (ATMEGA32U4). I tried to flash it with firmware downloaded from config.qmk.fm (selected dz60 as keyboard). It said successful on qmk toolbox, but my caps lock light is stuck on and no button presses work. The esc + plugin option to reset stopped working, so I had to take the pcb out to press the reset button. Still not working after flashing with default firmware downloaded from config.qmk.fm. I tried flashing it with dz60 via firmware, and it gets recognized in via now, but still not working. After hours of troubleshooting of it not working, I flashed it with dz60rgb_v2 just to see what happens, and then very few of the keys work after a few presses (but they're mismapped), and the caps lock light goes off. I've tried the keyboard on different devices, and on both of them it gets recognized as a keyboard, but the caps lock light is still stuck on and no presses register.

Let's suppose that the issue is the diode orientation. I'm a total QMK newbie -- how could I swap between ROW2COL and COL2ROW at the firmware level? On the QMK Github I see instructions for modifying the appropriate headers. But when I generate my config from config.qmk.fm I only get a single .hex file. Thanks again!

Probably the easiest way to do it by clicking buttons is to use config.qmk.fm.

For non-ez keyboards, a similar tool is the QMK Configurator. See this documentation page or the video tutorial for an overview.

EDIT: Realized that one is unmaintainted, so here’s a maintained one: https://github.com/ckb-next/ckb-next

There is unofficial software written for Linux to interact with the corsair keyboards, like the k95. https://github.com/ckb-next/ckb-next

You can control corsair keyboard rgb with https://github.com/ckb-next/ckb-next. Works fine on my ancient strafe keyboard and the assorted corsair mice I've used.

not sure. i use ckb-next which is for linux and only supports corsair devices as i have corsair ram and peripherals. i never really had any luck with openrgb tbh

ckb-next is for Corsair devices, and mostly is for RGB, but does offer mouse button configuration. I use this one with my M65 Elite as it also configures DPI level settings and other items, as well as per-led lighting.

Welcome to open source. Can I interest you in https://github.com/ckb-next/ckb-next ?

If you're on linux https://github.com/ckb-next/ckb-next is really good