I tried this with MC 2.2.4 on NT and could not reproduce it. It worked
fine, no matter what order the buttons were layered.
[EMAIL PROTECTED] wrote:
>
> I have noticed a certain button behavior that has caused me problems in the
> past. I'm not sure if it is a "bug" or a "feature." To explain how it
> works, I created a new stack with one card with a button named "A1". The
> script of button A1 is:
>
> on mouseUp
> beep
> end mouseUp
>
> When I click on A1, the system beeps as expected. I then type the following
> into the message box:
>
> click at the loc of button "A1"
>
> When executed, the button A1 is clicked and the system beeps. I then create
> another button "A2" with the following script;
>
> on mouseUp
> click at the loc of button "A1"
> end mouseUp
>
> When I click on A2, nothing happens. However, if I *lower* button A2 to a
> level below A1 and then click on A2, button A1 is click as desired and the
> system beeps. What gives? Why should the relative levels of the buttons
> make a different? I am running MC 2.2.2
--
Marni Centor ([EMAIL PROTECTED])
Summit Systems, Inc.
22 Cortlandt Street
New York, NY 10007
(212) 896-3466
The views and opinions expressed in this email message are the sender�s
own, and do not necessarily represent the views and opinions of Summit
Systems Inc.
