The auto-clicker clicks into the password entry box on the remote PC.
That when I connect via computer number 2 via RDP to computer number 1, and launch an auto-clicker that emulates constant keystrokes, the clicks go to the password entry plate in the blocked session, on computer number 1, and on computer number 2 the clicks do not go to the application, although the clicker indicates the binding of the application window.
It feels like the sign prevents clicks on computer number 2 from passing.
Today, I once achieved that computer number 1 did not accept auto-clicker clicks in the password entry frame, the clicker clicked in the RDP window and worked properly. After restarting, the frame prevents pressing again. I do not know how I managed to get around this wrong job 1 time, but I want to ask for help.
Maybe you know how to make the application work for the user who runs it, and not click in the password box in a blocked session on a completely different computer.
