Le 21 mars 07 à 18:59 Soir, Jason Toews a écrit: > First, can someone please clarify the AppleEvent.Timeout constant > values, and their meanings? > > -1 = "use the default"... what does this mean, exactly?
The default timeout for an AppleEvent is 2 minutes. If you send an AppleEvent to an aplication which is busy, then the AppleEvent will be destroyed, by default, 2 minutes after it has been sent. > 2 (which I believe is supposed to be -2) = wait as long as it takes > for the AppleEvent to receive a response, even if that's a looooong > time (is this correct?) It will try until the target application becomes not busy (or you force quit it; in that case, you'll receive "false" for ae.send). > 0 = don't wait for a response to the AppleEvent; continue on to the > next line of code (is this correct?) Yes. That is certainly (I didn't tested that) equivalent to the AppleScript statement: ignoring application response (as you certainly know, AppleScript acts with AppleEvents). > Second, if I use some OTHER integer, does that integer represent > the .timeout value in seconds, or ticks, or milliseconds? LR says > seconds, but an old message on the NUG says ticks. It's in seconds. In AppleScript, for instance, you can use this statement: with timeout of 297 seconds tell app "Finder" to display dialog "Hello wolrd." end timeout _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
