Clipper Reviews

this one fails (in comparison with windows/region): Path p = new Path(); p.addRectangle(100, 100, 100, 100); subjects.add(p); p = new Path(); p.addRectangle(125, 100, 100, 100); subjects.add(p); p = new Path(); p.addRectangle(150, 150, 100, 100); clips.add(p); ops: xor + even_odd used 4.7.5 c#

This library is a clipper's dream and it comes with incredible support from author. Thank you Angus!

Superb library, very fast, well written, good license. Where is the donate button?

Incredible lib! I tried several others.And those were either lacking features or written so that it would be hard to port.This one rocks! Many thanks to the author!

Excellent library to use from C#. Easy to use, and very fast.

Incredibly fast and useful library, even coping well with very nasty closet cases such as edge overlaps. Of indispensable usefulness in the development of my games; if one of the commercial ones sees success, be expecting a nice donation.

some written writeup on the methods used would make it even better to use.

Using GIS data frequently encountered datastet cut up regular grid, and this library is not suitable for this. (see Open Discussion).

Brilliant piece of software stable fast and simple to implement.

This project has been a great help to me. In addition, you would like to ask you one question. The project has the following expression. "The code in this library is an extension of Bala Vatti's clipping algorithm" I would like to know specifically about this. In other words, I would like to know about the difference between your algoritm and Bala Vatti's clipping algorithm concretely. Reply would be appreciated. Thank you.

As soon as the Algorithm details are documented Vatti should be jumping that his ill written algorithm is being put to good use. handles polygons with overlapping edges ! --(There is problem in hole classification as of April 2014). The new releases handle polygon offsetting with a state of the art algorithm. This developer has a lot of energy which is good for end users like me.. The Developer should start writing the clipping algorithm in plain English. Program source is no substitute Angus should start writing a parralizable version.It can be terminated early but there is NO simple easy way to start with a late scan line.! The new version(only in delphi) is a work of art. Very good .Has used support edges much more effectively .

It's no secret that Clipper outperforms many other polygon clipper implementations, sometimes by an order of magnitude.