Hello,
I'm new to AutoIt programming language and I'm writing some photographs computation program with it.
I chose AutoIt because this program needs to get various data from other programs that I can't drive in other ways than keyboards/mouse events programming.
At the time, result is good, but this application is not robust at all : when program is running, mouse pointer is moving on the screen, keyboard inputs are auto-typed and so on, but execution falls in no man's land when program is disturbed by some other OS driven event (another program pop-up, firewall warning, ...), that steals focus to active window.
So I'm thinking of 2 solutions to solve this :
1/ have a thread that protect the program active window focus to be lost (that means that I can't do no other action on my computer when program is running).
2/ putting the program alone in some virtual machine, that would have independent keyboard, mouse and focus events (that's maybe not possible).
More generally, I get other problems caused by overall system/OS health : sometimes, computer is slowing down a little, so that some events that I send to OS applications aren't well-executed, even if I use timing operations (WinWaitActive(), Sleep(), ...).
This problematic is so present in AutoIt event programming that I would be surprised if no other topic yet deal with it. Unfortunately, my english is not so good, and I can't find really good related posts using the forum search function.
Just for fun, and I hope it will be understood as a compliment, I held AutoIt as :
- great work for the team which builds this tool, since it must not be easy to allow those special interactions with Windows OS.
- great path to get results nearly unreachable with other programming ways.
- weak applications building, since events are too much OS/system state dependent (timing problems).
- baby coding
Finally, yeah, AutoIt is very cool stuff
Hope you can give me some piece of information or point me to related topics, see you.
