• 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: Tell Blocks Considered Harmful (was Re: open for access)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Tell Blocks Considered Harmful (was Re: open for access)


  • Subject: Re: Tell Blocks Considered Harmful (was Re: open for access)
  • From: Chris Page <email@hidden>
  • Date: Wed, 17 Dec 2008 13:49:39 -0800

On Dec 17, 2008, at 1:02 PM, Jon Pugh wrote:

At 11:44 AM -0800 12/17/08, Ed Stockly wrote:
What would be really useful is the ability to shutout all user interaction while the script runs.

I've been asked about this a number of times. I liken it to a game taking over the entire screen & UI experience. We want a script to be able to do the same thing, except we don't really want to take over the whole screen since we often like to watch the automation run, but don't want the user mucking with things while it does. All they should be able to do it abort the process, or just interact with the script's UI whatever & wherever that appears.


That's not too difficult to implement. You can place a translucent (even 100% translucent) window in front of all windows, like Dashboard does, for example.

But how do you relate that to the script and stop the script if the user wants it to stop? That's where it gets tricky.

When a script does ‘display dialog’ the script waits for the dialog to be dismissed. It doesn't continue running until then. Alternatively, you can write

  ignoring application responses
    display dialog "Hi!"
  end

and the script will continue running while the alert is displayed. But, if the user clicks the Cancel button, the script will never know, because it ignored the response.

So, how would we signal the script to stop? Hmm.

--
Chris Page

  The other, other AppleScript Chris

_______________________________________________
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
  • Follow-Ups:
    • Re: blocking user actions
      • From: Jon Pugh <email@hidden>
    • Re: Tell Blocks Considered Harmful (was Re: open for access)
      • From: Ed Stockly <email@hidden>
References: 
 >Re: Tell Blocks Considered Harmful (was Re: open for access) (From: Shane Stanley <email@hidden>)
 >Re: Tell Blocks Considered Harmful (was Re: open for access) (From: Chris Page <email@hidden>)
 >Re: Tell Blocks Considered Harmful (was Re: open for access) (From: Ed Stockly <email@hidden>)
 >Re: Tell Blocks Considered Harmful (was Re: open for access) (From: Chris Page <email@hidden>)
 >Re: Tell Blocks Considered Harmful (was Re: open for access) (From: Rick Gordon <email@hidden>)
 >Re: Tell Blocks Considered Harmful (was Re: open for access) (From: Rick Gordon <email@hidden>)
 >Re: Tell Blocks Considered Harmful (was Re: open for access) (From: Chris Page <email@hidden>)
 >Re: Tell Blocks Considered Harmful (was Re: open for access) (From: Deivy Marck Petrescu <email@hidden>)
 >Re: Tell Blocks Considered Harmful (was Re: open for access) (From: Chris Page <email@hidden>)
 >Re: Tell Blocks Considered Harmful (was Re: open for access) (From: Ed Stockly <email@hidden>)
 >Re: Tell Blocks Considered Harmful (was Re: open for access) (From: Jon Pugh <email@hidden>)

  • Prev by Date: Re: Option Key Down
  • Next by Date: Re: Tell Blocks Considered Harmful (was Re: open for access)
  • Previous by thread: Re: Tell Blocks Considered Harmful (was Re: open for access)
  • Next by thread: Re: Tell Blocks Considered Harmful (was Re: open for access)
  • Index(es):
    • Date
    • Thread