Clone node on drop

[notbear]

I'm trying to make an application where items can be copied from the palette to the canvas. For now gridpack supports only moving between grids. I hoped that it would be enough to remove line 785 from v0.2.5 which removes the source of element, but it leads to undesired behaviors when I try to copy the element from palette into canvas two or more times.

Example: http://codepen.io/NotBear/pen/EKyYqB/

Please advice

[troolee]

Try to unbind all events handlers and data attributes of cloned item

[notbear]

Thanks, I will try and let you know.

[kertonandrew]

Did you find a solution to the problem?

Edit: I'm cloning widgets from a palette similar to your example. After dropping a widget in my gridstack container the next widget I grab from the palette triggers an "out" event although it has never entered the droppable area. This occurs in your example too. I'm a bit of a js noob so not exactly sure why these events are occuring. Would greatly appreciate any pointers, I'll post my solution once I figure it out.

[notbear]

@attractivePoop I'm sorry, but not. My team resigned from gridstack due to changed requirements.

[kertonandrew]

Thank you for the response.

[mcelligottnick]

@troolee @attractivePoop I have solved this with a faux clone implmentation - https://gist.github.com/mcelligottnick/2d17a65615eb54b1c744050cb31ed028

[redstubble]

@troolee I am hitting this same issue. I have tried to unbind all attributes and events to no avail can you provide a snippet to point me in the right direction.

[radiolips]

We'll take a look at adding this ability into v.0.2.7 so that no hacky workaround will be required