4
I Use This!
Activity Not Available

News

Posted over 14 years ago
All algorithms support orientation clockwise/counter clockwise Consistent argument order Doc update, not finished Realized: orientation (clockwise / counter clockwise) Moved to trunk The order is in 99% cases sufficient, there are a few cases left
Posted over 14 years ago
This was the version (tag) before namespace model:: Close/non close behaviour implemented (planned for 0.8) High arithmetic precision supported everywhere (planned for 0.8)
Posted over 15 years ago by [email protected]
fixed: It is at Boost SVN now and mirrored at GIT
Posted over 15 years ago
Version 0.6 is the first new stable version after acceptance
Posted over 15 years ago by [email protected]
fixed: I proposed is_simple but it leads (for the moment) to confusion. I've created an 'intersects' function that should check if two polygons intersect, and can also be used for one polygon to check self-intersections. You can use that one. ... [More] Alternatively you can now also call get_intersection_points with one polygon (and an intersection-point-vector) to get all self-intersection points. This is probably enough to close this ticket (I did) The behaviour of traverse should still be that it continues even with self-intersecting polygons but that is not yet implemented. [Less]
Posted over 15 years ago by [email protected]
fixed: Fixed. Closing.
Posted over 15 years ago by [email protected]
Trac ticket notifications test
Posted over 15 years ago
ASSERT when intersecting "criss-crossed" polygon with box
Posted about 16 years ago by [email protected]
Run GGL through Boost Inspect Tool
Posted about 16 years ago
fixed: Done