Is there any general information on what a recommended approach
might be for error handling/recovery with ooRexx and ooDialog?
I have a specific problem right now, where I have not found a good
solution. I run the application with Rexxhide and have found that
if ooRexx errors, for example with a "Bad arithmetic conversion"
type of error, if I have also have a .TimedMessage with an infinite
timeout, the only way I have found to end the application and
regain control is by using the Task Manager. Since the .TimedMessage
blocks getting control via the normal windows "X" close, or a cancel
button, and Rexxhide prevents a Ctrl-C from interrupting the
interpreter. I could use a timed duration of the longest period I
would expect the timed activity to take, but then the waiting message
would also keep the dialog from continuing until the timeout period
has expired. Looking for suggestions/thoughts.
--
Art Heimsoth - artst...@artheimsoth.com
------------------------------------------------------------------------------ This SF.net email is sponsored by Windows:
Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev
_______________________________________________ Oorexx-users mailing list Oorexx-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-users
