On Sun, 24 Dec 2006 23:40:55 +1100, T&B <email@hidden>
said:
>Hi Matt,
>
>> Go right ahead - this works just like any AppleScript "library"
>> situation (as described, for example, on p. 121 of my book, using
>> "load script" in the usual way)
>
>Yes, that works. But my issue is that those loaded .scpt files can't
>be edited in ASS, and can't be debugged (with breakpoints etc).
I suppose that's true. But since debugging with the Xcode debugger generally
works so poorly in AppleScript Studio anyway, that's never been a big issue
for me. I use other debugging techniques that don't rely on the Xcode
debugger.
> And I
>can't two main scripts call one library script unless I load two
>copies of that library (ie one into each calling script), which is
>just wasteful and redundant.
But if that really bothers you, there are solutions to that problem,
depending on how much command of the architecture you are willing to assume.
As I said, check the archives.
No one is denying that the current architecture is a pain in the butt. I'm
just saying that there are things you can do a lot more constructive than
bemoaning the (undeniable) fact that the current architecture is a pain in
the butt. m.
--
matt neuburg, phd = email@hidden, <http://www.tidbits.com/matt/>
A fool + a tool + an autorelease pool = cool!
AppleScript: the Definitive Guide - Second Edition!
<http://www.amazon.com/gp/product/0596102119>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-studio mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
