[Performance Issue] Enigo blocks other inputs while clicking about enigo HOT 2 CLOSED

you can ignore the second paragraph, I'm probably going to have to just wait until this is better optimized or something. as i mentioned before, this is directly copy/pasted from my SO post.

from enigo.

Thank you for your report. If you experience any problems with enigo or have other questions, opening issues in this repo is the right place to ask. I don't monitor stackexchange for questions related to enigo.

Regarding your question: Yes, unfortunately this is a known problem. Windows seems to need a delay between the keydown and the keyup event. We have an intentional delay in the code (e.g. here). If you call it many times in a loop, everything afterwards is delayed because we don't enter it in parallel.

A workaround that might work for you could be to call

enigo.mouse_down(MouseButton::Left)
enigo.mouse_up(MouseButton::Left)

in the loop. Those functions intentionally don't have a delay. You probably have to sleep for a couple of milliseconds in between. Otherwise it might not click the expected number of times.

If you want to enter text, it is better to use the key_sequence function. It also has a delay, but it can enter multiple characters at once.

I had a brief look at the code of the python library you mentioned and I can't see a delay there. I have to look more into it to understand how they can avoid it. It would be very welcome if we could get rid of it.

I am closing this for now. We have an issue regarding the delay already: #45

Feel free to reopen the issue, if you have more questions :-)

from enigo.