I just can't remember how to do it at present.
I want to be able to hide the features from the feature tree in the model in a sldprt, while the whole is still complete.
Need help jogging my memory.
You can use DEFEATURE ( Tools -> defeature ) for that.
Look what i've done with this part.
You can't hide the features in a part, you could create a derived part which could be updated from your original when edits are performed or lock / break links to prevent edits having an effect. You could also export the part and import it back in.
I seem to remember a way to do it in one file, without having to save as, import, or export it.
There it is!
When we need to do this for (sending out to customers/suppliers etc) the easiest way is to just save as a STEP file.
There an some more options to do this:
- Use the "Convert to Bodies..." command in the FeatureManager
- Write an Macro wich will hide any features in the FM:
Sub main() Set swApp = Application.SldWorks Dim swModel As ModelDoc2 Set swModel = swApp.ActiveDoc Dim swFeat As Feature Set swFeat = swModel.FirstFeature Do Until swFeat Is Nothing swFeat.SetUIState swUIStates_e.swIsHiddenInFeatureMgr, False Set swFeat = swFeat.GetNextFeature Loop swModel.ForceRebuild3 (False)
Admittedly, I avoid using macros and most specifically for things that have a function already in the SW.
There are few things I use macros for, one is the auto toggle/untoggle of selection through transparency with my RMB shortcuts.
Just out of curiosity, in what scenario do you use "Defeature"?
When and if I share a native SW file with any one outside of my organization. I hadn't been using and had forgotten the function of defeature because I rarely share a native SW file (usually a STP or Parasolid). Ultimately, Protects IP.
Some fairly large organizations I work with have entire departments dedicated to scrubbing their engineering doc's to protect IP.
So is that to say that "Defeature" cannot be reversed then? Even if they have the software Scott?
A valid point, Dave. The next user can run feature recognition and get whatever SW has chosen to determine the features were created. IP isn't just about the finished product but also the workflow and design process as well.
No offense to any one on the forum, if I have a method that saves myself and my company a lot of money in my workflow, I'm not likely going to share that with others. In fact, I don't even show all of my tricks to my coworkers.
The defeature tool also allows for horrible design intent to be hidden.
Don't get me wrong!
I wasn't making any criticism about your use of it, I purely didn't know anything about the feature or suitable situations whereby a person may want to use it. An educational question on my part...........
Good to know it can cover up all those extrudes I used when I should have just done a revolve lol.
Of Course, no criticism assumed.
I get you on hiding the extrudes and all... Sometimes we get so far into development that we might as well just leave it as a mess. As long as it can be built - hey, the drawing can cover it hahaha.
I recently did something against my own methods, and the quick and dirty would have and did taken the prize in that case. So, the right way is not always the... right way?!
Now who would ever do horrible design intent?
I just call it development.
It's a lot better than it was when I started all this stuff 12 months ago Jim, but still got a long way to go............. lol
Retrieving data ...