Tagging features

[Jacek_Mydlikows]

It would be usefull to create extra tags inside features.

This would have following advantages:

* better navigation in model tree

* faster understanding of model not created by us\

* simple managing/distribution of dimensions, parameters or attributes among tagged features

* first step to automation of model structure to implement some kind of model manager funcionality(more about it in separate thread)

This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

[Dale_Rosema]

Jacek Mydlikowski‌

You may want to vote on your own idea ......  

[dnordin]

Jacek,

Can't most of this be accomplished with existing functionality?

You can create a feature parameter that can be used to identify or tag the feature with a "name".

  * The parameter is searchable (Look For: Feature; Look by: Feature; Attributes Tab; Rule: Expression; Criteria: Type=String, Symbol=(your parameter name), Comparison=is equal to, Value=RIBS

  You can save the query for quick access.  You can filter the model tree based on the search.

  * The parameter creation can be automated with UDF's (embedded in the UDF)

  * The parameter can be displayed in the model tree as a column just as you have shown

  * The value can be set/edited in the model tree (if you don't use UDF's; not the easiest way to create feature parameters, but it works)

You can create feature/sketch relations that reference global parameters (via notebook) or even model parameters.

  * If you use UDF's for your features, it can be automated (assuming you already declared your notebook reference or the controlling model (not feature) parameter already exists).

  * If you're creating the feature relations on the fly, it's quite easy to select dims from the graphics area as well as selecting parameters (local or global) to include in the relation.  Relations can even be created on the fly.

One step to help with understanding the model created by others would be to implement & enforce feature naming, so your features have logical names instead of the default names of hole, mirror, group, etc.

If your trying to control multiple features via a single relation which is what it looks like in your example, you should investigate UDF's and notebook.