[quoted text, click to view] > And they shouldn't, OF COURSE!
Well .. actually they SHOULD of course. .. its just that you don't want them
to in this case.
[quoted text, click to view] > Why is it that way?
Because the button responds to the mouse, unless there is something over it
that ALSO responds to the mouse. If the front-most objext does not respond
to the mouse, then the next thing behind it gets a chance to respond and so
on until something responds (or there is nothing left)
[quoted text, click to view] > Why is a button completely covered by another MC, still active?
Because you haven't said NOT to make it active.
[quoted text, click to view] > My MC has some mouse actions on it, and as long as it is in front of
> another button, the other button is OBVIOUSLY not supposed to be active,
> has anybody in their right mind would NATURALLY EXPECT!!!!
If your clip has mouse actions on it, then it will get the mouse rather than
the button. So there must be something else you're not telling us here.
[quoted text, click to view] > Yet, is the only solution to this, to add some code in order to
> de-activate my buttons (12 of them, that would be 12 lines of code), or am
> I missing something?
set _enable = false for each button
[quoted text, click to view] > Thanks for your help, and your calming advice if possible
ok ... please be calm .. you'll enjoy life more that way :)
Jeckyl