Never mind, resolved. DragProxy has a different function for selecting which object to dispatch drag/drop events through and they produce different results between 3.2 and 3.1 so after finding that out that we figured how to get it to route the events to the correct object.
--- In flexcoders@yahoogroups.com, "reflexactions" <reflexacti...@...> wrote: > > I have an app that been working fine under 3.0 and 3.1 for over a year, > its worked on by team of guys, now we have installed 3.2 and Drag/Drop > has stopped working for all of us. > > The app adds DragEnter/DragDrop events handlers to a Canvas that fills > the display area but whereas under 3.1 they get called under 3.2 they > are not. > > When we drag out of a list based component the cursor changes to the > drag cursor but with the red cross showing you can't drop, but the > event handlers on the canvas never get invoked so they dont get to call > DragManager.acceptDragDrop. > > Does anyone know what has changed between 3.1 and 3.2 that could cause > this, is there something else that needs to be turned on to detect > dragging? >
