OnAutoItExit even with hard error?

[ken82m]

Twice I've had need to run OnAutoITExit even in the script died from a hard error.

I try to take everything into account but I'm not perfect

The only way I've found to do this is:

1) Start the script and then RunWait itself with a switch to actually run the script.

2) The original instance can run Func OnAutoItExit when the child process terminates.

Does anyone know of a better way to do this that I'm missing?

Kenny

Here's an example:

MsgBox(0,"",$UndefinedVar)

Func OnAutoItExit()
    MsgBox(0,"","Exiting")
EndFunc

[dbzfanatic]

Try this:

$oMyError = ObjEvent("AutoIt.Error","MyErrFunc") ;Straight from help

[ken82m]

Thanks, never would have thought to look at that one

I tried this but no joy

$oMyError = ObjEvent("AutoIt.Error", "OnAutoItExit2")
MsgBox(0,"",$UndefinedVar)

Func OnAutoItExit2()
    MsgBox(0,"","Exiting")
EndFunc

Kenny

[dbzfanatic]

Well this only catches COM errors. Is that what you're getting?

[ken82m]

No just general errors on autoit fucntions.

I was using a script I got from the forum that allows me to block user input except for specific keys,

or just block the mouse or keyboard.

The problem is if I get an error that causes the script to end immediately and it doesn't unlock user input.

The only way I found around it was the above method which allows the original process to issue the unlock command no matter what happens.

-Kenny

[Valik]

Fix your code, that's the right answer. Under no circumstance should a properly written script hard-error. Implementing a solution like this doesn't fix the underlying problem. It's a very bad thing to do.

The alternative - and more correct version of what you are trying to do is spawn a second process which does nothing but block input and waits either for the parent script to close or for it to receive a signal from the parent to unblock input. In other words, decouple the event where you need guaranteed action from the main script so that things that affect the main script do not affect the guaranteed actions.

[dbzfanatic]

Oh you're still using that? I ghosted that thread a bit so I know what you're talking about. If you run the script from SciTe you should get the error output in the console and be able to see where it happens, then just do a bit of error checking and do something like:

If @error <> 0 Then
;code to release lock on keys
EndIf

[ken82m]

Thanks guys.

Valik-

Your second suggestion is actually what I'm doing now, I guess I didn't do a very good job explaining it in my first post.

As far as fixing the script your absolutely right. But the scripts are long and just used for some automation on my own machines and I guess I'm lazy lol.

dbzfanatic-

Thanks I'll give that a try

One way or the other I have a way around it now was just wondering if there was another I may have been missing.

Thanks,

Kenny