Re: novice questions (error diagnosis/incomplete dictionaries)
Re: novice questions (error diagnosis/incomplete dictionaries)
- Subject: Re: novice questions (error diagnosis/incomplete dictionaries)
- From: "Jason W. Bruce" <email@hidden>
- Date: Wed, 22 Nov 2000 09:09:13 -0600
Joe,
Out of memory errors can occur when one builds lists through
concatenation as opposed to setting the end of the list to a new item. You
can end up making multiple copies of the list and not reclaiming some
memory, I believe. Is there some way you could isolate the code which deals
with list construction and post that? Several hundred lines sounds like
alot for what you are trying to do.
As to determining what an application responds to if its dictionary is
incomplete, I think it's pretty much trial and error.
Jason Bruce
----------
>
Message: 8
>
Date: Tue, 21 Nov 2000 04:33:43 +0100
>
To: email@hidden
>
From: Joe Rice <email@hidden>
>
Subject: novice questions (error diagnosis/incomplete dictionaries)
>
>
Hello -
>
>
Been watching the list for a little while and have tried to RTFM, but
>
I have couple questions which I hope someone might be kind enough to
>
address.
>
>
1. Recently put together my first scripting droplet, which was aimed
>
at processing audio files - first in SoundJam, and then in Cleaner,
>
with creation of some ancillary text files by the Finder.
>
>
What I found was that when dropping a folder containing a large
>
number of files to be processed, it would process many of them and
>
then halt with a "Can't Continue" error on each. (This is what was
>
returned in the error log - when I was watching the script live, I'd
>
get an "Out of Memory" error). I can't seem to determine what's
>
causing the error. I don't think the script is running out of memory
>
(being several hundred lines, I bumped it up to 4MB, but perhaps it's
>
creating a list of items to work on which is larger than some
>
internal limit? Could the Finder be running out of memory somehow? I
>
couldn't find any documentation on the "Can't Continue" error, so any
>
pointers would be appreciated! For each input file, 6 output files
>
are created - not sure if that might have some bearing on this.
>
Again, everything works fine until it's processed 30-60 input files.
>
>
I ended up using the walk folders command from Jon's Commands to
>
handle folder recursion, although I tried Apple's recursion sample
>
code with the same results.
>
>
Not sure if there's enough information there - I'm happy to clarify privately!
>
>
2. With some applications, I found that some command syntax wasn't
>
addressed in the application's scripting dictionary. (such as what
>
parts of the program and windows could be addressed, or what objects
>
took what arguments). Found some examples on the web which opened the
>
door to what could be done in some cases, but I'm curious as to how
>
one goes about determining what an application responds to if it's
>
dictionary is incomplete?
>
>
Thanks in advance for any assistance. I'm pretty impressed by how
>
easy AppleScript is to use, and cant' wait to delve further into it.
>
>
Joe