Fix issue with convertPathData with sequential h or v movements

Quick test and fix for convertPathData when a path has movements in h or v in opposite directions-

eg:

```
M10 50h30h-30
```
would produce

```
M10 50h0
```