Hi there,
I have noticed this odd behaviour: see attached video.
If you want to re-use a Frame Generator member in ANOTHER assembly to save creating more files you might want to use copy-paste.
If you do then you find you can't delete this member or other ones that have been copy-pasted into that assembly.
Oddly enough if you use "place component" you CAN delete it.
I am using Inventor Professional 2014 Service Pack 1 Update 1.
Any ideas would be helpful as a customer of mine is also experiencing this problem.
Thanks
Dan
Apologies, I couldn't attach the video, so here is a dropbox link:
https://www.dropbox.com/s/dpvtjhtc4x2re9t/Inventor%202014%20Frame%20Gen%20Delete.wmv
Dan
Not sure of the cause of this, but I have noticed this behavior with other Content Center parts. They do not react well to copy/paste functionality. In Tube & Pipe it is the same thing. I hate to sound like the old Dr. joke (Dr. it hurts when I do this... Then don't do that.)... but that seems to be the fix. Just don't copy and paste Content Center items in an assembly or between assemblies. Besides, where Frame Generator is concerned, trust me, it is beneficial to have your members be unique parts from one assembly to the next.
Chris Benner
Inventor Tube & Pipe, Vault Professional
Cad Tips Tricks & Workarounds | Twitter | LinkedIn
Autodesk University Classes:
Going With The Flow with Inventor Tube and Pipe | Increasing The Volume with Inventor Tube and Pipe | Power of the Autodesk Community | Getting to Know You | Inventor Styles & Standards |Managing Properties with Vault Professional | Vault Configuration | Vault - What is it & Why Do I Need It? | A Little Less Talk - Tube & Pipe Demo | Change Orders & Revisions - Vault, Inventor & AutoCAD | Authoring & Publishing Custom Content
I have found a way to delete the items out of your assembly.
Select all the items, right click, then component , then demote.
You can delete the newly created assembly.
This aint a fix but it gets it done.
Kind regards,
Leander Torres Falcato Simoes
Thanks for the response, I will have a go and get my customer to try that too.
It sounds like a fix for now.
Cheers
Dan
Same problem here.
The suggested work around is a messy one. Don't like it.
We are also on SP1 update 2.