I wanted to quickly test the validity of creating a number of "VCarve / Engraving" toolpaths. So I hard coded some values and called a CreateVCarvingToolpath function linearly rather than in a loop.
An excerpt of the code is below. The CreateVCarvingToolpath function is hard coded to write a flat tool. This is just to show the names of the three toolpaths expected:
Code: Select all
CreateVCarvingToolpath(
"Test VCarve Rough 1",
0.0, 0.125, vbit_angle,
tool_dia, tool_stepdown,
tool_stepover_percent, tool_in_mm
)
CreateVCarvingToolpath(
"Test VCarve Rough 2",
0.125, 0.0625, vbit_angle,
tool_dia, tool_stepdown,
tool_stepover_percent, tool_in_mm
)
CreateVCarvingToolpath(
"Test VCarve Finish",
start_depth, flat_depth, vbit_angle,
tool_dia, tool_stepdown,
tool_stepover_percent, tool_in_mm
)
-- --
It adds the tools to the end of the list after the three exisiting toolpaths. Ignore the lack of a "...[Pocket]" toolpath as that's a known limitation that I hadn't compensated for.
The same code run in VCarve Pro v9.519 results in this image:
-- --
Each toolpath is added to the top of the list before the three existing toolpaths. After the three CreateVCarvingToolpath functions are run the toolpaths they create are in "reverse order"—although each end mill "[Pocket]" toolpath does come before its associated v-bit toolpath.
I can find nothing in the SDK PDF document (for the ver 9 series) indicating how to add the toolpath either at the end of the list or in the order they are created.
I don't really want to collect all the toolpaths into a stack / queue and bulk create them later using "last in first out" (LIFO) logic.
Any thoughts?
Steven