but wait, there's one example that shows what is possible multithreading in AutoiT -InetGet. But here's the irony, this function should be part of the language.
Use autoit info tool to get the id of the control you want and then controlgettext to get the text of the control. If it is IE then check the IE UDF. IEPropertyGet(ID, innerText) could do the trick. But we are shooting in the dark. Share your code or the site you are automating...
That's not an error, that's a warning message that is telling you that your script is written badly and AutoIt refuses to run such poorly written drivel.
joker197cinque, Unfortunately your username does not inspire confidence. Please PM me with some details of what run few software, press some buttons, copy some files really means. You get to the Messenger via the dropdown next to your username at top-right. Until I get a satisfactory answer we will lock this. M23
I'm not sure I'd accept the answer you did unless I heard it from a code dev.
Why would the local var need to be tested again? it is equal to 7 and tested at the top of the loop, it is not While $var < 8 where it might be tested.
I would say it is actually a bug, but someone would come along and say otherwise so let's just say using such a temp variable outside of its loop causes undefined behaviour.
I imagine it has something to do with how AutoIt handles loops, and specifically nested loops.
You see the Until keyword does not recognize that the variable has reached its limit and Do loop should end.