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.
Comments
Extrudes...
Lofts...
These are just a few things I currently use when doing some parent/child type troubleshooting...
I would like to see similar functions when selecting/hovering parts from part list.
- the feature tree showing the sequence of creating all parts.
- the parts tree showing all parts and the related features (which you don't show yet) creating them.
Today you show that in onshape already but just in one level in each tree. When you now look at the workflow you initially start inside the feature tree creating the initial parts. But when you have more than 10-20 parts you most likely switch more to working with the parts tree because you adjust and modify parts that "fit" together.The key here is to provide the right context UI based on selection. Today I can select a part in the workspace and in the feature tree the lastest feature performed on that part is highlighted. And in the parts tree the part is highlighted. But the problem is I could have created features related to a part out of sequence. I created a feature on one part and jumped to the next one and back. Now the feature tree is tough to navigate when I'm looking for what features modified a part. That is why the part tree should show all related features that created that part.
That said here is the set of features I would like to see for both trees.
Feature tree:
- enable tagging; some of it you already do by naming (Sketch, Extrude, etc.) but allow user to create their own tags.
- provide filter capabilities such as:
Parts tree:- show creation features only (no sketches)
- show sketches only
- show features filtered by tags
- Below each part show the features in sequence that created or manipulated it.
- Allow user to tag parts.
- Allow to insert other part studios
This also brings up the issue to were do you draw the line in regard to Part Studio versa Assembly. I can't modify parts in assemblies and I think that should stay that way. But I need to be able to modify parts from multiple Part Studios in the same place. And that I can't do today in onshape.So besides allowing grouping for parts inside part studios I also should be able to "import/show" other part studios in my part tree.
Another issue are boolean operations that merge or split parts. The feature tree is simple for that since it just show the sequence of manipulation opoerations. For the parts tree that becomes a bit more complicated since you now created or removed parts. One way to solve that is for a merge the new part has now a set of grayed out parts below it with their features that created it. And the first feature on that new part is the boolean feature. For a split each of the new parts has one sub part from which it split off. Now this is simple for one level of splits or merges but when you have lets say 5 of these nested it becomes very complicated to comprehend. So I would always display the latest only and hide any other levels under "...".
On a last note hierachical tress are a good thing as long as you limit the amount of levels you enable. Most people (except engineers) don't think in hierachies. They more think like tagging works. These 5 parts belong to this tag but 2 of these also belong to another tag. So enabling tagging in both trees enables the user to work and name things the way they want to work.
Hope this helps.
If other users don't want this feature, just add a disable/enable option in the user settings.
Here's a quick copy paste version of the tree with icons and a colored part list. I didn't even have to move around anything. However: I tend to rename only sketches and planes. The list gets a bit cluttered this way.
Also, because operation names are so long ("extrude", "thicken", "chamfer"), I've taken to using a text character as an icon. Extrude is =, sketch is #, fillet is r (because it has a 90° curve), chamfers and drafts are /, etc, etc. Just more evidence IMO that the feature list really needs more UI features to keep it manageable.
Or are you thinking just manual grouping like choose lines, click group, input name, have possibility to collapse/expand to show just name/all contents somehow tagged to certain group?
- Planes and sketches
- Main Body
- Attachments
- Finish
- Manufacturing
I guess you'll need a robust naming convention in your organization. Naming features is a hell. I only always name the planes and sketches. Everything else can be quickly selected in the 3D model – if it doesn't hide behind booleans…Mostly I will just rename parts and few features/sketches that are most likely accessed often.
But I'm big fan of multi-part sketches and features so that I can modify multiple things with single edit.
To be honest I don't know what I should request for making feature list better, my best quick fix is to be able to quickly mark/unmark 'favorites' with star or so and be able to one-click filter only favorites in list.
I suppose tagging would be the most universal and flexible choice in long haul.
i doubt it takes more than one day to implement.. XD
- Feature tree => As it is now
- Dependency tree => The actual "Tree" of parents and childs
- Tag "Tree" => Features sorted by tags, foldable
But the most important feature that should be awesome at first: Make all features selectable from the 3D view. It should go further back in time than one boolean. I want to be able to have a list of all features in the past that were necessary to create that fillet, face, edge… Who needs the tree if we get to everything in 3D view?@kevin_quigley @emerson_bottero
I agree that feature tree isn't the best as it is, but if you put same sketch into each feature it's used you end up with even longer list to scroll if you have 'em all expanded.
I would still prefer tagging, automatic combined with manual. Manual tags user can write what ever keywords, automatic tags would connect part names, feature names, sketch names, used parameters etc.
To begin with: Add similar filter as we have in recently added tab column, no 'magic' words to memorize just type to filter.
@mark_biasotti: I'm a huge fan of yours! In this particular case, however, I have to disagree: absorbed sketches are Satan. It confuses ordered lists in a way that makes things extremely difficult to manage in my workflow, and in teaching SolidWorks courses it was always confusing to students. I was thrilled when SolidWorks finally added the flat-tree, but sad to see that this excluded folders. So if I want to see an actual ordered list of sketches, I must forego the use of folders. To me this was always a huge down-side of SolidWorks, and made me miss CATIA and NX desperately.
I'd much prefer sketches to be shown inline as they currently are, but to have more smart highlighting to call out parent/child relationships, and better tagging/grouping/folders/nesting to consolidate the list manually. NX has some fantastic nested part functionality that allows complex parts to be comprised multiple nested sub-features. It's very powerful, and badly needed in other systems.
Adam