Here's a trivial exemple of some simple computation going awry.
The implementation language is mostly irrelevant (here, AutoIt) as you'd get about the same thing with C and the vast majority of languages.
Is there a way to have Aut2Exe write its error messages to the console (stdout/stderr) instead of popping up a message window?
We build our project software using Bash scripts that compile AutoIt scripts, compile C programs, install data files, etc. If Aut2Exe encounters an error when compiling an AutoIt script it pops-up a message window, which is problematic when running from a Bash script. It's worse when part or all of the build is executed remotely via SSH: if you're watching the build, you can kill the local script if it gets stuck (i.e., is waiting for Aut2Exe to exit), but the Aut2Exe process is still running on the remote machine and has to be killed there.
A local Aut2Exe already exits with a non-zero status once the window is closed (which is only a minor problem; see below). The big snag is the remote processing; cleaner local processing would be a plus.
Note: For use in repetitive compilation testing, I created an AutoIt script that waits for Aut2Exe error windows to appear and closes them. In a Bash test-script, this error monitoring script is started in the background at the beginning of the test and killed at the end. This could be used with local builds, but I doubt it can be adapted to work on a remote machine since the remote SSH processes run in Windows Session 0 (including the login shell). Session 0 doesn't seem to be an issue if Aut2Exe exits normally, however.
(Abandoning remote compilation is not an option at the moment; we're trying to work our way out of that.)
I wrote a small script that displays a web page within autoit GUI.
Is there a way to "catch" the clicks on the links on that web page?
The web page is customizable, so I can define the link in any way I want...