Either you are using the Macro Recorder to record your keystrokes, or you manually drag and drop the "Send Keys" action, sometimes you may need to change how fast the keystrokes are sent. WinAutomation provides you with 3 different tools to do that:
1) Set Playback Speed ("Tools - Set Playback Speed" in the Job Designer window): This option allows you to control the playback speed of your recorded macros. You can choose whether you want to execute the actions that you recorded without internal delays or exactly as you recorded them.
Notice that the "Set Playback Speed" option affects all recorded actions (including mouse movements and mouse clicks).
2) Delay Between Keystrokes Option ("Send Keys" action properties, "Delay between keystrokes" input): This option allows you to set a standard delay between all keystrokes in a single "Send Keys" action. For example, in the following action:
there is a delay of 1000 miliseconds (=1 second) between the keystrokes. Practically this means that first, the key "T" will be sent, after 1 second the key "h", after another 1 second the letter "i" and so on.
3) Custom Delay Between Keystrokes: If you want to specify custom delays between various keystrokes in the "Send Keys" action, WinAutomation allows you to do so with a special notation: {Delay delayInMiliseconds}. For example, in the following action:
there is a fixed delay of 1 second between every keystroke, but in addition to that, there is an extra 1 second delay between the "S" and "A" keystrokes. This means that there will be a 2 second delay between the first and the second keystrokes, and a 1 second delay between the rest.
The issue that you are referring to, was a known issue that used to occur in rare cases and has been solved in the latest release of WinAutomation (v 3.0.1.390). Specifically:
- The keystrokes will be now sent correctly regardless of the delay that you add between them.
- The minimum delay that you can set is now 0 down from 10.
- The "Send Keys" action now properly works in Remote Desktop.
- The "Send Keys" action now properly works in the command line window.
- Multiple repetitive keystrokes can be sent in the format {X:n}.
Furthermore, the jobs that have been recorded through the Macro Recorder, will now work properly in every case.
Hi,
Thanks for posting this tip, because sometimes a script could run without any problem in the Job Designer, but when scheduling/running it through the console maybe should be adequate to do some adjustements. I noted some problems when sending some keystrokes to the desired window and concluded that maybe these keystrokes are be sent so fast, for the default value of 30 miliseconds. I adjusted to 50 miliseconds and added the following instruction to the "Text to send" Action box:
{Delay 1000}%Command_to_be_sent%{Enter}
Than, noted that the problem with the first character disappearing not happened more...
Rgds,
Sven
Post new comment