Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!rochester!bbn!bbn.com!mesard
From: mesard@bbn.com (Wayne Mesard)
Newsgroups: comp.sys.mac.hypercard
Subject: Re: Intercepting error messages
Message-ID: <40518@bbn.COM>
Date: 25 May 89 19:35:16 GMT
References: <14642.247BD08B@cmhgate.FIDONET.ORG>
Sender: news@bbn.COM
Reply-To: mesard@BBN.COM (Wayne Mesard)
Organization: Bolt Beranek and Newman Inc., Cambridge MA
Lines: 19

In article <14642.247BD08B@cmhgate.FIDONET.ORG> Barry.Chern@f200.n226.z1.FIDONET.ORG (Barry Chern) writes:
>Did you try trapping for the result in your script? Usually, "if the
>result is not empty" can be used as a condition tester right after the
>command that can possibly fail, followed by instructions for what you want 
>done in this eventuality.[...]
>Maybe you are saying that you tried this and it doesn't
>work in this case. If so, sorry, I haven't tried it , just talking off the 
>top of my head.

Yes, that is what I was saying.  I want a global like lockErrors which
will direct all error messages to _the result_ as opposed to a dialog
box (where a niave user asks "What's a background?" and then "How come
the program stopped working?".)  Currently, this happens only for some
(one?) errors, and it happens automatically.

-- 
unsigned *Wayne_Mesard();     POKE 59468,16
MESARD@BBN.COM                
BBN, Cambridge, MA