Re: Applescripts run in editor, die with an OSA error when saved as an application
Re: Applescripts run in editor, die with an OSA error when saved as an application
- Subject: Re: Applescripts run in editor, die with an OSA error when saved as an application
- From: "email@hidden" <email@hidden>
- Date: Thu, 22 Jan 2004 14:14:26 -0700
Paul,
Thanks for the tip. When I save my scripts as regular (not as run-only)
applications they execute without any errors. You had stated that if this
were the case you would be mystified; I sure am. You were correct in
guessing that I saved these scripts as run-only out of ignorance. When I
have a few spare minutes I'll play with Smile and Script Debugger and see
what happens.
Thanks again,
Theresa Hilding
on 1/22/04 12:45 PM, Paul Berkowitz at email@hidden wrote:
>
On 1/22/04 9:17 AM, "email@hidden"
>
<email@hidden> wrote:
>
>
> This must be a simple system configuration problem. Applescripts run
>
> correctly in the editor but when I save them as run-only applications they
>
> die with a similar error every time. First, an alert box pops up that reads:
>
>
>
> "Could not run the script "***" because of a program error." The error code
>
> above the edit button varies, -1312 and -1344 are common. When I select the
>
> edit button another alert box pops up that informs me:
>
>
>
> "Could not read the file because of a scripting system (OSA) error."
>
>
>
> I am running OS X 10.2.8. I used applescript a lot under OS 9 but am new to
>
> scripting under OS X.
>
>
It was exactly the same in OS 9. If you save a script as Run Only, that
>
means that the source code is not retained and you can't open it for
>
editing. So I'd suggest saving it first as a regular application, not
>
run-only. When you do that, do you get any errors? If so, there might well
>
be something which has a different value when run from a stand-alone
>
application than from a script editor. When you open it for editing, the
>
offending term should be highlighted, and that should give you at least an
>
idea of what to check next.
>
>
If, on the other hand, the script worked perfectly as a regular application,
>
but not as a run-only, I'd be mystified. I have several run-only scripts
>
which work just fine in OS 10.3.2, but I do make them with Script Debugger,
>
not Script Editor. If this happens one would have to assume some sort of bug
>
in SE, and I'd recommend you try saving them in Smile (excellent free
>
editor) instead.
>
>
But chances are there's something wrong with your script that opening to
>
edit will reveal.
>
>
Is there any particular reason why you're saving these scripts as Run-Only?
>
It means you can never open them again. At the very least, save a _copy_ as
>
run-only, not the original. But I suspect you didn't know that "run-only"
>
means "can't open to edit"? It's just for keeping proprietary code secret,
>
and is usually used only for commercial and some shareware scripts.
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.