Connect - Persistent Constraints after Feature Removal

When I remove a feature from my parametric model any constraints that were used to create the feature do not get removed.  Is this WAD?

I would expect that when a feature is removed any constraints that were attached to the profile under it would also be removed.  In this case it was a profile that was protruded... I cannot remove the profile first then the protrusion, but once the protrusion is removed the profile doesn't become visible.  It's a bit cumbersome to have to chase down all of the constraints and remove them manually without accidently grabbing a good constraint.  I attempted to compress the file thinking maybe there was an option to remove "unused constraints" but I didn't see one.

Model before feature is removed.

Model after feature is removed.

Test File, Remove tie rod extension protrusion in the 2A-TB_1-6in Bore model.

1524.2A-TB.dgn

  • How are you deleting the feature in the solid?

    The dimensions that you are seeing after you delete the feature seem to be tied the profile used for the protrusion feature. This behavior would be consistent if you were only deleting the feature, for the dimensions to be deleted the source profile would have to be deleted.

    I was able to get the dimensions to delete automatically by doing the following:
    1. select the solid and open the properties dialog.
    2. expanding the selection under protrusion(rod extension) right click on the Protrusion profile #24 and select Show Input Element.
    3. select the profile and delete it.

    You may have left over features listed in the Properties dialog.

    The proper workflow would be to use the "Delete Solid Feature" tool as this tool deletes the profile and feature in one action.

    Answer Verified By: Grant Wood 

  • More Parametric Solids UI polish... ASAP, please?

    1. Mstn should be able to highlight the 'dangling' dimensional etc constraints when a feature is deleted. Mstn already highligths dimensions that have lost their associativity... this is closely related and expected behaviour.

    2. Delete (and other Mods) need to make use of the 'fearure tree' in the Properties Panel. It would be good to have some a means to filter the dangling relationships in the PP.

    3. The dangling dims/constraints should NOT be automatically deleted. They often times need to be re-attached to the revised profiles. Auto-delete would be OK, if the user is askd for confirmation and the selected redundant constraints are presented to the user to allow him to de-select the ones that are to be re-purposed.

    4. Mstn should also provide the means to help the user update any 'dangling' Variables as well. These will more than likely need to be cleaned up as well...

    5. Also, a way of stepping through the 'history tree' like GC or SW's 'divider' line would be pretty essential. With the history/procedural MCAD-style way that PS works... its essential that the user has good UI tools to allow him/her to step through the 'script'

  • Thanks for your suggestion Dominic, we are always looking at ways of improving the UI and all of our users' feedback is important.

    Currently the constraints associated to an element that is deleted are also deleted as it is possible to replace an input element of a feature and this should automatically update its constraints. You can do this using the "replace input element" from the feature glyph or from its properties in the tree.

    I have noted your suggestions and we'll keep it in mind for our future releases.

    Thanks,
    Marco
  • This behavior seems the opposite of intuitive but I can live with it.