> 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.
>
Ahh OK. That helps the mental image I had. I was assuming a "slide
show." So your sequence in a set of difference "maneuvers" that can be
applied to a large image. The frames are then the individual images that
make up that "maneuver." Is the finished product a series of sequences,
or just the one sequence?
>
> So each oFrame object has the code to create an 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)?
>
Personally, I would pass it. I tend to view ancestors as a base class.
Then, child objects that utilize that ancestor are really subtypes of
the parent. For example, "Fruit" would be the parent script and "Banana"
and "Mango" would be child objects that have ancestors of "Fruit." In
this case, I don't view oFrame as a subtype of an oSequence.
> How would the destroy method look like?
Usually you put any clean up stuff you need to close out or "save." It
could look something like this:
In oSequence:
on clearFrames me
repeat with frm in pFrames
frm.destroy()
frm = VOID
end repeat
pFrames = []
End
In oFrame:
on destroy me
someObject = VOID
another = VOID
member("someMember").erase()
-- etc
end
> I guess me = VOID wouldn't work well.
No. That's not such a good idea. ;)
> 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?
That ought to do it. Just don't forget to remove yourself from the
actorList when exporting is complete.
>
> Another question yet, more general: I have seen code, where
> all properties were referenced with "me" like that:
> me.pFrames. What for?
It's makes the code clearer in cases where polymorphism is applied. If
your ancestor and child both have properties called "pName" the code is
easier to understand when you know which pName you are referring to.
Either me.pName or ancestor.pName.
<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!]
