Re: Script Editor vs. Applet
Re: Script Editor vs. Applet
- Subject: Re: Script Editor vs. Applet
- From: "Stockly, Ed" <email@hidden>
- Date: Mon, 28 Jun 2010 12:44:04 -0500
- Acceptlanguage: en-US
- Thread-topic: Script Editor vs. Applet
Each time Script Editor runs it clears the values of globals and properties.
Each time you run your script as an applet, it retains those values. It
sounds like each successive run is increasing the amount of memory used.
Might be a good idea to try to reset values of properties or globals on
launch, or, if possible, at the end of the run.
Set myProp to {}
or
Set myProp to ""
If there are values you want to access in your script you may write them to
a file and read them as needed.
ES
On 6/27/10 12:46 PM, "tom wible" <email@hidden> wrote:
> yes, i saw my error(appending my local script objects to my list of
> eyetv schedules) & corrected it, which brought me to my main problem:
> the code works perfectly when run from script editor, but seems to
> have some major problem when i try to run it as a stay-open droplet.
>
> the 1st schedule is processed correctly, the 2nd takes 2x as long,
> the 3rd grinds to a crawl, using >50-80% cpu, slowly increasing
> memory usage, until i kill it or it dies. all other functions
> (processing tvpi files, emailing them to my dvr) continue to work
> perfectly as before, just the eyetv tell is affected.
>
> there is some major difference between the s.e. & droplet runtime
> environments...
_______________________________________________
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