• 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: App and droplet
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: App and droplet


  • Subject: Re: App and droplet
  • From: Axel Luttgens <email@hidden>
  • Date: Fri, 13 Oct 2006 23:14:21 +0200

On 13/10/06 19:37, kai wrote:

On 13 Oct 2006, at 11:51, Axel Luttgens wrote:

[...]
A bit as if the execution of a handler's first statement and the handling of pending events were in close relationship (sorry, I am unable to express this in a better way).
Is this somehow documented?

Yes, Axel. Check out the discussion section for "awake from nib" from the AppleScript Studio Terminology Reference:


ADC Home > Reference Library > Reference > AppleScript > Tools > AppleScript Studio Terminology Reference:
Application Suite > Events > awake from nib


[...]

The section indicates that the order in which event handlers are called, on application start up, is:

[...]

This is borne out by tests here on, focusing on application and nib event handlers (including open and quit), which suggests the following, slightly more detailed sequence:

[...]


Thanks a lot, Kai, for having taken the time to reply in such a detailed way!
I was more concerned with those seemingly differing behaviors between an AS app (as built with SE) and and an AS Studio app, as far as the handling of pending events is concerned.
With an AS app, it seems that the handlers for pending events are executed each in turn.
With an AS Studio app, it seems that a kind of parallelism may be observed: the execution of the handler for event B seems to be intermangled with the execution of the handler for event A, even if event A occured before event B.
And this is why, I guess, you suggested following workaround:
set WasActivated to GotActivated
I was thus more precisely wondering whether one could always reliably rely on that precise moment: the execution of a handler's first statement for catching an inter-event condition, such as the setting of a property (in this case, GotActivated).
Hence my question about a documented -"official"- statement about such matters (which I haven't found yet).


Now, who said "OT"?


Um...


Never mind... Just a stupid joking attempt. :-)

Axel
_______________________________________________
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


  • Follow-Ups:
    • Re: App and droplet
      • From: kai <email@hidden>
References: 
 >App and droplet (From: Craig Stanton <email@hidden>)
 >Re: App and droplet (From: Axel Luttgens <email@hidden>)
 >Re: App and droplet (From: Philip Aker <email@hidden>)
 >Re: App and droplet (From: Axel Luttgens <email@hidden>)
 >Re: App and droplet (From: kai <email@hidden>)
 >Re: App and droplet (From: kai <email@hidden>)
 >Re: App and droplet (From: Axel Luttgens <email@hidden>)
 >Re: App and droplet (From: kai <email@hidden>)

  • Prev by Date: Re: Indesign Spread confusion
  • Next by Date: AppDirectoryContents
  • Previous by thread: Re: App and droplet
  • Next by thread: Re: App and droplet
  • Index(es):
    • Date
    • Thread