AutoHotkey Community

Hi Chris,

what about errorhandling in AutoHotkey



or like in Javascript with try {} catch(e) {} ?

Also nice would be a


If it is Off, all OutputDebug-Commands are skipped.

_________________
Tekl

I'm not sure what types of errors you had in mind with OnError. Perhaps you could give some examples.

In any case, these sound useful so I'll add them to the list for future consideration. Thanks for continuing to post your ideas.

Hi,

it was no error in specific. It just to get rid of those messages which a normal user cannot understand. For example I have a script which uses commands which are not present in an old AHK-version on the users computer. Instead of confusing him with a message, that a command could not found the OnMessage-Routine could catch it and tells him what to do: "Before reporting a bug, try updating AutoHotkey. Press Update to automatically download AutoHotkey. If you already have the newest version press send bug-report which will send a log-file to the author" or something like that.

As I include a file with hotstrings in my script it could be that something is wrong with the hotstrings-file so AutoHotkey will stop the script. This could be detected by the OnError-Routine which renames the hotstings-file to let the script work without it.

Just some ideas.

_________________
Tekl

Due to the way scripts are loaded, both of the above examples for OnError would be difficult to implement. Another problem is that I don't think there's a reliable way to tell the difference between a real syntax error and one for which the installed AHK version is too old.

Even so, I'll give more thought to it in case I've overlooked something.

In the meantime, you could have a starter script check the variable A_AhkVersion and only if it's new enough launch the main script. I realize this is clumsy, but it might be appropriate in some cases.

Thanks.

Actually, this is the method Mozilla Firefox employs to ensure compliance of extensions.

If it's good enough for Firefox...

That's what I'm actually doing and even if OnError would exist I won't do it all in one script because the starter-script only exists after an update checking the ahk-version and does some things that the main-script never needs to do. After executing it also deletes itself.



It was just an example. It would also help to create a custom error-dialog with a message in the preferred language and maybe a button or an edit-control to copy the real error-message into clipboard, so that a user can mail it to the author.

_________________
Tekl

Most things (such as Run) have a UseErrorLevel mode now. Please let me know if you discover any remaining sources of errors for which a UseErrorLevel mode would be desirable (other than syntax errors that prevent a script from launching).

Hi Chris,

there are not many sources left. But for example I had a mistake in a complex script where I forgot a Gui, Destroy in an GuiEscape-Label. I forgot to test the dialog in every case. A user then called the dialog, escaped it and after recalling the dialog he got the error, that a variable cannot be assigned again to another gui-element. The user didn't know what it mean and even didn't know if it was his mistake. As the script is quite complex I think there can be other error-sources and then I want to inform the user, that he has to inform me to get the bug fixed.

In my case it would help to make the error-dialog customizeable:

Well language-specific would be better (with variables), but I think AHK has to get the custom-message before a error can occur. Maybe a #CustomErrorMessage0407:/#CustomErrorMessage*07 could do it.

I hope you understand what I mean.

_________________
Tekl

Thanks for the details. There is a plan to add a UseErrorLevel mode to Gui (like the one for the Menu command). However, it's not be as good as your #CustomErrorMessage idea for all purposes, so I'm not sure which will wind up getting done.

Thanks!

_________________
Tekl