Add dragging and methods to a list of objects

sleaman wrote:

I’ve tried running the list through a for loop and assigning the drag functionality to each element, but it applies the drag to the last element in the list. I assume this is because each loop writes over the drag function rather than adds to it…

You’re mostly right. This is a common issue with such puzzles as “when dragged over” being used in a loop.

You’re probably using the loop’s counter variable to reference objects inside the “move do” or the other slots. It makes “when dragged over” rely on the counter’s value at the moment you start dragging. But the loop is executed immediately and when it’s over its counter’s value equals to the last element.

In the end you have dragging registered on every object from the list, that’s great, but sadly they all will drag the same object that happened to be the last.

There’s a standard workaround to deal with this situation. You should extract “when dragged over” puzzle into a separate procedure as follows:

Ivan Lyubovnikov wrote:

There’s a standard workaround to deal with this situation. You should extract “when dragged over” puzzle into a separate procedure as follows:

oh man this just got me out of a rut with this issue.

thanks!

sleaman wrote:

on drag drop

Note: if you drop two or more objects with the same name only one of them will be draggable. The rename object puzzle is needed.