Copying parametric solids and their associated Constraints is going to quite common. Even just to make a copy to experiment and compare variants will be a regular thing. Selecting the solids and using the regular copy command seems to retain the Constraints so that the user does have to start over. Bravo.

Instead of having Constraints or Associative lock to control whether the Constraints are copied: Maybe the better option would be to add some option boxes to the translate tools (Move, Rotate, Mirror, Array). This would pave the way for the more sophisticated options that will be consistent with the old Feature Modeling tools' Separate Copy, Associative Copy.

• Copy w Constraints

• Associative Copy

Associative Copy would be good to have. This would be analogous to the way Revit's Load into Project works. When a user changes the parametric object, he has to constantly re-load the object into his model to check that it works.

So, when a Mstn user is tweaking a leg object in the active model that is part of a table, he will expect the other legs in the model to update when he is done with the tweaks. Advantage over Revit is that the Mstn user would not have to change context (ie exit / re-enter the Family Editor).