Not appending (1) on nested copied objects in folders

When duplicating a folder, do not append (1) or any other suffix to child objects of that folder.

The problem that this feature will solve:

Makes object hierarchy much cleaner. Encourages the use of duplicate pieces.

I often create one object, put it in a folder, then reuse it a lot - seeing a folder called Hinge (6) is fine, but Hinge (6) > Bracket (6) > Leaf (6) > Pin (6) is irritating.

When it gets into an issue of modifying a nested object and re-duplicating it, it starts interfering with readability and name truncation. For example, splitting a body adds an asterisk - I’ve actually ended up with Bracket (4) * (1) * ** (1) before.

Brief description of the outcomes that you expect from this feature:

Helps keep complex projects organized, which is useful for professional use cases (especially when one project is shared between multiple users).

UX feature, for medium to power users.

What can’t you achieve without this feature?

This is not a workflow blocker. After a certain point I still have to work in Fusion 360, and this would help push that boundary out further.

This would make Shapr3D more appealing for larger, more complex projects. Makes Shapr more convincing sell to other CAD designers in-studio or prospective collaborators.


That’s a good suggestion :+1:

1 Like

Another +1 for this.
Shapr team, please consider this.

1 Like