feoinc

I've made around it adding other entry point to my script and calling myself using that other entry point to close the new modal dialog (I do not want to have 2 scripts around). It is dirty and obscure but it is the only way around it that I've been able to make work. Or does anyone know if AutoIT has any multi-thread/multi-process support? Thanks to all who replied. Cheers

The problem is that the script hangs before reaching the WinWait(), if I write there any code like MsgBox(0, "test", "test") nothing is displayed. My guess is that the script never returns from the ControlCommand because the application spawns the modal dialog and the control and window it was addressing is not the current active one.

The script hangs after ControlCommand(), it does not execute anything after that instruction.

Hello, I've been searching a bit the forums but I haven't seen any topic related. I am trying to automate an application, and when I send a ControlCommand to change the value of a ComboBox the application pops up a modal dialog that I want to close. However after doing the ControlCommand the script seems to hang and start using around 10% of CPU. The piece of code that is having problems is something like: AutoItSetOption ("WinTitleMatchMode", 2) ... ControlCommand("program", "", 1000, "SetCurrentSelection", 1); this is executed ; AutoIt hangs here If WinWait("Error", "Error Message", 0.5) = 1 Then Send("{ENTER}") EndIf I am on latest version (3.2.12.1) I've discovered that if I manually close the dialog the script stays in memory and further executions work fine. However leaving a zombie process eating 10% of CPU is not an option. muttley