I think shapely didn't measure distance to boundary, but to any point in
the chunk, which could lead to wrong sorting in outliefill. Now it
measures the distance to boundary.
The user no longer has to apply modifiers to a mesh before calculating a
cam operation. If user option "use mesh modifiers" is enabled then a
temporary mesh is created with all modifiers applied.
This has not been tested with OpenCamlib.
- rampZigZag() was being used as a function that returned a chunk object
when in fact it returned nothing. Its a chunk object method that works
directly on the chunk.
Also when paths are trimmed due to depth or limit curve. Similar
approach could be used for other non-sorted 3d strategies.
Especially good with ZigZag - Meander movements.
This speeds up greatly finding of parent/child in pockets, outlinefill,
and probably more.
Pockets with many independent shapes were ultra-slow, not really
measurable, now should be usable....
Now meshes can generate autobridges too,
and many 3d operations have bridges enabled, some will not work yet
probably, but only the experimental ones...
This is a sortof big change, because object based silhouette wasn't
stable and fast enough so far. Now it is enabled for meshes that have
less than 200k faces. This means precise silhouettes in many operations.
E.g. outlinefill now works much better. Remember, there is still a small
imprecision in the whole computation, because all faces get extended by
about 0.001 mm
found a bug in silhouette offsetting and realized that buffering the
triangles actually works much faster, the optimization is exponential -
1300faces 1.27sec vs 2.34(original), 12k faces 13.6s vs 99.5secons(orig)
didn't test for larger meshes.
-revert new parallel pattern algo, isn't finished yet(parallel stepback
problem)
-curves, text, can now be used also if parented
-scan tools remove small parts tool.
When adding new featuers, the default behaviour should always be so that
things work like before by default... Please don't assume more users
will want a new behaviour, and not noticing this might be dangerous for
users who are used to a certain behaviour.
If experimental is disabled in addon properties then disable the
following:
- first down for pocket and medial axis operation
- gcode header and trailer
- tool change overides
- block numbering overrides
Moved the shape basically 5 meters away from center, should be ok now.
It was a stupid bug, the shape was supposed to be 100 meters of, but the
scene was scaling too for the collisions, to improve precision.
Resorting a collection of chunks would yield different results than the
first sort. This was caused by adaptdist changing the order of the
points on a chunk that had already been sorted earlier.
- block numbers can be enabled/disabled in gcode output. the starting
number and increment value can also be set
- Tool change commands output can be controlled along with G43
added the following post processor override options:
- output block numbers
- output tool definitions
- output tool change commands
- output g43 on tool change command
- output a user defined g-code header for an operation
- output a user defined g-code trailer for an operation
Prepared geometery not setup properly so reverting to using basic
geometry object collision for now.
allpoly would have to be setup as a prepared geometry and not a Polygon
at the begining before entering the collision check loop. disjoint
method is for Geometry objects and not for prepared geometry.
Jroc