Aquileo | Recent changes to bugs

Aquileo | Old tarballs not available anymore

Fri, 05 Aug 2022 10:36:57 -0000

All tarballs have been removed from Files, except latest release. It's not very convenient for package managers which have to build from source old versions (for example Assimp depends on clipper 4.x only).

Could you restore these tarballs please? And eventually, it would be awesome if you could provide tarballs of each release, with a stable url (and checksum).

Thanks

Aquileo | #213 Some Delphi 7 issues

Sat, 26 Mar 2022 07:32:56 -0000

Sorry, I have still sourceforge in my mind. Maybe you should empty it and make a link on github.

Aquileo | #213 Some Delphi 7 issues

Sat, 26 Mar 2022 00:58:10 -0000

Hi again Ralf.

Thanks for reporting this. I'll fix it in the next upload.
(That might be a few more days as I'm currently occupied with merging touching polygons in clipping solutions. I've had many attempts at this - to do it relatively simply and without a significant performance load - but this time I think/hope I've finally got it nailed.)

Clipper2Lib issues should probably go to Github.

Yes, I'd prefer all Clipper2 feedback here please.

Aquileo | #213 Some Delphi 7 issues

Fri, 25 Mar 2022 23:19:09 -0000

Clipper2Lib issues should probably go to Github.

Aquileo | #213 Some Delphi 7 issues

Fri, 25 Mar 2022 20:16:26 -0000

Refers to Clipper 2.

Aquileo | Some Delphi 7 issues

Fri, 25 Mar 2022 20:13:55 -0000

1) File saved as Unicode
ï»¿unit Clipper.Core;

korr:
unit Clipper.Core;

2) Delphi 7: Invalid type cast
Result := Result +
double((path[j].Y + path[i].Y)) * (path[j].X - path[i].X);

korr:
Result := Result +
(path[j].Y + path[i].Y) * (path[j].X - path[i].X);

3) Delphi 7: Invalid type cast
Result := Result +
double(op2.Prev.Pt.Y + op2.Pt.Y) * (op2.Prev.Pt.X - op2.Pt.X);

korr:
Result := Result +
(op2.Prev.Pt.Y + op2.Pt.Y) * (op2.Prev.Pt.X - op2.Pt.X);

Aquileo | #212 Wrong output when using ctDifference

Fri, 04 Mar 2022 21:57:09 -0000

status: open --> closed

Aquileo | #212 Wrong output when using ctDifference

Fri, 04 Mar 2022 16:08:56 -0000

I didn't know that it only works with integers. I rewrite the codes and it works! Thank you!

Aquileo | #212 Wrong output when using ctDifference

Wed, 02 Mar 2022 02:21:27 -0000

To be clearer, ClipperLib works with integers. You'll need to scale up your geometry so that the minimum resolution sits on an integer interval (e.g. if you need to represent 0.001, you'll need to scale all of your geometry by at least 1000). You can then use this scaled geometry with ClipperLib and scale the result back down again afterwards.

The main reason for this is to avoid errors from floating point precision.

Aquileo | #212 Wrong output when using ctDifference

Tue, 01 Mar 2022 23:56:09 -0000

I think you'll find that if you sensibly scale your polygons, you'll get the result you're expecting.