investigate why a new connection is created after drag

GoogleCodeExporter commented 8 years ago

upon successfully dropping a dragged connection, the source then discards that 
connection and creates a new one:

https://github.com/sporritt/jsPlumb/blob/master/js/1.4.0/jsPlumb-1.4.0-RC1.js#L2
517

this issue is here to remind me to figure out why this is necessary. it would 
be better if it were not. amongst other things, it is confusing for people 
using a beforeDrop callback, as they assume that the connection they are given 
will be the one that ends up getting added to the UI.  so if you change 
something on this connection during beforeDrop, those changes then disappear.

Original issue reported on code.google.com by simon.po...@gmail.com on 26 Feb 2013 at 10:40

GoogleCodeExporter commented 8 years ago

Stumbled upon this while trying to pass arguments using setParameters() and 
getParameters() on drag and before drop. It's nasty.

Original comment by mandro...@googlemail.com on 7 Mar 2013 at 8:50

GoogleCodeExporter commented 8 years ago

update: this only happens with the makeTarget method of configuring a target. 
it does not happen on an endpoint that is a target.

Original comment by simon.po...@gmail.com on 13 Mar 2013 at 9:40

GoogleCodeExporter commented 8 years ago

moved to github

https://github.com/sporritt/jsPlumb/issues/27

Original comment by simon.po...@gmail.com on 30 Apr 2013 at 11:37

GoogleCodeExporter commented 8 years ago

Issues have all moved to Github.  Google code is no longer in use for jsPlumb.

Original comment by simon.po...@gmail.com on 10 May 2013 at 11:37

Changed state: WontFix

jnobre / jsplumb

investigate why a new connection is created after drag #323