Chip & RC,
Part of the overlap seems to be in the negative part of the profile.
And lazyturn doesn't like that. Good scenario for checking out the tolerance acceptance for
the import though. Will follow your lead though and will try a few things and come up with a list
of what seems to work and not work.

I just added lines or a point above and below the profile, attached or detached by some distance for rejection before. Using another program for comparison, that one will take the profile but will only generate gcode for a single profile cut and only for acceptable parts of the profile. So you have an instant visual reference of something wrong at any point along the profile.

Maybe Lazyturn can do the same or similar thing as it goes through clash detection and stop at the point.
On the other hand, it could turn into being a PITA. Need to think about this some more.

Will spend some time tonight fooling around and will then post.
Rich

Art,

I like the sound of the segmented output but I think a snap point drag would be good so that small areas are not missed or a drag to next intersection.

Graham

Hi Art

I don't know if it is already been asked but Will there be the possibility to use more then one tool in a project?

Greetings:
Willem

Willem:
 
  Only as 1 tool for roughing, one for finish rough and one for finish..

Art

Hi All,
 ART, I must admit the importing is really good and have been trying to break it.

Hopefully the following will provide some insight into the forgiveness built into Lazyturn.

 LAZYTURN IMPORT OF DXF FILES -  CAD DRAWING ERRORS
1.A vertical line going up or down at the end of the profile is accepted but not required.
2.Additional elements  ie; multiple lines / one drawn under the other will cause an
  error " self intersection in master file" and no rendered graphics will be displayed.
3.Lines vertical or parrallel not connected to the profile ( even as close as .0001") are ignored.
4.A vertical line touching the profile will cause part of the profile to be ignored. The part ignored is
  is to the right of the line. If the line dosn't touch the profile then the line is ignored.
5.Two vertical lines touching the profile will cause rejection of profile to the left of the lines and
   acceptance of the profile to the right of the two lines. I didn't check to see what happens as the
   gap between the two vertical lines is increased to some value.
6.A break in the profile continuity on a straight horizontal line from .001" to about .11" still provides
  for a rendered image. With the break exceeding .11" to .2"  it acts as a break in the profile
  and the left side of the profile is accepted / is the beginning of the rendered profile.
7. Space between intersecting circles .001" to .1"  still allows for a rendered graohic but a
    horizontal line is created to complete the profile. Greater than .1" and the left side of the profile
    is created as if it was the start of the profile at zero.
8.LazyTurn will reject lines in the lower half of the profile ( similar to 3 above ) including lines drawn
   through the profile, but, no negative y values are allowed, and if they exist you will get an error
   message telling you so.
9.When partial circles ( arcs not touching / terminating at a common tangent point) overlap, the amount of
   overlap modifies the profile similar to #7 above. Starting at a overlap tail of approx .050" only a partial
   rendered profile will be produced. Note that #7 to #9 are for circles which would follow some basic shape
   formula, thus a continous profile can be generated. This may not be the case for a non basic
   shape / non generic  math formula.

I am sure there are others that you can find and list. Lazyturn is very tolerant and seems to allow for
many common errors but nothing beats doing it right the first time. Don't take this as gospel but rather
what my testing with the attached file found.

RICH
   

Hi Art

That means we have to make several G-code file's to make one project, for each tool a separate file and at last joint them together.

Greetings:
Willem

Willem:

   No, when its done, you will just select the three operations, one by one, and when posting the program will take care of making the entire GCode file. At the moment all you have is roughing, so you can only do th efirst stage...

Art

Hi Art

I am afraid that i did not expres myself good.
What i mean that sum shapes can not be cut with one tool in one pass.
As you can see on the screenshot the red area must be cut with a second tool.
this go's for roughing as well for finishing.

P.S.
Should the yellow square not be removed in this pass?

Greetings:
Willem

Willem:


 It should.. and Im still looking into a better algorithm to determine that.. Not as easy as it sounds to make that right on all profiles.. but Im getting close..



Art

Art,
What's your definition of the rough / finish pass?
Not sure you even need a second distinct step since it could be taken care of by tool selection and just posting.
IE; rough takes away the bulk stock as defined by slider / mouse selection / manual definition of extents with
whatever tool is chosen.  I would just create a tool with maybe different cut depths / parameters and rough away ( could be the same tool in the holder).
That roughing would be posted ( and if something were noted in the posted code, easy editing) . If the program were more advanced it maybe would tabulate / table  each of the steps your going thru and allow for modification to them.  
The finish is giving you the final profile tool passes based again on selected tool.

Can a different tool be selected for each of the three steps ( or will it be limited to first selected tool for
all of the steps?

Will any of the tools be usable for any of the steps?

I gather that your going to limit LazyTurn for the free version in some way and should you continue the
development would add additional features to it. As always, i remark that what is simple may be complex on the programing side.
 

A program can't anticipate what profile and combination of tools and steps the user will actually do to machine a profile.
Granted your not going to use a triangle to do a square groove, but, maybe someone will try, and tool misuse becomes apparent by the restriction of generated pass. Quess I'm just saying that a program shouldn't have to teach someone how to machine a profile. Even a simple profile could be machined numerous ways.

Just some thoughts,
RICH