Release 7.1.0
New Functionality
- New Overlay option
visibilityadded: use "hover" to specify that some overlay should only be visible when the mouse is hovering over the edge.


- Edge definitions in a view now support an optional
deleteButtonparameter, which instructs JsPlumb to show a delete button overlay on edges of that type that are rendered. You can also provide adeleteConfirmfunction, which JsPlumb will invoke whenever the user presses a delete button instead of the default behaviour of deleting the edge immediately.

- Edge definitions support a
deleteButtonLocationoptional parameter, which you can use to specify the location of one or more delete buttons on your edges.
As with everything in JsPlumb land, delete buttons can be easily styled via CSS. This is the default hover look and feel, for example, but you can easily change it by targeting the class .jtk-edge-delete:

Updates
-
We identified an opportunity to introduce a performance enhancement, particularly when ingesting large datasets. 7.1.0 can ingest large datasets significantly more quickly than either 7.0.0 or the 6.x versions.
-
In 7.1.0 we have reinstated switching on hover events by default. This functionality allows you to map mouseover/mouseout events to edges, and we disabled several versions when it was thought to be a performance hit, particularly in our Angular integration. We've since tracked those performance issues to being related to Angular's zone js (and fixed them!), and so we're reinstating hover events.
Further reading
-
Read about delete buttons for edges here: https://docs.jsplumbtoolkit.com/toolkit/7.x/lib/edges/removing-edges#showing-a-delete-button
-
Read about hiding/showing overlays automatically on hover here: https://docs.jsplumbtoolkit.com/toolkit/7.x/lib/overlays#showinghiding-on-hover
Start a free trial
Get in touch!
If you'd like to discuss any of the ideas/concepts in this article we'd love to hear from you - drop us a line at hello@jsplumbtoolkit.com.