When one runs HitDataVector getIntersections with a single path that winds around and crosses itself one or more times, the number of HitData records returned is equal to the number of times the path intersects itself, but the contents of each record is the same, representing the first intersection only. I suspect this is not the intended behavior, as it would be much more useful if it returned each "crossing" in order, from beginning to end.
You're right. It should work the way you describe. I've added it to the list for a future version, but cannot promise when it will become available.
As of CORE 0.7.4, PathArt::getIntersections() correctly returns every location where a path crosses itself, but only the lowest-index segment is recognized. That is, the info for the intersection at the second pass is a duplicate of the first-pass intersection. Temporarily reversing the path would probably be a suitable workaround in most cases, though.
Thanks Rick, for the suggestion. We'll consider it for a future release.
Brendon