thank you very very ………………very much

Well, following my example above, the Panel are the drag source elements, so they would listen for mouseDown. You would need to have some parent container to act as the drag target that listens for dragEnter and dragDrop. Lastly, I’d recommend a custom layout applied to the parent container to handle the positioning of the dropped Panels.

Good luck.

Can you tell me how to achieve this?

Now… Upon validation of the dragSource the drop target state goes from normal to dropYes, and dropNo if it doesn’t validate.

I’ll check your others posts to see if I can manage that.

Thanks.

Thanks for reading, but I must be missing something, because when I compare the “Manually adding drag-and-drop support” pages (Flex 4 vs. Flex 3) they look very similar to me, including the dragExit and dragOver events.

Also, both Flex 3 and Flex 4 do not support copy. The Flex 3 docs say here, “The list-based controls can automate all of the drag-and-drop operation except for when you copy the drag data to the drop target…Flex leaves it to you to implement object copying…”

Lastly, Flex 4 isn’t fully baked yet, so who really knows what works and what does not.

When adding a element to a container it removes it from it’s origin container. So, we can’t copy an element by dragging it to an other container.

I’m using Beta 2 and the DragDropProxy Square and Circle didn’t showed-up at first. Seem that the 100% for width and height were the cause. Set them to 80 and it worked. I’ll see if there is another way to correct that.

By the way. Custom Drag And Drop support isn’t unchanged. We are missing some methods like dragExit() ans dragOver(). We can declare them in object but they are not fired. I have some Flex 3 components that used dragExit to set their visual state back to normal.