Yes this makes sense. I would like to see fields added to the action so you can set the delay to
be between X and Y. All emulations would be different and random within those delay times then.
Also anyone that uses one keyword emulation action for filling out several fields in one action could do with this feature:
The ability to use a {-Keystrokes.Delay-} variable.
Wouldn't it be cool if you could have a action like this:
{-Keystrokes.150-}username{TAB}{-Keystrokes.75-}email{TAB}{-Keystrokes.250-}password{TAB}{-Keystrokes.300-}confirmPassword
That way all fields would be using different emulation delays and if you wanted to you could use a
macro to generate a random number between X and Y and use that as the delay value.