Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!mcvax!ukc!stl!stc!datlog!torch!paul
From: paul@torch.UUCP (Paul Andrews)
Newsgroups: comp.sys.mac.hypercard
Subject: Re^2: Intercepting error messages
Message-ID: <348@torch.UUCP>
Date: 5 Jun 89 14:22:11 GMT
References: <14659.247E7348@cmhgate.FIDONET.ORG>
Organization: TORCH Computers Ltd., Cambridge, England
Lines: 16


Intercepting error returns seems to be basically impossible. I've come across
two situations which behave differently:

1) Hitting Cancel in a find stack dialogue gives no indication that the
operation failed. Solution? check name of stack before and after you issue
ANY go stack command (sigh).

2) Aborting a print request that orginated in a script aborts the ENTIRE
SCRIPT! Solution? Check in an idle handler for a flag you set before printing
and clear after printing. If its set in the idle handler, the print was
aborted (paradoxically, I don't think this is so drastic).

Still, It keeps us glued to the screen for hours of harmless fun.

- Paul.