Eva,

>It doesn't seem to be catching on any particular image.

OK, so it's not the images.


>It seems to be
>directly related to the volume of images.  For example initially the smaller
>galleries work fine but if I continue through and look through the other
>galleries (granted the larger galleries post the previously discussed error
>message.) and I come back to the smaaller galleries that were working before
>they proceed to sieze up too.

OK, so it seems more and more like a memory problem. What happens if 
you crank the projector's memory allocation?

On the whole I think the idea of storing the image pixels (you're 
doing a .duplicate()) in a list seems heavy (esp. unoptimized if it's 
jpegs) - the list will hold all the uncompressed images which may be 
rather heavy. It seems more optimized to just .duplicate() one image 
at a time to a buffer, do your stuff, erase the buffer, and then take 
the next image. But it depends, maybe you need all the images at once?

Let me ask you, there was a mention of having different galleries in 
different movies... do you make sure to erase the old list of images 
before entering the next movie? If it is a global, or contained as a 
property in a global object it might reside in memory unless erased. 
But then again, if you use the same name for the global in the next 
movie, it will be overwritten anyhoo.


>Again I am not using lesson one but two.  All of my members are held in
>internal casts not relative path folders.

Sorry, I thought lesson 2 was an extension of lesson 1.


>I always keep an external folder within my project for all of my xtras to
>eliminate overhead by having them in each individual movie.

The extras are not stored in the movie, but in the projector, of 
which you only have one, or am I missing the point?


-A.
[To remove yourself from this list, or to change to digest mode, go to 
http://www.penworks.com/lingo-l.cgi  To post messages to the list, email 
[EMAIL PROTECTED]  (Problems, email [EMAIL PROTECTED]). Lingo-L is for 
learning and helping with programming Lingo.  Thanks!]

Reply via email to