Skip to main content

Filter by idea status

Filter by product

6851 Ideas

Modeltree filters/queries - create and save advanced, user defined modeltree filters/queriesArchived

Current situation: The modeltree can be filtered by using the Tree Filters functionality and it can be modified by displaying different columns by using the Tree Columns functionality. Additionally the user is able to filter or query by a certain item using the quick search field. This will reduce the model tree and show only objects that has the certain item.   What is missing: What is currently missing is a way to filter the modeltree in a way that shows objects without a certain information - the other way around. Next to the quick search field I found some predefined queries and I was hoping to create my own but it is only possible to use the existing ones. I wanted to filter the modeltree to identify objects that do not have a certain parameter value and therefore need to be treated. As the quick filter only filtering for a certain item it can't be used for that kind of "negative" search.   What can be improved: To be able to filter the modeltree for missing values it would be necessary to create user defined queries that enable the user to create "negative" searches/filters in modeltree. The idea is to make it accessible next to the already predefined queries as shown in the picture.     can With the new functionality of quick search/filter it is possible to reduce the modeltree or highlight objects inside the modeltree with a matching item from the quick search field. 

Improve user speed using Sketch filletsArchived

Issue: I suggest that there is a need to improve user productivity using sketch fillets.   Problem: When needed to make tangent arcs to lines, the user normally draws the lines first, and then applies fillets between the line pairs to obtain the tangent arcs. When the user only needs 1 or 2 fillets, this workflow does not need too much time. But when the user needs to draw several fillets, and specially when the fillets have all the same radius, this workflow is not the best one, from the user productivity point of view, since after selecting all the line pairs, and the fillet is constructed, the user will have to re-specify constraitns, to guarantee that those fillets have all the same radius.   Solution: To improve sketched fillets drawing workflow, I suggest that should be introduced a new fillet command, where the user pre-specifiies the radius value, and after only is asked to select vertices between connected lines, instead of selecting two line pairs. This improves speed, by selecting falf the inputs, and by do not needing to re-constraint the fillet arcs to have all the same radius as needed. I guess this is the Solidworkds workflow, and it is indeed a time saver for the user, since this is such a common sketch drawing task.   Curiosity: Creo constraitns vertices for sketch mirror operations (instead of constraining the line entities instead of their vertices), contrary to Solidworks, but uses line entities for the fillet operation, when the vertices approach is the faster alternative for the user, when Solidworks uses vertices, as the better approach. Creo's approach for the fillet operation is only better when the lines to be filleted are not already connected by a vertex, so, it could keep both methods as different commands, or modify the existing command to allow both aproaches, filletingbetween non parallel lines, or filleting the line connected vertices.   Thank you.

Make the Solidfy Feature option Replace Surface auto-hide the used quiltArchived

Problem: We use a lot the solidify feature in regular modeling practices, specially the third option of the solidfy feature, which is the "Replace surface" (ancient Tweak Replace with quilt). Every time we used the feature, we had to imediatly create an extra-layer, if it wasn't already present, to hide what should have been a consumed quilt. The first two options of the "Solidfy" feature, "Fill with solid" and "Remove material" always consume the quilt, so we don't need to create a layer to hide the quilt. Why didn't the third option, "Replace surface" didn't follow the same behaviour, and kept the quilt? It's even more anyoing, since in 95% of the time we will not use the quilt for anything else, so we have to create a layer to hide it, slowing us down, or create an extra feature, the "Remove surface" feature, not forgetting to imediatly selecting an extra option, "Leave Open", just to remove which in 95% of the time should have been a consumed quilt of the solidfy feature. This inconsistent behaviour is annoying, slows experienced users in the modeling process, and baffles novice users with inconsistent behaviour of the same feature (Consuming or not a referenced quilt).   Proposal: Keep existing behaviour as an option, but also add a config.pro option to make the solidfy feature have an extra option to allow the user consume or keep the referenced quilt when using any of the three sub-options of the Solidf feature, making all three options consistent, and allow the user to speed up common modeling practices. See the last image.   Please see the attached images to better illustrate the idea. Thank you.