Hi:
For all intents and purposes there is no real good reason, a radius of .0005 is effectively 0.0 in real world terms. It means an error tolerance of .001 ( inch or mm) in a
profile, so it has no real effect. Internally however, I just have to ensure low values are treated fairly for the sake of stability.
Questions like this one go to stability in the end, and the theory of "If they CAN break it, they WILL" , which is somethign I have learned over the past
few years. It was my decision early on in LTurn to allow for this, and to profit from it by allowing it to be broken, shut off each avenue as I can, and then
I wont have to worry so much about support. In Mach3 I quite often use the axiom that "If it hurts to laugh,..dont laugh.." , but in LazyTurn I want people
to go ahead and break it if they like, if I can shut off that door, I will, and hopefully we'l have much less support questions from things that shouldnt be done, because internally
the program will correct whats wrong before you see it.
One of the reasons for example that more files now load, is that I change them as they come in , or just tell
you that they wont load. The program now "AutoTolerates" so that lines that dont join, automatically stitch
together as long as it doesnt create discontinuities in the math functions. This means the program will try a
tolerance of .1 for example, and if it finds that this creates a conflict, it will jump back and set the toleance
to .01 and try again, then .001 etc.. until it either solves the problem, or rejects the file.
By the time LazyTurn is complete, I will be very well armed to tackle some of these type of issues in LazyCam
which suffers greatly from tolerance issues. These sort of notifications therefore go toward educating me on the issues,
and even if they sound kinda crazy at times, they actuall do have their place in the scheme of things.
:-)
Art