Add support for merged paths (M..Z M..Z M..Z)

[peteruithoven]

No description provided.

[wout]

Any questions?
:)

[peteruithoven]

No... I'm just used to using issues as todo's ;)

[wout]

LOL :)

[wout]

Quick question, how about you becoming a collaborator on this plugin? That way you don't have to send out pull requests every time.

[peteruithoven]

That would be nice :)

[wout]

Done!
:)

[wout]

Just wondering, how would you solve this? I was thinking that in case of more than one path, a group is created wrapping the individual polygon / polyline elements. That way the converted shape can be moved as a whole.

[peteruithoven]

Interesting issue, mainly what to return is tricky right?
I was thinking of using an array or svg.js set. But when your editing I agree that it would be nice to have these formally merged paths grouped.
Your solution will also work nicely with the ungroup plugin I hope to write.
It will require a warning in the docs anyway I think (that it can also return a group reference).

[wout]

An instance of SVG.Set would also work. Although, calling move() on a set will move all parts to the given x and y by their upper left corner. So in that case a group provides more expected behaviour when manipulating afterwards.

About the ungroup plugin, I would accept this feature to the core. Maybe a good one to add to the list of rc.11 when the new matrix transformations are implemented in rc.10.

[peteruithoven]

Nice, I've been reading the references readme already.

[wout]

Great :)
Just a tip, if you clone the reference branch and run gulp docs, the REAME will be converted to the more readable documentup layout.

[afocus]

Are there any progress?
This is a useful feature...

[Fuzzyma]

Your best approach would be to split your path at M commands and convert them to polygons one by one.