Associativity between models with Toggle Inheritance option

[YLocatelli]

Hello,

I noticed that when we use the function ''Merge/Inheritance'', we can activate the option ''Toggle Inheritance''. This allows to integrate the copied functions in the model tree of the part and the associativity link between the reference model and the part remains established. In case of changes in the reference model, the part can be updated with a regeneration.

Unfortunately, it is only in this way. If the part is modified, the reference model will not be corrected.

Are there any improvements planned in this case?

Best regards.

[tbraxton]

For inheritance features: Changes in the reference part are associatively propagated to the dependent Inheritance feature when both reference and target parts are in the same session. You can control whether Inheritance features are dependent on the reference part.

In your reference to the verb 'toggle" are you using it to describe this action? 

Click to toggle between Merge mode (default) and Inheritance mode for the feature.

If so you are changing the feature from a merge to an inheritance feature. It is not clear what your expectations would be for enhancements to this?

[YLocatelli]

Hi tbraxton,

Thank you for your answer.
The option ''Toggle inheritance'' is available in the function ''Merge/inheritance'' (see image Toggle_Inheritance) and allows to import the functions of the base model in the model tree of the part (see image Model_Tree).

Unfortunately, if we modify the functions in the part, the base model is not updated (see image Modifications).The associativity is unidirectional and this creates differences between the base models and the parts. 

[kdirth]

Inheritance brings in all of the features of the inherited model.  This allows you to make changes to the inheritance, but not the original model, in the part.  Any changes to the original model will update in the inheritance.  It is not a "two way street."

I use this function regularly for molded families of parts.  The base model includes all of the possible features (mold inserts).  Each model variation inherits the base model and individual features are either suppressed or unsuppressed in the inheritance.

[tbraxton]

I suspect there is some confusion about what merge and inheritance features are designed to do. There is a difference between the two and it is deliberate. One needs to consider your design intent and the parent/child paradigm to use them effectively.

This is a very broad characterization of the difference between them.

The Merge/Inheritance feature is a method to incorporate one complete model into another model.  The result is a single feature added to the target part.  When setting the feature to the Merge option, no changes are allowed in the new part.  The Inheritance option allows access to the individual features, enabling you to edit the Inheritance feature in a derivative part.

For much more detail refer to this document explaining some differences and applications. This is an HTML document of material I authored 20 years ago but the information is still valid today and provides some details of how to use inheritance features. Review this material and then decide if an inheritance feature is appropriate to propagate your design intent or not.

[tbraxton · Accepted solution]

My  TLDR response is the following:

The inheritance feature enables changes to a derivative model while maintaining one-way associativity with the parent object. The inheritance feature creates a one-way associative link of geometry and feature information from the base model to the derivative model. This resolves the problem of accessing the master model from within a derivative part and also provides direct access to features within the inheritance feature.

[YLocatelli]

Hello,
Thank you for your answer. Yes, indeed the difference between Merge and inheritance functions was a bit confusing.
Now I understood that this function allows to link two models between them (parent/child) and that the one-way associativity is deliberate and not an option.

Thanks @tbraxton for the documents and additional info. It is very well explained.

Best regards.