ClipperOffset return erroneous ring hierarchy for negative offset.

[SuberFu]

ClipperOffset seems to return the wrong PolyTree structure when using negative offset.
https://jsfiddle.net/fdnhe938/3/

Note that with positive offset, the polytree's "IsHole" property matches the ring orientation (clockwise).
However, for negative offset, that's swapped.

JsFiddle output is in console.

[kheyse-autodesk]

I seem to have encountered the same problem.
What I also noticed is that the first child of the PolyTree is not actually the root node: PolyTree.GetFirst().Parent() != PolyTree but PolyTree.GetFirst().Parent().Parent() == PolyTree