• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
calling classic osaxen from OSX
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

calling classic osaxen from OSX


  • Subject: calling classic osaxen from OSX
  • From: email@hidden
  • Date: Mon, 10 Dec 2001 14:53:36 EST

A funny thing is happening on the way to the future.

MacOS 9.x + Script Editor 1.6: when saving files, the options include
"Classic Applet" and "Mac OS X Applet". Depending on how the applet is saved,
when run, it runs in either the Classic or OSX environment (when OSX is
running). When the applet is running in Classic, I can call handlers which
use classic osaxen, and everything works just fine.

But....

MacOS 9.x + Script Editor 1.7 offers to save the script as "Application" - no
choice of whether classic or OSX. When the resulting application is then run
from OSX, it runs as an OSX applet and... it chokes on the osax calls. : (

Here's the actual code I'm using (requires Jon's Commands in classic):

This is saved with the name "ticks".

on theTicks()
return the ticks
end theTicks

And here's what I'm running inside the OSX Script Editor:

tell app "ticks"
set tic to theTicks()
end tell

So what's the deal? Did something break going to 1.7? Is there a way to
reliably access classic osaxen from OSX scripts? Is there a "using terms
from" construct or "tell classic environment" shell I should be using?

Jeff Baumann
email@hidden
www.linkedresources.com


  • Prev by Date: Re: URL Access Scripting
  • Next by Date: Re: URL Access Scripting
  • Previous by thread: Re: Comments Field
  • Next by thread: Summarize anything?
  • Index(es):
    • Date
    • Thread