>I have been using Director & Lingo since v4.0 and have recently been getting
>much more into the middleweight side of lingo with behaviours etc.  However,
>the documentation on parent scripts does just not make much sense to me -
>maybe its because I am a designer as opposed to a full on programmer, but
>can anyone give me some pointers to their advantage in relation to a
>behaviour and how they work in conjunction with them - I'm really confused
>and want to further my lingo skills, but know that I will not get there
>unless I bridge this gap. Examples, Technotes anything welcome.

Chapter 12 of LiaN, free online at the URL in my sig, talks about
Behaviors, Parent Scripts, and OOP.

In short, the Parent scripts and Behaviors have a lot of similarities.

Differences:

1. Behaviors are tied to sprites in the Score. Parent scripts are not.
Parent scripts float free. Thus they can outlive a particular sprite.

2. Behaviors can have user-configurable parameters (properties) set via
their getPropertyDescriptionList handler. Parent scripts can have
configurably properties, but they're set manually via Lingo, not via a
dialog box UI.

3. Behaviors generally respond to mouse events and things associated with
sprites, although this is not always true. Parent scripts often respond to
more esoteric things. For example, you might implement some "management"
object as a parent script, rather than as a behavior.

See chapter 12 of LiaN for more insights.

Regards,
Bruce


Bruce Epstein, Zeus Productions, [EMAIL PROTECTED], 732-940-2800
Check out LAST CALL - The Ultimate Bartending Sim:
http://www.zeusprod.com/games/lastcall.html
--------
Director and Lingo in a Nutshell (DiaN/LiaN) kick butt.
Free Sample Chapters: http://www.zeusprod.com/nutshell/downloads/
--------



[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/LUJ/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