Hi,

Input3D events are processed using the Stage. To filter the results, you can use Input3D.enableEventPhase. Using that, if some event was catched by another movieclip before reaching the stage, Input3D will ignore it. In the same way, setting it to false will make all events always reach Input3D (because they all reach the Stage).

But even if you have enableEventPhase set to false, you can always stop the event by hand. For example, if you have a 2d button, in your click handler you can do something like this:

private function buttonClickHandler( e:MouseEvent ):void
{
    e.stopPropagation();
    // your code and stuff
}

In general terms, event flow in Flash is a little convoluted, you can see more details here.

Regards,

Hi,

This has been really difficult for us to track down. Whenever changes are made, half the users are happy while the other half isn't Please take a look at the code in this link.

The results I get from this code is that if I click the cube, I get a trace saying "Cube Clicked" and if I click the square sprite, I only get a trace saying "Square Clicked", even if I click on a part that overlaps with the cube.

If I add Input3D.enableEventPhase = false; into the mix, if I click the square where it overlaps with the cube, both messages are triggered, which is correct.

Would you mind testing this to confirm my results?

I see. mouseHit only checks if the mouse button has been hit, it doesn't check where. So if you click the mouse, the check will be true no matter your eventPhase settings. You can however, filter the results like this:

private function sceneUpdate( e:Event ):void   
{
    if ( Input3D.eventPhase > EventPhase.AT_TARGET )
        return;
           
    if( Input3D.mouseHit ) 
    {     
        trace( "Input3D.mouseHit" );
    }
}

Please se if this works for you.

Regards,