Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

10.3: A fix for AppleScripts in OmniOutliner's script menu Apps
Problem: When using Panther, AppleScripts you write for OmniOutliner do work when run from ScriptEditor, but usually fail when invoked from Outliner's script menu.

Solution: Remove the script's resource fork, for instance by a contextual menu item such as GrimRipperCM. An alternative solution would be to use either Jaguar's ScriptEditor, Smile or the osacompile shell command for compiling the script.
    •    
  • Currently 1.20 / 5
  • 1
  • 2
  • 3
  • 4
  • 5
  (5 votes cast)
 
[21,974 views]  

10.3: A fix for AppleScripts in OmniOutliner's script menu | 2 comments | Create New Account
Click here to return to the '10.3: A fix for AppleScripts in OmniOutliner's script menu' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.3: A fix for AppleScripts in OmniOutliner's script menu
Authored by: dmg on Feb 04, '04 03:22:35AM

AppleWorks 6 also has the same problem. And even though it's a Carbon problem, the solution for AppleWorks might also work for OmniOutliner.

That is, save the script as an application (rather than as a compiled script) using Panther's Script Editor. Then see if it works from OmniOutliner.



[ Reply to This | # ]
Use osacompile! (was: 10.3: A fix for AppleScripts in OmniOutliner's script menu)
Authored by: dim ben on Feb 04, '04 10:47:58AM

The problem is in fact the new script format that the 10.3 scriptbuilder is using. OmniOutliner and some other applications got a problem with that.

The ususal way to work around this problem is to convert the applescript with osacompile. In the terminal, type osacompile Path/to/your/script and osacompile will create a new script called a.scpt in the directory where you called osacompile from.

See man osacompile for details.



[ Reply to This | # ]