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:
on mHit me
SomeMovieLevelHandler()
end
And another could be:
on mHit me
gSomeObject.mSomeMethodCall()
end
Or whatever.
Irv
At 9:59 AM -0500 8/21/01, [EMAIL PROTECTED] wrote:
>Just got in and thought I'd post the question before I attempted it
>myself.
>
>I've got a bunch of buttons that react the same (ie rollover, down, blah
>blah blah) but on mousedown should all call a different handler.
>
>I was thinking that I create one behavior asking for the text of the
>handler to call, then do a sendallsprites(do(stringentered))
>
>Would this be the way to go or would it be
>sendallsprites(symbol(textentered))
>
>?
>
>
>[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!]
--
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/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!]
