Re: Quitting from an idle handler
Re: Quitting from an idle handler
- Subject: Re: Quitting from an idle handler
- From: Gil Dawson <email@hidden>
- Date: Mon, 8 Aug 2005 15:15:02 -0700
At 8:02 AM -0400 8/8/05, J. Stewart wrote:
I must admit to being a bit curious as to why you would want/need to
write a custom error handler when there is a built in construct that
will usually do a better job of it. Try - on error's sole purpose is
to deal with errors. It can notify, ignore, supply alternative
methods and of course, bail out.
Sometimes I need a little guidance seeing new ways of doing things.
My program mounts a target disk, starts a backup program, waits
(perhaps hours) for it to complete, then dismounts the target disk.
The program is structured as a lattice of several subroutines.
It makes elaborate tests inside the subroutines to ensure that all is
ready for the next step. If any test fails, I would like it to put
up a dialog and wait (perhaps hours) for the user to see it. When
the user OKs the dialog, I would like the program to quit.
My strategy for implementing this scenario is to make all the tests
on their failure branch call a single subroutine that puts up a
display dialog then calls error number -128.
What would you suggest?
Thanks for your interest, James.
--Gil
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden