>
> When the user has entered the data, the sequence object is
> created, collecting that data.
>
That's fine, or the object could be created when you start, and just
re-initialized for each new sequence.
> 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.
> It loads those images into
> memory (these images are now properties of oSequence, right?
> It steps through the data to see what frames are to be
> created. (repeat
> loop?)
> For any frame that is to be created, an oFrame object is
> instantiated.
Right, here I would loop through the data and create a frame object for
each image frame. I would pass into the new handler whatever properties
needed to be set for that frame. Then I would add that to a property in
oSequence called pFrames. It would be a list of frame objects:
repeat with i=1 to howeverManyFrames
tempFrame = script("FrameObject").new(memberNameOfImage, startFrame,
endFrame, number, etc)
oSequence.add(tempFrame)
end repeat
When you finish, oSequence would look like: oSequence.pFrames[<offspring
"FrameObject" 2 22ca14>, <offspring "FrameObject" 2 22ca14> ...]
> This oFrame object needs access to the source
> images. How? By making oSequence the ancestor of oFrame? Or
> rather by passing the images in question as a parameter to
> the oFrame? oFrame creates the image and exports it.
When you need to do your export, you could have a handler in oSequence
that loops through the frames and exports its image:
on exportSequence me, exportPath
repeat with frm in pFrames
imgMember = member(frm.pImage)
-- Do your export
end repeat
end
> What
> then? Who destroys the instance of oFrame? A method in oSequence?
Sure, you could have a handler that looped through the frames and called
something like oFrame.destroy().
>
> Another issue is the fact that creating and exporting an
> image can take a while. Creating all those images in a repeat
> loop could choke the application. I'd prefer using "on
> stepframe" somewhere. But where?
>
Well, you could add the object to the actorList and then export an image
on each stepFrame event. You may want to do some playing here. Is it
important to allow other events to occur while you are exporting this
video sequence? How bad is the crunch when you export? IMO a repeat loop
wouldn't be death here. I'd change the screen to a progress indicator of
some sort, and in my repeat loop update the display to show how far you
have come.
HTH
<br />
[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!]
