Troy - drag events are dispatched to what _you_ attach them to. If you want the event to spawn from a child - but be handled by the parent... you should override addChild in the parent and attach the listener there. Your handler will be in the parent and each child will announce whatever event you attach to it at that level.
Rick Winscot -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Troy Gilbert Sent: Monday, April 14, 2008 11:56 PM To: [email protected] Subject: Re: [flexcoders] Letting parents handle drag events > So. are you _not_ using the dragSource, dragInitiator or draggedItem > provided by your drag/drop events? I would recommend that first before you > try to get list items to dispatch events. Uhm, I think you're missing my question. I'm trying to use all of those things, but I can't because I'm not getting the drag events. And this isn't an actual list component, it's a canvas full of controls (controls witch initiate the drag events) and another similar container full of these controls, and I need to detect when controls dragged from one are dragged onto controls in the other. And I'd prefer for the parent's owner to handle this instead of building the logic into the component itself. Just like I'd have it handle any other event (at least any other event that traverses the DisplayList, like a MouseEvent, which being the super class of DragEvent would imply that DragEvent works similarly, but it doesn't... > As for the second question, the mouse must participate in a drag/drop > operation - but the actual functionality of dragging and dropping is a lower > level operation that isn't directly tied to a components condition. If you > wanted to turn drag/drop off based on mouse enabled or something similar. > then all you had to do is check for myComponent.mouseEnabled with your drag > start event. and if this fails. event.preventDefault(). The point is that the drag events don't fire correctly *because* they don't work like mouse events, but they should. This is a known bug (in Adobe DB and confirmed) and I've already fixed it to a degree. Troy. ------------------------------------ -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.comYahoo! Groups Links
