>
> For another approach, see my article at Director Online:
>
> http://www.director-online.com/accessArticle2.cfm?id=340
>
> Basic idea: Have a generic button behavior that you attach to any
> and all buttons. When the button is clicked it does a sendSprite to
> the current sprite number calling a standard handler (I chose
> "mHit"). Then you attach another custom behavior to each button
> where each does the action of the button. For example, one could be:
Or you can combine both approaches, to get a truely OOP button - with or
without accessor methods ;)
Karina
[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!]
