Has anyone made a Macro to do this....?

[Slagathor]

I am working with design tables for fairly large parts. 150-250 features.....

The DT approach we are using utilizes a lot of varying supression state combinations. When you create a DT for part with this many features..SW often jumbles the order of the features...leaves some out, etc. Getting them straight is a nightmare...especially with the goofy 90 degree text rotation....

I set up the feature tree using folders for organization. It would be awesome if there were a simple way to export the feature tree name data to a text file...in the same order as they appear on the tree. This would save tons of time, and reduce errors a lot.

Ideally, the out text file would look like this....

Folder 1
Feature A: Revolve
Feature B: Cut-Extrude
Feature C: Surface-Extrude
Feature D: Split Line
Feature E: Ruled Surface
Feature F: Surface Extend
Feature G: Surface Cut

Folder 2
Feature H: Boss-Extrude
Feature I: Cut-Extrude
Feature J: Surface-Extrude
Feature K: Split Line


Folder 1, Folder 2, Feature A, etc...are names that I give features. This is the naming convention I used to keep info straight on huge Design tables.

Basically...just go down the feature tree...and output the name list. I dont need to go deep into absorbed features....basically just the first level (if you consider a folder 1st level...then in that case...2nd level...)

 

[CorBlimeyLimey]

SW often jumbles the order of the features...leaves some out, etc

The features are being re-arranged or left out in/from the Feature Manager, or the DT?

Does the order of features in the DT match the order required in the FM?

 

[Slagathor]

Yes. Some small sections are in order...but then the rest is all jumbled up. When you have 100 features...this can get to be a real pain...

 

[CorBlimeyLimey]

Are you able to post a sample part for review and testing?

 

[Slagathor]

CBL,

Can't share the model. Proprietary.

Thanks for the offer, though.

-Brant

 

[CorBlimeyLimey]

Can you not create a dummy example or drastically change (add and remove features) a proprietary one beyond recognition?

 

[Slagathor]

CBL,

The issue is that it has so many features.... Simple models do not behave this way. This is a master model that could drive hundreds of future models....so it is very complex. I just cant see re-creating this...

I guess I will just learn Macros. Thanks for offering to help.

 

[CorBlimeyLimey]

Till a macro is created, you could take a series of screenshots to capture the FM tree.