• 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
Re: Classic vs OSX osax
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Classic vs OSX osax


  • Subject: Re: Classic vs OSX osax
  • From: Aaron London <email@hidden>
  • Date: Thu, 24 May 2001 12:31:24 -0400

Classic scripts/applets cannot use native OS X osax and vice versa, or at least that is the official position. There's a workaround, however. Look in your OS 9/Classic system folder and you'll find a little app called ProxyApp. I use Dialog Director, an OS 9/Classic osax from my OS X native scripts/applets, by nesting all calls to it within tell statements directed at ProxyApp. The easiest way to convert a Classic script/applet for use in OS X while retaining Classic osax calls is the following: open the old script/applet in the OS X script editor, where calls to Classic osax show up as raw AE code; nest that code within tell ProxyApp statements, where ProxyApp is set to the path to the actual ProxyApp since the script editor will otherwise replace "ProxyApp" with "Classic Startup" on save and the script won't work. Hope this helps.


  • Prev by Date: Re: Calling other OSA Scripts
  • Next by Date: Re: Outlook Express rules?
  • Previous by thread: Re: applescript-users digest, Vol 2 #697 - 11 msgs
  • Next by thread: automating e-mail replies
  • Index(es):
    • Date
    • Thread