implement {DELAY=X} in autotype

[jmper]

{DELAY=X} sequence inserts Xms delay between each character during
autotype

[nmschulte]

KeePassX already supports this feature, with a nearly identical syntax:

{DELAY X} -- no =, and X is in milliseconds.

Ah, I see that your syntax (with =) is a different feature:
https://www.keepassx.org/dev/issues/296

[jmper]

{DELAY X} and {DELAY=X} are different. {DELAY X} only inserts delay before autotyping the entire string. {DELAY=X} (which I added) enables entering delays between every character that is being autotyped. This is useful on sites which do some JS processing of entered characters and KeePassX is too fast for them.
Both DELAY features were meant to be compatible with original KeePass (and KeePassX 0.x), but so far only the first one was implemented.

[arigit]

this is awesome news jmper, thank you for this. This was needed for true compatibility with Keepass, I have one particular site where this is needed and I found the missing support the hard way.

[arigit]

p.s. I'm surpised there are 50+ PRs pending review by the devs dating back 9 months ago.
Hoping that this one can be merged soon :|

[nmschulte]

p.s. I'm surpised there are 50+ PRs pending review by the devs dating back 9 months ago.
Hoping that this one can be merged soon :|

There was a recent commit to the repo, so hopefully development will pick up again. If not, I'll probably implement a fix for global auto-type prompting to unlock the DB, or revert back to < v2.0.

[george-viaud]

This is much needed - I'm running into problems (likely due to plugins in my browser) that are causing the browser to "miss" autotyped characters ~50% of the time which is unfun. I suspect additional delay would fix this

[george-viaud]

Working great - thanks!

Suggest a sequence similar to:

{DELAY=15}{DELAY 200}{USERNAME}{DELAY 100}{TAB}{DELAY 100}{PASSWORD}

[george-viaud]

@jmper would you consider please making this pull request also on fork:

https://github.com/keepassxreboot/keepassxc

It appears they've either missed it or perhaps haven't put it in their main branch yet (not sure how to check)

Many thanks

---

EDIT

Thanks @jmper - looks like your PR got implemented there - very good indeed!