Hey @pabrams !

This has been on my mind since I started modifying the flashing sequence. We should support way more keyboard shortcuts, but this requires planning, for example:

• Use the shifted F-keys to select the layer (this could also be done with the regular numbers and Ctrl modifier)
• The shifted numbers to select the colors
• Any key without any modifier pressed to change the selected key position in the layout editor
• modifiers won't be inputted this way because they are needed to transform other keys
• any special action like macros, Superkeys, layer changes, Oneshot, etc... won't have shortcuts (or I don't have any in mind that are useful)

The superkey and macro views require their own shortcut schema, and it may be worth it to create a dedicated shortcut for no-key and transparent keycodes.

I also thought about being able to drag & drop a key on another position to swap them, but that should be in another card 😂

What do you think about these changes? Do you have any specific suggestion? Thanks in advance @pabrams !! :)

Hi @AlexDygma , If the hotkeys are fixed, then you definitely have a point about planning, but I think it's preferable to tackle this in smallish chunks, prioritized by current level of pain. So what about allowing all hotkeys to be configurable (via json - I strongly suggest not to implement UI for this, at least not yet), and then the planning becomes less important, and that gives us the freedom to start implimenting one piece at a time? I can see that you've already put a lot of thought into having the hotkeys set up just right, but remember it doesn't have to be perfect. If we tackle the low-hanging fruit, first, hopefully we can eliminate a large amount of pain with a minimum amount of effort.
I probably have more specific suggestions, but have no time at the moment. Will circle back when time permits.

Hi @AlexDygma , If the hotkeys are fixed, then you definitely have a point about planning, but I think it's preferable to tackle this in smallish chunks, prioritized by current level of pain. So what about allowing all hotkeys to be configurable (via json - I strongly suggest not to implement UI for this, at least not yet), and then the planning becomes less important, and that gives us the freedom to start implimenting one piece at a time? I can see that you've already put a lot of thought into having the hotkeys set up just right, but remember it doesn't have to be perfect. If we tackle the low-hanging fruit, first, hopefully we can eliminate a large amount of pain with a minimum amount of effort. I probably have more specific suggestions, but have no time at the moment. Will circle back when time permits.

This is in fact the best way to go forward with this until we identify good presets for the keys, they can be even disabled until toggled in preferences, then the JSON file is read when using the different editors.

Thanks for the heads-up @pabrams! this proposal makes it simpler to tackle this problem in an incremental way, ill create a dev branch and start a PR to follow the dev process.