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.
(un)suppress a folder from a configuration
jeff_mcaffer
Member Posts: 66 ✭✭
The new ability to (un)suppress a folder of features in the UI is awesome. Thanks. I don't however see a way to do this from a configuration. I do see that you can add all of the features in a folder using configure suppression but that adds a column for each of the 17 features in the folder rather than one column for the folder. This leads to issues like:
- folders of any size result in too many columns in the list
- all features are exposed making users think they can control them independently when really some inputs depend on others and should not be changed directly
- new features added to the folder are not included in the list and features removed from the folder remain in the list with no easy way to update other than managing them individually.
- in the configuration pane is it not obvious which columns are part of a folder (or which folder) so they're out of context
I do see the value in the current behavior — basically a shorthand for "add/remove all the features in this folder to the list" — but it is just that, shorthand. more generally you could have added "select all" (features in this folder) then the user could "select all, suppress" or any other multi-feature operation.
The use case for this is having a user-facing list of inputs to control the model between different discrete states (e.g., large/medium/small, with(out) holes, …) where each state might differ in many ways (lots of different, implementation-specific inputs) but where the user of the model manipulates a small number of the inputs (e.g., size, hole count and color).
Alternatives to folders directly in input lists might be
- conditional suppression: If one could "code" the suppression of features based on the suppression a feature or value of input/parameter values then you could add the top level inputs to the list and hide the suppression logic under the covers of the model.
- grouping of inputs: As a fallback, being able to indicate to model users which inputs are "for them" and which they should not change would get part way there. Then it doesn't matter (within reason) how big the list is, do long as the "user inputs" are first and clearly indicated.
Answers
Vote here: