Reporting Issues

[AngusJohnson]

Please only report probable bugs in Issues, otherwise post your questions here. (And unless you're pretty familiar with Clipper2, what you suspect is a bug probably isn't because Clipper2 is now pretty stable.)

All questions and feature requests etc should also be done here in Discussion. This is mostly because others are likely to have the same questions. When you ask questions in Issues, and I answer and close them there, no one else will see my answers. Consequently I'm likely to get the same questions again, and answering them again when I'd much rather be coding 😁. (Edit: Discussions can be closed too, though most don't bother, and I'd prefer that they aren't for the reason I've just mentioned.)

Because Clipper2 isn't written in just one language, when posting code samples it's really helpful if you don't make it too language specific (especially as I mostly debug using Delphi).

So with that in mind:
1. paste polygon samples using integer or float arrays, and without {} or (), see examples here.
2. don't forget to state both the clip type (intersection, union etc) and the polygon fill rule (EvenOdd, NonZero etc), unless the issue is about polygon offsetting (where offset deltas, join and end types are needed).
3. keep the code compact (pseudo-code is fine too)
4. as well as a small data sample, it will often help if you paste an image or two that shows the problem.
5. please don't post very long data samples. Simplify samples as much as possible, and if it's still several KB, post it as an attachment.
7. I get a lot of emails (not just about Clipper), so please don't email me directly requesting help.