Traumflug

> Is there workaround using polygons? Yes. Two of them: 1. Change your design to not have polygons. When milling with Voronoi paths, polygons make not too much sense anyways....

Where is your patch / pull request?

I run Ubuntu 16.04 here, too, and Visolate works. Just tested releases 3.0.1, 3.1, 3.0.1, 3.1 and 3.1.1. All of them show at least the initial window with the test...

Looking at these stack traces, I can't see any Visolate code involved. Whatever is there, it happens inside Java3D. It might be a misalignment between J3D and your video driver...

I guess it's a known limitation and/or missing feature. To get these Voronoi color fields, Visolate draws a frustum/truncated cone around each track an each pad, then views the result...

> i think it means that instead of voronoi i will have to stick with the outline style tracks. Not neccessarily. Voronoi paths around two rectangular pads are the same...

> i could change the 1206 footprint to have circles instead of rectangles Ovals, not circles. Just like a short piece of track. I think this is doable. It's likely...

Sucking at coding isn't a permanent property. People learn by doing; so will you ;-) As said, modifying the geometry as part of fixing topology is probably the wrong approach....

Yes, start- and end-gcode read from a file is an excellent idea. Movements above the PCB surface should be at travel/rapid speed already, written out as G0. Is there a...

G0 and F don't really work together. G0 means "as fast as possible" and that's different on distinct machines/printers. At least Teacup firmware ignores a F on G0 moves and...