Re: Basic AppleScript theory
Re: Basic AppleScript theory
- Subject: Re: Basic AppleScript theory
- From: Emmanuel <email@hidden>
- Date: Wed, 20 Nov 2002 12:12:48 +0100
At 11:55 AM -0600 19/11/02, Wallace, William wrote:
And why
wouldn't the launched script application just do its thing quietly in the
background?
Maybe you can use a little help here: each AppleScript commands
returns some result (which may be empty). In other terms, when you
execute an AppleScript command, the application you've sent the
command to (be it AppleScript itself) will execute it, will hang your
script until execution is terminated and will, upon termination, send
back to the calling script the result of the execution - be it the
empty result, a meaningful one, or an error notification.
So, you may want to know that the "ignoring application responses"
structure will force the lines that it encapsulate to return to the
script before the command is actually terminated, letting the called
app do its thing quietly in the background.
For instance, when I script trashing a file in Finder, I usually
write (pseudo-code)
------------------------
ignoring application responses
tell app "Finder" to delete alias TheFileToDelete
end ignoring
------------------------
in order that the script continue even if for some reason the Finder is slow.
Emmanuel
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.