To expend on the previous replies: To understand e.target and e.currentTarget it is important to take into consideration event flow. Also, the difference between these two transpires mainly when objects are nested within each other in the display list. There are three phases in the event flow: capture, target and bubbling. Say, you have three nested display objects: sprite1 is the

Hello, for a few reasons, I'm wondering what the best way to handle dispatching mouse events when there is more than one sprite that could potentially receive the event. In the code below, I've drawn two overlapping squares. The question is: when a mouse event occurs in the overlap area, is there anything I can do to redirect the event to the lower square instead of the upper square?

On 17 Jan 2008 Paul Vigay <invalid-email-address@invalid-domain.co.uk> wrote: In a dim and distant universe <04e9c2624f.john@user.orpheusmail.co.uk>, J Peachey <john@jpeachey.co.uk> enlightened us thusly: Just a thought, but rather than it being a programming issue, is it a sprite issue? Is the sprite standard, or one with an alpha? channel? Sprites are fine, and load perfectly