Hi Scott,
It’s not ideal, but how about “Load Error Handler”? eg
Load error handler ccPWM/ErrorHandler (first error, last error)
After that have your code. If you want to catch OS level events like timeouts etc, it should happen automatically. If you want to create your own custom errors, you can eg
Signal error {27,"Something bad happened, Err 27"}
When done,
Unload error handler ccPWM/ErrorHandler
In your error handler, you can then take whatever action necessary, and include eg
SEA continue execution
You can test the #ERRCODE and #ERRTEXT for specific errors eg
Switch #ERRCODE
Case 27
; Our special error signal
Case kerrBadnotation
; Notation error
Case kerrDiskfull
; OS file ops related
Default
; All other cases here
End Switch
SEA continue execution
Hope this helps!
Regards,
Paul.
A man rushed into the doctor’s office and shouted, “Doctor! I think I’m shrinking!”
The doctor calmly responded, “Now, settle down. You’ll just have to be a little patient.”
Paul W. Mulroney
We Don't Do Simple Pty Ltd
ACN 161 009 374
Bentley Western Australia 6102
