September 8, 2003
During one of those ‘head meets desk’ moments today, I discovered that AppleScript under OS X recognizes scripting additions that reside in your OS 9 system folder. On one level this makes an awful lot of sense, since this is the same basic behaviour the two systems use with respect to fonts. Simply, OS X can use fonts that are installed in the OS 9 system folder. While this may seem a logical and reasonably transparent way to accessing fonts residing in multiple locations across operating systems, the same concept caused no shortage of frustration in terms of getting a certain AppleScript to compile. I still run a couple of applications in classic (most notably Claris Emailer) and rely on a half dozen customized scripts for various repetitive tasks. I also had a few older third-party scripting additions dumped in the system folder, namely Akua Sweets and the relatively ancient FB text manipulation tools, because you never know when you might need one of them. My problem was that it attempting to read and set type and creator information via a script, the ding dang script would choke on the property statement for grabbing the creator of a file. After finally trying the script on another Mac and discovering that it was in fact something on my machine and not my questionable scripting prowess, I removed all of the non-Apple osaxen and tried again. Sure enough the sucker worked. But weirdness of a different animal still persists. Even after putting each of the scripting additions back into the OS 9 system folder in order to determine which of the little buggers caused the initial burp, the issue is gone. Everything is fine, as if nothing happened. I guess I’m happy about that, but I’d sure appreciate a bit more closure.
This item was posted by.
You can follow comments on this item via the RSS 2.0 feed.
Feel free to leave a comment below or trackback from your own site.