Re: iTunes and AppleScript

FROM : Matt Neuburg
DATE : Fri Aug 25 21:15:40 2006

On Fri, 25 Aug 2006 10:36:44 -0700, John Stiles <<email_removed>> said:
>On Aug 25, 2006, at 10:34 AM, Matt Neuburg wrote:
>

>> On or about 8/25/06 9:39 AM, thus spake "Daniel Jalkut"
>> <<email_removed>>:
>>

>>> Behaving
>>> "just like Script Editor" (and unfortunately, running with
>>> NSAppleScript does not achieve that) isn't the only measure of
>>> success

>>
>> Yes, and I'm still mystified why the timeout isn't throwing an
>> error; if
>> NSAppleScript somehow doesn't obey timeouts, that would be yet another
>> failure on its part. m.

>
>OK, so now we're all on the same page


No, no, that's not what I mean. I'm saying that timeout *does* work in
NSAppleScript. Here's the error message from one that I tried just now:

[Session started at 2006-08-25 12:12:23 -0700.]
2006-08-25 12:12:27.026 NSAppleScriptTimeoutTest[958] {
    NSAppleScriptErrorBriefMessage = "AppleEvent timed out.";
    NSAppleScriptErrorMessage = "Finder got an error: AppleEvent timed
out.";
    NSAppleScriptErrorNumber = -1712;
    NSAppleScriptErrorRange = <0000002c 00000034 >;

That is the "right answer" when something times out. What I want to know is
why *your* event is not timing out. I'm suggesting that you might need to
test your script in something like Script Editor. Tweak it there until the
timeout works. If you can do that (and I'm not guaranteeing that you can),
it should work in NSAppleScript too. m.

--
matt neuburg, phd = <email_removed>, <http://www.tidbits.com/matt/>
A fool + a tool + an autorelease pool = cool!
AppleScript: the Definitive Guide - Second Edition!
<http://www.amazon.com/gp/product/0596102119>