Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.
First time visiting? Here are some places to start:- Looking for a certain topic? Check out the categories filter or use Search (upper right).
- Need support? Ask a question to our Community Support category.
- Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
- Be respectful, on topic and if you see a problem, Flag it.
If you would like to contact our Community Manager personally, feel free to send a private message or an email.
naming
rune_thorsen229
Member Posts: 179 ✭✭
Please make naming 'cascading' by letting new names being inherited from the generating process.
example:
I start with a sketch and give it a name, say 'gripper'
Then I extrude it, please let it inherit the name 'gripper' both as operation and resulting part so instead of the feature being named the useless 'Extrude #' then its called 'gripper' (anyway the icon tells what operation it is so calling it Extrude is redundant).
The resulting part should also inherit the name 'gripper' instead of 'Part #'
It would really make the documentation a hole lot easier.
example:
I start with a sketch and give it a name, say 'gripper'
Then I extrude it, please let it inherit the name 'gripper' both as operation and resulting part so instead of the feature being named the useless 'Extrude #' then its called 'gripper' (anyway the icon tells what operation it is so calling it Extrude is redundant).
The resulting part should also inherit the name 'gripper' instead of 'Part #'
It would really make the documentation a hole lot easier.
2
Comments
In a similar manner its very common to have a part made up of multiple extrudes, revolves, and other features. How would Onshape know which feature name to use for the part?
[Smart naming] / [Nerd naming]
Right now a boolean of multiple instances results in the name of last instance right?
Twitter: @onshapetricks & @babart1977
Maybe my proposal is not clear enough?
Perhaps I'm not understanding your suggestion properly, but this is how I imagine that it would work based on your description:
Lets say I have a sketch named "Gripper". From that, I extrude two different gripper paddles and hinge pin. In a separate sketch named "Ribs", I design a couple of ribs that would be used to stiffen the gripper paddles, and extrude the ribs so that they merge with the paddles. Now, following your suggestion, I have a hinge pin named "Gripper 3" and two gripper paddles named "Ribs 1" and "Ribs 2". If I understand your suggestion correctly, the smart names are actually misleading.
I'm certainly not against improvements, but I think a simplistic "feature gets the referenced sketch name" doesn't add much value because the relationship between features and sketches is not 1-to-1. An extrude could reference multiple sketches, and multiple extrude features could reference a single sketch. So, any naming logic would have to make so many assumptions that it could easily create names that are confusing.
Also, development resources being limited... I would prefer other improvements be prioritized over this one.
A group rename function would be much appreciated. Select all the parts and rename them according to a pattern. It may be possible to do this using a "multiple cursors" analogy (a cursor appears in the rename input field of each box, and your keyboard affects all the inputs simultaneously). Alternatively, the rename could be a simple pattern - enter "Stud" and the studs get renamed "Stud1", "Stud2", etc.