Making Qukeys more friendly?

Hello. Isn’t it possible to make Qukeys more friendly, especially in not having to refer to the row and column as numbers when declaring them? Something like the Macro/TapDance way of declaring them as part of the keymap and later describing the relevant options in a separate function would be much more convenient. Or is this difficult because Qukeys works at a much lower level?

It’s possible, but I haven’t had much time to write code since Kaleidoscope-Qukeys got moved to the keyboardio organization and became “official”. Preprocessor macros could probably make it somewhat better, but the best way would be to add a range in Kaleidoscope-Ranges and do significant restructuring of the plugin, which I definitely don’t have time for (I could possibly do it sometime in August, but not before then).

2 Likes