Running autoit3.exe insice batch script never finishes

[zaphodikus]

I need to run my autoIt3 script from inside another program, I'm actually calling autoit3 from C# .NET. When does the script engine actually ever terminate?

I am miss-understanding the way autoIt is intended to be used, since in a control fashion; my calling application has no way of knowing when the script has completed (unless of course the script sets some kind of mutex that my C# code waits upon).

I have managed to work around things by creating a marker file as the last thing my script does, containing a "exitcode", the caller then kills off the autoIT executable once it see the file get created, but this feels like a very brutish approach. Does the script engine have an engine-exit verb/function? I need to run a series of scripts and in this case killing the autoit3.exe tray application is not necessary after each script, but this way of working does cloud things.

Basically why does autoIT not support running scripts in the same fashion as I would perl, python, powershell, etc scripts?

Edited June 25, 2012 by zaphodikus

[UEZ]

Well, without seeing the AutoIt code it is not easy to say something about your issue.

It depends on the code whether it exits or stay in a loop.

Br,

UEZ

[zaphodikus]

My bad.

I knew I was missing something vital, my script was actually paused, but I thought the tray icon always did that at the end, it was stuck on this line

WinWait("controller") ; wait for control

Is there a way to see which line number I am on when it shows paused? Since I pause at various points once my script gets bigger it gets harder to know.

Anyway, at least I found my script bug :-)