Re: on blocking target applications' GUIs (was Re: Tell Blocks Considered Harmful)
Re: on blocking target applications' GUIs (was Re: Tell Blocks Considered Harmful)
- Subject: Re: on blocking target applications' GUIs (was Re: Tell Blocks Considered Harmful)
- From: Ed Stockly <email@hidden>
- Date: Thu, 18 Dec 2008 00:06:19 -0800
This is one reason I think nearly all applications should have a
Script menu. So that users are inclined to run the script from
within the application, and it will naturally prevent them from
interacting with that application while the script is running. This
also gives the user a predictable way to stop the script, instead of
having to bring an applet to the front to stop it.
Many of my scripts control multiple applications, and the app where
the script launches or runs is often not the script where most of the
work is done or where I want user interface items displayed.
For example, I have a script launched from the finder that downloads a
pic through Transmit, open it in Photoshop, save it a new file/format
then open place it in a new quark document. It could be launched from
a script menu, but that wouldn't offer any advantage. I certainly
wouldn't want to have to return to the finder, or whichever app
launched the script, each time I display a dialog.
ES
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden