Re: Applescripts often going wrong when saved as package
Re: Applescripts often going wrong when saved as package
- Subject: Re: Applescripts often going wrong when saved as package
- From: Tetsuro Kurita <email@hidden>
- Date: Sat, 23 Jun 2012 17:27:05 +0900
> ==========================
> 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.
Does "init() of includes" mean initializing all properties of "includes" ?
If all properties are initialized when the applet is launched, the cause
of your problem will not be remembering values of properties.
You should describe the details of your problem.
For examples, differences your expected behavior and actual behavior, error
messages and so on.
=======================================================
Tetsuro KURITA
E-mail: email@hidden
http://www.script-factory.net
=======================================================
_______________________________________________
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