Hi, If that is the requirement the try, event.stopImmediatePropogation?? or why r u not assigning priorities to events at the time of adding event listeners???
On 29/03/2008, Alex Harui <[EMAIL PROTECTED]> wrote: > > Looks like that was done on purpose. DRAG_ENTER is more of an "offer". > If you don't accept drag on the potential new target, we don't send > DRAG_EXIT on the old target. > > > ------------------------------ > > *From:* flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] *On > Behalf Of *Mac Sims > *Sent:* Friday, March 28, 2008 3:27 PM > *To:* flexcoders@yahoogroups.com > *Subject:* [flexcoders] DragEnter & DragExit trigger order > > > > In my experience, when you have two UIComponents (A & B) right next to > each other and you move your mouse from A to B you will get two events. > First, A will trigger a mouseOut event, and then B will trigger a mouseOver > event. But this order does not seem to hold true for analogous dragging > events. If I am dragging something and I move from A to B, first B will > trigger a dragEnter event and then A will trigger a dragExit event. > > So a few questions: > > Have others observed this same behavior? > > Is this the expected and correct behavior for dragging events? It doesn't > seem like it should be to me. > > Is there a workaround? > > > Thanks, > > Mac > > > ------------------------------------------ > Mac Sims > [EMAIL PROTECTED] > www.macsims.com > > >
