I guesss the question is then, what happens during compile that fixes
this problem. I suspect that some how, a recognition process is
performed.
On Jun 7, 2006, at 1:47 AM, Cheryl Homiak wrote:
I just wanted to confirm the observation some of us made a few days
ago. I tried this again with the
"safaritabs" script I posted onlist a while back. I have two mac
minis, both running the latest macosX and both with the same settings
for the script editor and safari. On the computer on which I
originally ran it, it was saved as an application and ran fine. When
I moved it to the other computer it immediately showed up as an
application but as "classic" and complained about needing Macos9. I
pasted the original text file of this script in the applescript
script editor and it ran fine; saved it as an application and it
showed up as an application and ran fine. Very strange!!! I wonder if
this is some kind of bug or what would cause such behavior just
because a script is moved from one computer to another?
--
Cheryl
"Where your treasure is,
there will your heart be also".
