Quote:
|
The problem was that i needed the x button to be pressed with the smallest break possible after pressing the z button.
|
I am confused as to what you meant. I just performed a benchmark on this program, and it emulated the key press 'x' 5 times in less than 1/4 of a second ( 0.212 seconds was my fastest time with it ). That seems rather fast to me, as that's roughly 16-22 key presses a second being emulated. If it needs to be faster, there might be a way to trim it down a few milliseconds, but it still won't fall under 0.150 seconds from what I can imagine.
Quote:
|
x and after a couple of milliseconds another x
|
It sounds like you were wanting it to be even quicker in emulating the 5 key presses to perhaps less than 0.050 seconds. I don't think this can be done, as it takes a certain amount of time to take an event from the Windows events stack, process what to do with it, and send the 5 emulated key pressed back to Windows to be performed. This would be up to the speed of your processor, which mine is currently not the best in the world by far. The speed isn't capped, so if you can get it to perform quicker on your system then that will solve that issue.
Quote:
|
What that program does is it just pastes xx instead of x and after a couple of milliseconds another x
|
By 'pastes', do you mean that it sends the literal character value for 'x' instead of the key press of 'x'? Both can be done, but this program specifically emulates the key press of 'x' instead of sending the character 'x' to Windows applications. If you're not wanting the program to emulate the key presses one right after another and instead have delay between each key press, that can be done.
Example:
*Key Press 'X' is sent*
-DELAY 0.100 SECONDS-
*Key Press 'X' is sent*
-DELAY 0.100 SECONDS-
*Key Press 'X' is sent*
-DELAY 0.100 SECONDS-
*Key Press 'X' is sent*
-DELAY 0.100 SECONDS-
*Key Press 'X' is sent*
The time of delay can be whatever you need though, that's just an example.
.
