At the moment, warping an SVG will essentially lock it's shapes and paths to whatever was there before passing it to warp.js. While possible, it's not easy to do certain things such as adding new shapes to a warped SVG, while removing them results in a memory leak.
New shapes should be normalised and added to the internal path data, while removed shapes should be discarded from the path data. Perhaps a refresh() method could query the SVG for all it's elements and compare it to what's in the path data?
At the moment, warping an SVG will essentially lock it's shapes and paths to whatever was there before passing it to warp.js. While possible, it's not easy to do certain things such as adding new shapes to a warped SVG, while removing them results in a memory leak.
New shapes should be normalised and added to the internal path data, while removed shapes should be discarded from the path data. Perhaps a
refresh()method could query the SVG for all it's elements and compare it to what's in the path data?