> Sure. Create a parent script with the properties and create an instance, > then refer to the properties in that instance.
Kerry, This seems like a lot more over-head then just calling a sendSprite to itself. I think i would prefer "containing" the functions to the sprite itself, rather than having to create/distroy an object for each sprite. But could this potentially cause errors or redundencies? I guess i was kinda hoping there was something simple in director's architecture that i was missing for "sharing" properties between behaviors on the same sprite? Morgan- [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!]
