automatically move WAVE-linked features to top of Model History tree? 1

[potrero]

NX6.0.1.5 MP1

When features are WAVE-linked into a part, they by default appear at the bottom of the Model History tree in the Part Navigator.

This isn't an annoyance if the WAVE links are made right at the beginning. But if you add WAVE links to a part after some features have already been made, and since a WAVE-linked feature is often being used as construction geometry, one often ends up dragging the copied entities up to the top of the tree, manually.

Is there a setting or method to have WAVE linked features inserted at the top of the tree? It'd just be a convenience thing... Maybe having a checkbox on the WAVE copy dialogue...

 

[JohnRBaker]

This is offered merely as 'Food for Thought':

Contrary to what many believe, experience has shown that it's difficult to make something truly easier to use simply by including a few additional options.


John R. Baker, P.E.
Product 'Evangelist'
Product Design Solutions
Siemens PLM Software Inc.
Cypress, CA

http://www.siemens.com/plm

http://www.plmworld.org/museum/

To an Engineer, the glass is twice as big as it needs to be.

 

[potrero]

John, good point. I didn't mean to sound flippant. I actually think this would be useful functionality.

 

[hudson888]

Two things I could add to this.

Firstly from bitter bitter experience Never Ever place a wave linked body the very first feature in you model. I often just have the datums before the first linked bodies. If they go horribly horribly screwed up in ways that can only be exacerbated by using teamcenter then it occasionally helps to be able to roll back the model behind them in order to more or less trick the system into allowing you to perform edits and swap out their dependencies on redundant data. Why exactly this occurs or how it works I can't offer a detail explanation to justify so for the moment it is just something I can offer as a tip that you might be glad one day to have heeded.

Secondly you can quite often reorder it quickly and easily while it is completely separate from the other features in the tree. I imagine that being on separate branches of the tree provides that the reordering can occur without re-evaluating all the features so long as there is at the time of re-ordering no association between linked bodies and other model features. If it is a bunch of sheets try grouping them first it may help.

Best Regards

Hudson

www.jamb.com.au

Nil Desperandum illegitimi non carborundum