You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As you may know, QMK supports layouts, which allows for the same layout to be applied to multiple keyboards, without the need to configure each keyboard x keymap individually.
Looking at the default layouts, for example, we can in theory apply LAYOUT_split_3x5_3 to Keyball39.
Having this feature would unlock many of the existing keymapping for keyball keyboards.
I am going to have a look at this myself (although I don't have much QMK knowledge yet) but I thought I would also raise it as an issue if someone has already done the work or wants to collaborate.
The text was updated successfully, but these errors were encountered:
unlock many of the existing keymapping for keyball keyboards
I believe that Keyball loses most of its value without KC_BTN{n} and unique key codes in the keymap.
So I don't understand the benefit of being able to use keymaps from other keyboards.
If you know of a specific example of another keyboard keymap that would be meaningful to use with Keyball, please let me know.
As you may know, QMK supports layouts, which allows for the same layout to be applied to multiple keyboards, without the need to configure each keyboard x keymap individually.
Looking at the default layouts, for example, we can in theory apply
LAYOUT_split_3x5_3
to Keyball39.Having this feature would unlock many of the existing keymapping for keyball keyboards.
I am going to have a look at this myself (although I don't have much QMK knowledge yet) but I thought I would also raise it as an issue if someone has already done the work or wants to collaborate.
The text was updated successfully, but these errors were encountered: