Hi Peter. First: thanks for 8.2
You were kind enough to help get the 18 âGâ keys going on my Corsair keyboard, but a firmware update pretty much messed it up. Since then, while I could use the G-keys, it was odd. (So odd, that I bought another keyboard, and used a third-party device for my macros.) But today, on a whim, I thought Iâd try it with KM 8.2.
Let me explain âoddâ - letâs say I assign G9 to a simple âpasteâ macro. If I single tap G9, it works. If I tap 2 times, it works; but after the 3rd tap, the key quits functioning (being recognized?) for up to 40 seconds. Or, if I tap G1, G2, G3⌠the whole G-key keypad goes away for 40 seconds.
Not suitable for quick, repeated use of macros via the G-Keys.
Hereâs what I discovered today, however, and it seems an important clue: if I follow a G-key tap with a tap on -any- key thatâs NOT on the keypad, the 40-second wait goes away. I could to 20 pastes in a row, for example, by tapping:
G9
shift
G9
shift
g9
shift⌠etc
So, I created a macro with was âpasteâ âshiftâ (using type a modifier)⌠and it worked!
I cannot tap as fast as a simple command-v will allow, but the 3-limit, 40-second delay is gone.
Iâm sharing this for two reasons:
First, in case it gives you an âAha! Momentâ and an idea how to fix it.
and Second: for the benefit of any other Corsair users who have experienced the same thing.
Iâm going to yank my ânewâ setup (new keyboard/and external keypad) and return to my beloved keyboard with the g-keys. All I need to do is add the type-a-modifier-key to each of the assigned short cuts, and Iâm back to work.
FWIW, and YMMV