Keyboard tweak help : hitting 2nd key stops 1st typed (hold hit)

[bruce741]

So Guys , am runnig a project using led keyboard lights
Am using the Acer 6312 Mechanical Keyboard : Acer keystwitches/membrane/intel chip

when i keep pressing a 1st key for example "a" it's obvious that the typing result is : aaaaaaaaaaaa-> continuously
But when i hit a second Key ( for once z for example) , the typing  stops.
This doesn't happen when using a usb keyboard (HP wireless) the typing result is : aaaaaaaaaaaazaaaaaaaaaaa->
i mean , typing result is multiple a then z (once) and back to the a key am keeping pressed.


I tested my keyboard with Keyboard Tester , i found out that my keyboard is 2/3/4 KR depending on positions.
But as a fact , for my previous example, the tester shows a good detection , but typing doesn't follow
on keyboard tester interface , the 1st  key is kept pressed even after pressing the 2nd one , but doesn't type it.

Hope i made my idea clear, Is there anyway to change this thing  so that my Acer6312 acts like the usb one for revert typing on the 1st key

[laffindude]

I just tested 5 keyboards (happened to be sitting on the desk), and they all stops repeating once you hit another key. If you hold the 2nd key, it'll repeat that.

I think the HP wireless is the one doing the incorrect repeat behavior.

Also. KRO is the MINIMUM number needed to cause a conflict -1. So it is a 2KRO keyboard.

[bruce741]

Thanks for the answer laffindude

So is it because of the USB not ps/2 , or because of the controller ?
i donno , i really need to find out where this setting can be changed. (regedit maybe ..)

My project is based on light on/off but without altering/stopping the tapping activity.


PLZ GUYS if anyone know something about this let me know.

[alaricljs]

In the case of the HP board it's not a setting, it's the way in which the keyboard itself behaves.  The HP wireless bits do things a bit differently and you are not likely to find a hard-wired KB that does the same thing.  The keyboard is re-signalling the A key-down event which is not a normal behavior.  There is even the possibility that they chose to do all the key repeat inside the board because of it being wireless.  This would mean the keyboard is repeatedly sending key-down/key-up pairs as long as you hold a key.  Normally the key-repeat happens in the PC side as it only gets a key-down event and then does whatever it's supposed to with it, whether it be auto-repeat characters or strafe left in an fps.

On the other hand, if you are determining your key detection by looking for letters to appear then you are doing it wrong.  In the resources thread you can find AKT which will show you that even tho letters are not coming out the system knows that the A key is still pressed.  You should be looking for key-down/key-up events, not letters.  If what you want to do requires the computer to spit out letters, then good luck figuring out a work around.  It would require you to write a keyboard driver.

On second thought you could write an AHK script to do it.  I don't know if or how well it would work, but you can intercept key-down events and have a timer repeatedly send key-down/key-up events to the application.  I have no idea if it's possible to deal with simultaneous key presses this way, but it's something for you to investigate.

[bruce741]

thx alaricljs for the good advice.