Skip to Main Content
Need Support? Let’s guide you to the right answer or agent.
Status Shipped
Categories 3D Modeling
Created by Guest
Created on Jan 27, 2021

Constraints: Option to retain Constraints on Copy

Transfered from EAP Ideas list
If Association Lock is set, then when a Constrained Element is copied, the attached Constraints are duplicated... Option to copy as disabled / suppressed Constraints.

  • Guest
    Reply
    |
    Sep 20, 2022

    Sorry guys for the late reply.

    Using OBD 9.2 (Mstn 16.3) Using the Copy command does retain the Constraints. This seems to work irrespective of the Association Lock. I think that this is OK for now but it would be better to have the option to copy without.


    Constraints lock: Maybe this is better as an option in the translate tools (Move, Rotate, Array) when have Copy options. This would pave the way for the more sophisticated options that the old Feature Modeling tools allow: Separate Copy, 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. Eg 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.


  • Guest
    Reply
    |
    Feb 26, 2021

    Hi Dominic, currently the copy does not copy the constraints anymore, meeting your original ask. If you want and if this is still important, I can create a new, separate idea for adding a "constraint" option in the association lock (enhancement 673735 as mentione by Regie) and close this one.

  • Guest
    Reply
    |
    Feb 23, 2021

    Marco Salino over 4 years ago

    Hi Dominic, we'll review this idea. In the meanwhile I am sure you know that, although you may not find this optimal, the constraints of the copied elements can be very quickly removed using the "Remove All Constraints" command.


    dominic SEAH over 3 years agoLooks like some work has been done.


    dominic SEAH over 3 years agocommunities.bentley.com/.../342688


    dominic SEAH over 3 years agoBut, yes I think that it would be good to take advantage of Mstn's longstanding Associative lock setting and not burden the model when copying or arraying constrained elements. I imagine that this will create a lot of info and bloat the file. I can see newbies and even oldies new to CE accidentally creating a lot of mischief. There should be a warning telling the user that he will be copying 'invisble' constraints as well.


    Reginald Wallace over 3 years ago

    Enhancement 673735 filed.