Hi Guys:
( Thx to Hood for letting me know this thread was running.

The Turn section of Lazycam is hard to use, LazyCam itself can be a bear, but its a project that was in progress
when I left. Its not something Brians continuing as yet, its on a back burner at best. While Im retired its my plan to update
both. LazyTurn is the first thing that has to be done , and at that point Turn will be removed totally from LazyCam, and LazyTurns
import mechanics will be put into LazyCam.
LazyTurn is a complete rewrite in most area's. Code has been tightened, imports made more fully compatible, and the process
of doing the toolpaths is still in progress. Turning is HARD, very HARD. When you search for a turn cam program and find most
of them lacking or very expensive..thats why.
LazyCam is long overdue, and it will be awhile yet before it gets touched, but LazyTurn continues. Slowly because of timing.
I dont code much in Summer, and Im the sole coder for it. Winter is my coding time as there isnt much else to do up here in the
winter of Canda if your not into ski'ing or snowmobiling.

( I hate cold).
Im close to a completing roughing profile, but had to do a rewite last couple months as I had neglected to take a few gouging items into account... like
the last pass through the stocks effect on the next pass.
LazyCam DOES have variables unexplained. The reason is that the licensed code I originally used for turning was undocumented, and very hard
to get to work. ( lesson learned, Im writing my own code for all those turning sections in LazyTurn, which is why its so slow going..only if
youve attempting writing such code can you fully experience the pain. Originally LCam was my attempt at getting enough cam product to
as many people as possible at as low a cost as possible. Hence all the licensed code in it. The DXF import was licensed and didnt do as Id hoped as well,
but recent fixes to it from the authors have made it much more usefull, though still not perfect imo.
In short, I learned many lessons from Lazycam, first, you cant do it by licensing modules from others and tying it all together, many code
problems existed and Ive learned allot about how to handle many things we originally couldnt deal with. So .. if I can finish up LTurn to
get it to the output stage this winter, then LCAm will start to see some changes to remove Turn, and convert the UI to somethign much more easily
handled,and LTurns import code will be ported over. Ill likely use my own pocketing routines as well, the ones I licensed for it seem way to sensitive
to tolerances and screw up in strange ways.
Really hard to explain to the user exactly why, as the licensed code is huge and undoced so even as the coder I cant explain some of its pecadillos..
It remains simply a cheap alternative to more expensive cam programs, and then only if you try it and can control it.
( Just thought Id kick in and let you know some of the why's here..)
Art