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
Is there a way to map two simultaneous key presses to another key?
E.g. Simultaneously pressing 'Q' and 'W' would be mapped to '~'.
The idea is to use such simultaneous-combos to avoid difficult finger stretches or to trigger specific macros/functionalities.
Clearly, finger stretches and macros can be triggered with non-simultaneous combos or through layers, but it seems my brain has a lot more ease with this notion of simultaneous-combos than more layers (at least for the moment).
Some other examples that I have seen mentioned include:
'A' and 'S' for 'CTRL' (instead of a homerow mod)
'P' and '[' for ''
'Z' and 'X' for 'CTRL + 'Z' (undo)
'X' and 'C' for 'CTRL' + 'C' (copy)
'X' and 'V' for 'CTRL' + 'V' (paste)
'A' and 'F' for 'ESCAPE'
Many thanks for any ideas on how to create such a behavior using the current Bazecor capabilities or information on whether such a feature has been considered/planned.
The text was updated successfully, but these errors were encountered:
I'm currently experimenting with Kanata[1] to get this functionality. Current results look very promising, although I agree it would be awesome if we had direct support to chords (I think that's the technical name to call this kind of key convinations).
Is there a way to map two simultaneous key presses to another key?
E.g. Simultaneously pressing 'Q' and 'W' would be mapped to '~'.
The idea is to use such simultaneous-combos to avoid difficult finger stretches or to trigger specific macros/functionalities.
Clearly, finger stretches and macros can be triggered with non-simultaneous combos or through layers, but it seems my brain has a lot more ease with this notion of simultaneous-combos than more layers (at least for the moment).
Some other examples that I have seen mentioned include:
Many thanks for any ideas on how to create such a behavior using the current Bazecor capabilities or information on whether such a feature has been considered/planned.
The text was updated successfully, but these errors were encountered: