Applescripts often going wrong when saved as package
Applescripts often going wrong when saved as package
- Subject: Applescripts often going wrong when saved as package
- From: James Gretton <email@hidden>
- Date: Fri, 22 Jun 2012 18:23:17 +0100
Hi, I have a set of AppleScripts which use some shared AppleScript libraries (written by be).
To make my library functions accessible I load the .scpt into a property. A simple example of this is below.
==========================
property includes : null
on run {}
set includes to load script file "::Library:Applescript:general:includes.scpt"
init() of includes
...
end run
==========================
I've found this works very well when testing from AppleScript Editor, but when I save my AppleScripts as applications things have been a little unreliable.
I *think* the problem is related to AppleScripts remembering the value of various property variables between application runs (particularly after something's timed out and/or gone wrong). But I'm not 100% sure this is causing all the problems.
In particular I don't really know why this problem only seems to occur when saved as an application.
Perhaps I just need to be more careful to set all properties to null at the start of each included file?
I know i haven't given any concreate information here, but any general thoughts, previous experience and suggestions would be appreciated!
Many thanks,
James
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden