• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Best practice for activation of another application
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Best practice for activation of another application


  • Subject: Re: Best practice for activation of another application
  • From: David Crowe <email@hidden>
  • Date: Sat, 8 Oct 2005 12:38:29 -0600

I like to put 'activate' before every display dialog and 'error' statement, although sometimes it can be annoying. But if the input is needed, c'est la vie.

It's also important to minimize user input, and to try to cluster it in time, so that the user isn't supposed to interact every few seconds, it's much better to get the input up front, if possible.

It's also important to remember that 'activate' may be necessary even when the application may already be active according to your script, because the user may have changed the focus if more than a few seconds has elapsed.

I wish this was the default behavior for display dialog/error, actually, with the scripter having to add "without activation" to stop it from doing this.

- David Crowe
_______________________________________________
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


  • Prev by Date: Re: do shell script "ps -auxwww | grep rsync | grep -v grep"
  • Next by Date: Paths & quoted form & do shell script
  • Previous by thread: Mount a Disk Image with Password
  • Next by thread: Re: Best practice for activation of another application
  • Index(es):
    • Date
    • Thread