Hi, Excuse me for late reply. This iso is tested ok with dvd install. This iso is not tested with usb install. I heard there was another person that had boot problems with this iso doing a usb install. It's problably solved when i do a grub-update before creating the squashfs filesystem. But the following iso is preffered : For example the Linux Pro is tested with usb install. This linux Pro iso can be found by clicking on the "maxus" name.
compiling problems on Linux debian 5.10.0-4-rt-amd64
Home
Home
Home
Now I'd love to learn just how is this library so fast and how can I speed up my code like this Through the desigh of the library with structures, retrieving data for the polytree in c++ looks impossible. After spending multiple day's to repair this, i stopped with it. Clipper looked fast for me when i started, now i can say it's not so fast for me... I did a few tests with the function intpoint. Wich checks if a point is inside a contour to retrieve a polytree myself. I implemented the Clipper library...
Now I'd love to learn just how is this library so fast and how can I speed up my code like this It's not so fast for me... I did a few tests with the function intpoint. Wich checks if a point is inside a contour to retrieve a polytree myself. I implemented the Clipper library in my c++ program. Did a speed test with clipper with the following speedtest.dxf drawing. My first clipper output was 120 seconds. Wich is horrible. After reviewing the code i came out at the following Clipper output: Clipper...
Program output : https://imgur.com/ci7gsVq
Program output : https://imgur.com/ci7gsVq
https://imgur.com/ci7gsVq
I implemented the Clipper library in my c++ program. Did a speed test with clipper with the following speedtest.dxf drawing. My first clipper output was 120 seconds. Wich is horrible. After reviewing the code i came out at the following Clipper output: Clipper output to find point inside contours : Output : 28 sec without making polytree Output : 37 sec with making polytree trough reverse engineering contour points. I decided to try something else... 7 lines of code... Sounds nice... https://wrf.ecse.rpi.edu/Research/Short_Notes/pnpoly.html#The%20C%20Code...
I found a dirty solution over here . https://stackoverflow.com/questions/58905767/memory-adress-output-instead-of-value/58944947#58944947
I guess your question is about getting a presision area output? Personally i do the area calculation outside of Clipper. So far as i can see Clipper uses polygon point's to calculate area. The Clipper area calculation is in my view an approx output. To get a more presize area output the polygon contour needs more points on the contour. For example, extra points on spline's, arc's, circles etc that are member of the contour. To get the extra point's you have to write some code. And after you digget...