At 9:10 AM -0500 12/4/01, Genevieve Young wrote:
>Thank you Irv for your detailed reply.
>
>However, does this mean:
>
>i. a behavior is a class?
Yes (Jakob gave a good description of the wording used in Director/Lingo)
>
>ii. classes are therefore not variables?
No. Classes (behavior scripts and parent scripts) contain variables
- each is called a property variable.
>
>iii.we can define our own handlers in parent scripts?
Yes. The only handler you absolutely need is "on new me". The rest
is completely up to you.
>
>iv. so a parent script is a class?
Yes.
>
>v. and therefore a behavior is somewhat similar to a parent script?
Very similar. See my other postings for differences.
>
>vi. and so behaviors can be used to create objects?
Yes in the strict sense of what an object is. A behavior script is
instantated (which means that when the playhead reaches a sprite span
that has a behavior attached), Director automatically allocates
memory for the property variables defined in the behavior. When it
reaches the end of the sprite span, Directory automatically
deallocates the memory associated with those property variables.
Irv
--
Lingo / Director / Shockwave development for all occasions.
(Home-made Lingo cooked up fresh every day just for you.)
[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!]
