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: Tim Mansour <email@hidden>
- Date: Fri, 19 Dec 2008 09:55:26 +1100
On Thursday, December 18, 2008, at 07:42PM, "Chris Page" <email@hidden> wrote:
>If you keep your script applet frontmost, the user will be able to
>stop it without fighting with your script activating applications. Do
>you usually find it necessary to bring applications to the front while
>controlling them from another process? Note I said "usually". How much
>of the time is it a requirement?
I mainly work in database publishing environments, and many of my scripts are driven from FileMaker Pro. In a typical solution, the script template text is stored in a FileMaker text field with placeholder variables, and then used to calculate an AppleScript which is executed using FileMaker's "Perform AppleScript" command.
This effectively means that every script I write is wrapped within a "tell FileMaker". But yes, there are situations where I want another application to be activated and displaying a dialog to confirm progress or select options. With InDesign I can always use its own UI functions but it takes a lot more effort for simple dialogs. And non-Adobe apps don't necessarily have any of their own UI controls.
--
Tim Mansour <email@hidden>
Mobile 0405 500 846
_______________________________________________
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