'pasting in' and reusing machining operations

[GoogleCodeExporter]

I'm probably missing this, if it's already done or David is working on it but:
Is it possible to copy the properties of a machining operation such as:
1. the tool used
2. clearance height
3. depth passes and final depth
4. step over and profile allowance 

Then take these properties and apply them to another piece of geometry or
even save these properties and use them in a fresh drawing/project to use
over again. I think that having to go in and change the start point and end
point of the op wouldn't be too bad, if all the other properties were
already there.
I know that you can do this in the python console (I've done it in a crude
way before) but I wonder if it's something that anyone's been working on
for the GUI in HeeksCNC?
This sort of thing speeds up operations a lot.
Thanks,
Dan

Original issue reported on code.google.com by ddfalck2...@yahoo.com on 27 Mar 2010 at 2:13

[GoogleCodeExporter]

Gidday Dan,

  I'm not working on this function.  I agree that it's a good idea.  I'm also hoping
that, now the graphics objects are children of the machine operations, we could 
add
some drag-n-drop or cut-n-paste functionality so that we could add and remove
graphics objects from the machine operations.

  I tried to do a cut and paste of a whole machine operation just then but it didn't
work.  I don't know why the cut and paste functionality doesn't work for machine
operations but that would be the first step.  If this worked, and we could 
add/remove
graphics objects from it then copying whole machine operations would be easy.  
We
could also add a menu option to just copy the parameters of the machine 
operation
instead of the whole thing (as you mentioned).

  I would expect that the cut and paste of whole machine operations would be easier
within the current framework.  My understanding of cut and paste is that the 
objects
are asked to generate XML in the same way they would if saving themselves to a 
file
but that XML is either written to a temporary file or held in memory.  When we 
do a
paste, it's like doing an import of this temporary XML data.  Would you 
consider it
just as easy to copy and paste a whole machine operation and then drag and drop 
the
graphics elements it's based on?  I believe that copying just the parameters 
would be
possible but the whole object might be easier to implement.

  What do you think?

  My vote is that we leave this issue open as an 'enhancement' and implement this
functionality.

  Thanks
  David Nicholls

Original comment by David.Ni...@gmail.com on 27 Mar 2010 at 10:29

[GoogleCodeExporter]

Copy and paste of any object should work.
I tried copying a pocket operation and doing "paste into", into "operations", 
and it
worked. However, just doing "paste" didn't work. I will look into this.
I agree that drag and drop would be good.
Because the tree control is written by me with OpenGL, it should be fairly easy 
for
me to implement drag and drop. 

Original comment by danhe...@gmail.com on 27 Mar 2010 at 10:43

• Changed state: Accepted

[GoogleCodeExporter]

I can also 'paste into' the 'operations' object. I'm not sure how to tag the new
pasted op to the sketch though.

Original comment by ddfalck2...@yahoo.com on 27 Mar 2010 at 11:11

[GoogleCodeExporter]

Ok,it does work :) This is how it works currently:

1. copy a machining operation
2. right click and 'paste into' into the operations tree
3. copy the new sketch that you want to machine
4. paste that into the new machining op that you just pasted into the 
operations tree

Original comment by ddfalck2...@yahoo.com on 27 Mar 2010 at 11:20

[GoogleCodeExporter]

Hi,

I've noticed a bug related to this when saving file with copied operations. If 
you
copy, say a profile operation, paste into the operations tree the new object 
does not
have a new ID. When you save the heeks file and reload it loses the operations 
with
the same id as the 'parent' operation. If you manually increment the 
operation's ID
the save works OK.

Thanks
Will

Original comment by williamr...@googlemail.com on 10 May 2010 at 10:45

[GoogleCodeExporter]

We need to be a little careful with the fix for this one.  Where a sketch is 
'copied'
and then 'paste_into' a machine operation, the fact that it doesn't update the 
object
ID is a great attribute.  We end up with multiple machine operations all 
relying on
the same sketch.

I agree that, when we copy a machine operation, there is no wish to retain a 
common
copy and so a new ID should be assigned.

I'm just saying that the update of the ID should be selective.  Good for 
Operations,
Bad for Sketches and other graphics.

Original comment by David.Ni...@gmail.com on 10 May 2010 at 11:05

[GoogleCodeExporter]

I think this got fixed ok.

Original comment by danhe...@gmail.com on 24 Mar 2014 at 4:54

• Changed state: Fixed