• 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: Display Dialog
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Display Dialog


  • Subject: Re: Display Dialog
  • From: Luther Fuller <email@hidden>
  • Date: Fri, 17 Dec 2010 13:25:09 -0600

On Dec 17, 2010, at 12:40 PM, Stan Cleveland wrote:

On Dec 17, 2010, at 9:34 AM, Luther Fuller wrote:

And, yes, don't tell the Finder or another application to do [activate and display dialog] unless it's necessary.

Here's a suggestion for the Chris's from Apple that monitor this list. How about adding a 'with activate' parameter to the 'display dialog' command that would bring the dialog frontmost and require no target whatsoever, not even 'me'?

It's more complicated than that, so I will suggest more ...

Suppose you have two AppleScripted applications. One of them, call it "A", tells Mail to do a bunch of stuff. The other, call it "B", does just one thing, it tells Mail to display a dialog.

If you run "B", but before replying to the dialog you run "A", then "A" can't operate because Mail is busy displaying the dialog. And if you run "A", then "B", then, I think, there will be intereference, but I haven't verified this.

I ran into this while writing an archiver & organizer for Mail. There is a basic principle here ...

An application should not be allowed to respond to two users at the same time.

Imagine a Mac with one screen, two keyboards and two mice (mouses?) and two persons trying to use the same application. Keep imagining ... very confusing, isn't it!

Unfortunately, this CAN happen when one of the users is an AppleScripted application. The user (a person) runs an AppleScripted application that tells Mail to do a series of steps that takes some time to complete. The user (person) forgets that the application (other user) is running and tries to operate Mail causing greate confusion and error to the other user.

When the AppleScripted application is launched, it ought to be able to first tell Mail to become "Busy" and display a visual indication of that state. In other words, the AppleScripted application now owns Mail exclusively and no other user, neither a person nor a script, can operate Mail. When the owning application is finished, it releases ownership of Mail and other scripts or persons can now operate Mail.

_______________________________________________
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: Display Dialog
      • From: Stan Cleveland <email@hidden>
References: 
 >Display Dialog (From: Peter R Hawkes <email@hidden>)
 >Re: Display Dialog (From: Steve Thompson <email@hidden>)
 >Re: Display Dialog (From: Luther Fuller <email@hidden>)
 >Re: Display Dialog (From: Stan Cleveland <email@hidden>)

  • Prev by Date: Re: Display Dialog
  • Next by Date: Re: Display Dialog
  • Previous by thread: Re: Display Dialog
  • Next by thread: Re: Display Dialog
  • Index(es):
    • Date
    • Thread