Paste options for machining

Paste Special Reusing Pattern for drilling operations.

Currently when you copy-paste a drilling pattern the pattern object is duplicated. So I  always have to go back and change the linked pattern in every copy.  Big time waste.

Paste Special Without Geometry for all machining operations.

Yes you can use Tools->Options but that sucks. 40 seconds gone from my life each time I need it.

Paste of any sort that works for Rules, Checks, Actions and other KBE stuff.

You can't paste Rules or other KBE stuff in a process document. It is broken by design.  Basically I end up with all my standard reusable KBE objects in a part and link the results to machining using formulas. It is a tedious confusing waste of time and seems risky.

Hi Cliff,

I don't know about much about KBE stuff for machining. And here are my 2c on the other 2.

Paste Special Reusing Pattern for drilling operations.

It is a pain when dealing with drilling patterns after copy paste or even after MP instantiation. And deleting unused features doesn't help either. Swapping family of parts still doesn't update the link properly for formulas (used in App/Ret macro management) and patterns. I reported this problem about 2 years ago and still waiting for the fix.

Paste Special Without Geometry for all machining operations.

This would be extremely useful for all of us.

I would like to see all of the enhancments Cliff noted, get implemented one day.

This makes the point... 40 seconds...many times a day... adds up to real time, and causes frustration. Fixing them would bring joy!!!

:)   :)

 

Dave

Cliff, these are AWESOME ideas.  I really like them.  I'm also doing like you...always changing the pattern so they all link to the same pattern.  It is kind of a time waster- I just never thought about suggesting an enhancement, so glad you are mentioning it.

I've also asked for the ability to copy MO's without geometry.  It is a pain to have to go into tools options all the time.  Sometimes I'll keep a dummy process open in another window just so I can quickly "steal" MO's that work well from it.  Makes it a lot easier when you can look and see what geometry to pick, and what the MO does.  I do this instead of using the MP catalogue sometimes.

I like your ideas of just enhancing the copy-paste-special routine.  That would work really well. 

Since I am in a pissed off this morning about this I will add another...

Copy-Paste-Special without Ghost Links.

Did you ever notice that when you copy an operation from a different program, even after disabling "duplicate geometry links" there is a ghost link established between your current process and the copied-from process?

Initially you will see this in that Catia will ask you if you want to save the "modifed" copy-from process which was not modifed.

And then when you close the copy-from process, Catia will warn you that it is still active because it is still active.

And then when you save and close the copied-to process you are again warned about the unsaved modifed copy-from process?

And finally if you ever have the misfortune to do a File->Send To of a process built this way you are treated to pages and pages of references and links to NC assemblies long past. This is dispite these link not showing up on Edit->Links or File->Desk (where CATDUA does not remove the lnks) or Save Management.

OK I am not really serious about a new paste-special option in this case. This mess simply needs to be fixed. When I copy an operation I don't want ANY links to the previous geometry, process, or NC Assembly to be established.

 

Hi Cliff,

Thats why I prefer MPs over copy/pasting. Anyway there is catch to it and you have to clean the links manually.

I would like to see CATDUA enhanced so it can remove such missing links automatically.

Some of the ghost issues also have to do with tools options and where you allow Catia to look for related files. I only allow Catia to look in the same folder as the document. This has saved me a lot of trouble with messy links. Downside is you may have a lot of files in a single folder, but so what?