>> It looks at the data and finds >> out what source images are needed.
> I assume here you are referring to what "image frames" were specified by > the user. If so, I'll buy that. No, to give you a simplified description of what could be going on: The sequence could be a zoom into or a pan across one very large source image. With "source image" I referred to that large master image. But I think you still buy that. So each oFrame object has the code to create an image. In my simplied example, as the oFrame object is created, it gets a reference to the source image(s), which is/are a property/properties of oSequence. It then copyPixels a selection thus creating the wanted single image. Again: Would I pass the very large source image as a parameter? No need to make oSequence an ancestor to oFrame (to inherit the property source image)? > Sure, you could have a handler that looped through the frames and called > something like oFrame.destroy(). How would the destroy method look like? I guess me = VOID wouldn't work well. Wouldn't it be sufficient to delete the reference to the object in pFrames? > Well, you could add the object to the actorList and then export an image > on each stepFrame event. Which object? oSequence or oFrame? If oFrame then I could have hundreds of instances, all getting the on stepFrame event and all trying to do their job at the same time. That wouldn't work, would it? So it's rather an on stepFrame method in oSequence that increments a counter, so that on every stepFrame event another frame is created. Am I right? I think I need this approach because the image export with the direct image Xtra may take some time and in an repeat loop of hundreds of image the user wouldn't have a chance to stop/cancel the process. The progress bar is a good idea though. Can this approach work like that? Another question yet, more general: I have seen code, where all properties were referenced with "me" like that: me.pFrames. What for? Thank you very much for all your help Michael [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!]
