>The button's
>*reaction* to a click should be provided by a separate behavior later on
>the same sprite, such as:
>
> on mouseUp
> alert "Ouch, you clicked me!"
> end
Yes, I've modified your behavior numerous times to account for mouseUp, and
even mouseDown (so a button has a down state). The behavior is
well-written, and easy to customize. Or is that customise?
>My behavior can also be used to activate/disactivate the button. If the
>"Mouse States" behavior is disactivated, it won't pass any events to
>subsequent behaviors. (This only works if "Mouse States" is the first
>behavior on the sprite).
That makes sense--I usually use the member change and cursor change
rollover behaviors as my first two.
>Please let me know if you have any problems with any of these.
Great--thanks. Understand, I wasn't reporting this as a bug in the
behaviour, but a bug in the program.
In fact, I sometimes use your behaviour, unmodified, to check for places
where another programmer might be looking for a mouse event. It's good to
know what somebody else has done, and why, if you are contemplating
blocking it.
Cheers!
Cordially,
Kerry Thompson
Learning Network
[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!]
