Re: Finder scripting dies
Re: Finder scripting dies
- Subject: Re: Finder scripting dies
- From: kai <email@hidden>
- Date: Sun, 19 Oct 2003 17:35:43 +0100
on Sun, 19 Oct 2003 08:45:52 -0700, Paul Berkowitz wrote:
>
On 10/19/03 8:21 AM, "kai" <email@hidden> wrote:
>
>
> While this generally doesn't happen with a standalone, I've sometimes forced
>
> access to application-specific terms by simulating a 'tell app' compile. For
>
> example, by amending the above script to...
>
>
>
> -------------------------
>
>
>
> run script "tell app \"Finder\"" & return & "end"
>
> tell application "Finder" to disk of folder "non-existent:folder:"
>
>
>
> -------------------------
>
>
>
> ....the standalone version then also returns:
>
>
>
> --> Can't get disk of folder "non-existent:folder:" of application "Finder".
>
>
That wouldn't make much difference! You'd just get a nicer error message,
>
that's all.
I don't think I suggested that it would make a difference. In fact, since an
error message occurs either way, I was merely trying to confirm that the
absence of Finder terms did not necessarily indicate a connection with your
previous compile difficulties - which you seemed to infer in your message of
Thu, 16 Oct 2003 09:43:58 -0700:
>
>> For the first time, a user of one of my run-only scripts has reported the
>
>> same bug which until now I've only seen in a script editor...
>
I have used the same sort of 'run script' to get application contacts
>
"exported" (to text files as well as to display dialogs outside a tell block)
>
in familiar English terms instead of in raw codes, but that would not change
>
the fact that an error message would still result and the script would still
>
not run.
Quite.
>
> Of course, all this may *still* have nothing to do with your client's
>
> problem - and I apologise in advance if it turns out to be a red herring.
>
>
>
> I obviously don't know how the path "ili 2:Users:...1.2.11:" is derived in
>
> your script but - in view of the above - I'd be tempted to re-check its
>
> validity before looking elsewhere for a cause...
>
>
This miscegenation of a list server has obscured the fact that the name of
>
his disk contains an accented letter (e-acute) - bowdlerized on this mailing
>
list to an "i". I have read an Apple note that indicates that there are
>
still some bugs in AS 1.9.1 with accented file path names.
Yes, that causes a similar problem here.
>
I suspect that the fact that the user gets this error consistently using a
>
standalone applet...
Where it occurs, the 'e-acute' disk name errors either from a script editor
or a standalone.
>
...- rather than the inconsistent behavior many of us have noticed in script
>
editors, and which can be fixed, as Jon said, by relaunching the app.
I must have missed the message in which you concluded that the two
behaviours were not connected.
>
I wrote the user a couple of days ago suggesting he temporarily change the
>
name of his disk. I have not heard back yet. If the accent is not the cause,
>
but an inaccessible Finder aete such as we've seen in script editors, the
>
script will error on other Finder commands (such as "update"). If the
>
scripts runs OK, it will mean that the accented letter in the disk was the
>
cause of the problem.
I'm sure that should fix it.
---
kai
_______________________________________________
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.