jeudi 3 avril 2014

K95 problem with pressing two G key concurently

Hello



I'm encountering a problem when trying to program G keys to do continuous playback.

What I'd like to do is to have G keyboard keys (linked to in-game commands) continuously send a specific keycode when pressed and kept pressed.

(user case: in WoW, press an action key while user commands are in global cooldown, so that the command fire the instant the GCD is over)



Setup:



I use the K95 keyborad configuration software. I set it up for "hardware playback" ("software playback" is not suited for what I want to do, but that's beyond the point I want to outline).



I create two macros (with numbers 1 and 2) like the one below:

(1) down

0.050 seconds delay

(1) up



I assign each macro to a different G key (say G1 and G2).

For each key, I select the continuous playback option (ie it should repeat the macro over and over again) with a delay of 0.050 seconds.



When I use press both key independantly, things works as expected: I get either a long strings of 1 or a long strings of 2.



Problem:



The problem arises when I press both G keys either simultaneuosly or one after the other in rapid succession.



Specific case: I press G1, while G1 is pressed I press G2, wait a little and then depress G1 while keeping G2 pressed.

I would expect a long string of 1 followed by a long string of 2 that keeps going even after I depress G1. (like 1111111111111111222222222222222222)



The result I get is that everything stops the moment I depress G1. Even though G2 is still pressed no "2" is registered. (11111111122 it stops when I depress G1 but with G2 still pressed).



It work as if the action "keydepress" is generic (the same for all G keys) and stop whatever macros are running (even if it is not attached to the key being depressed).



Note: using autohotkey to do something similar on another keyboard (or directly on the K95 on the numeric pads) works as I expect (one key depress do not stop the macro of the remaining pressed key).





Questions:



Is this the expected behaviour or is it an "undocumented feature"?



Any suggestion of what I would be doing wrong? Or any work around?





TY in advance




Aucun commentaire:

Enregistrer un commentaire