> that's what I was afraid of - anyone know of any other ways around it?
You'll have to create a new DragProxy class to change this behavior. To do this, you'll need to "monkey patch" (google it, you'll find it) the framework's DragProxy class. Once you do that, you can change the logic it uses for allowing a drop, or simply insert your "remove" code directly. Another option is to simply do the checking in addition to the work the DragManager does. So, when you start the drag operation, start listening on the stage (or SystemManager) for the mouse up event. When the mouse up event occurs, look at the currentTarget or target (or do a hitTest) to figure out where the mouse up occurred. If its in a "trash it" section of the screen, do the delete. You can also listen for mouse move and update the drag proxy cursor as it goes performing the same tests. Its the beauty of the event system, and the fact that (as far as I can remember) the DragProxy class isn't consuming the mouse events. Troy.
