AutoHotkey Community

[scamper_22]

Hi all,

just wondering what is the recommended way to handle errors.

In my case, I am using autohotkey to press some buttons and set some text of some controls. I ran into some issues where it takes a window some time to come up so when it executed the line, the control wasn't created yet. I temporarily just added in some sleeps.

Sleep(5000)

ControlClick...

Sleep(2000)

ControlSetText...


I'd rather have something a bit more concrete than the Sleeps.
Would you recommend testing the ErrorLevel after each Control command and then retrying it if needed.

Alternatively, I could test to see if a control exists first and then try the command.

Recommendations?
I'm leaning towards checking the error level myself.

[Carcophan]

MsgBox and ToolTip are the universal 'error checkers'. If used correctly (in the right places or with vaiables) they are magical.

Instead of a 'sleep' put in 'MsgBox, This is the first msgbox for testing reasons', if the box even comes up, you can assume the script has gotten to that point. And will continue until it reaches box 2 or 3 or 10. The msgboxs also can output variable information, so if you change values, you can verify everything is correct from step to step to step.
_________________
"Unfortunately a "COM for Dummies" book would be a little like "Neurosurgery for Dummies," in the end you're just gonna have to learn" ~Tank

[rtcvb32]

On top of that, use the documentation to your advantage. If it has errorlevel information or modification, use it for debugging as well as to make appropriate actions. You might start with simple error handling, but as specific errors pop up you'd add to it to handle more complex or common possibilities. Example:

[sinkfaze]

[jaco0646]

Debugging a Script
_________________
http://autohotkey.net/~jaco0646/