Re: file format backwards compatibility question
Re: file format backwards compatibility question
- Subject: Re: file format backwards compatibility question
- From: Matt Neuburg <email@hidden>
- Date: Sat, 23 Jul 2005 13:21:10 -0700
On Sat, 23 Jul 2005 09:59:34 +0200, Sander Tekelenburg <email@hidden>
said:
>At 19:51 -0700 UTC, on 2005/07/22, Matt Neuburg wrote:
>
>> When I save a compiled script from the Script Editor in Tiger and then try
>> to open it in Classic, where AppleScript 1.8.3 is present, either Script
>> Editor refuses to open it (in one version of Classic Script Editor that I've
>> got) or it crashes (in another version). Is this the experience of others?
>
>AFAIK it should work. For me, Script Editor 1.8.3 running in the Classic
>Environment can open scripts saved with 10.4.2's Script Editor, provided they
>were not saved as bundle.
>
>Possibly calls to third-party Scripting Additions that might not be available
>to the Classic Script Editor would affect this?
My file says "hello". Or: display dialog "hello". It makes no difference.
Script Editor 1.8.3 crashes when I try to open it. Script Editor 1.4.3 on
the same machine (i.e. running under AppleScript 1.8.3) gives a message
saying it can't open the file, which is at least well behaved.
Nevertheless I stand amazed that backwards compatibility is so poor, or that
users have not complained more about this. m.
--
matt neuburg, phd = email@hidden, <http://www.tidbits.com/matt/>
A fool + a tool + an autorelease pool = cool!
AppleScript: the Definitive Guide
<http://www.amazon.com/exec/obidos/ASIN/0596005571/somethingsbymatt>
_______________________________________________
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