Community Tip - Want the oppurtunity to discuss enhancements to PTC products? Join a working group! X
Following another thread about real-world use versus PTC trainers' knowledge, how about we start a list of small things, which ought to be relatively easy for PTC to change, that nonetheless annoy you on a day-to-day basis (and always seem to be passed over in favour of introducing dashboards and ribbons)?
Since various PTC people contribute here, if we keep it tidy and concise perhaps some of our issues could be considered for addressing in imminent versions of Pro/E / Creo (/wishful thinking...)
So, here are some starters:
I've only been using it for a couple days, I'll be back with more.
- Another nice feature would be to choose to keep the original sketch when deleting features. Currently, when deleting the feature, the sketch gets deleted as well. If you want to re-use, you must re-create from scratch.
I agree that would be better, it would prevent headaches, but I just want to point out for those that may not know that the sketch could be created as it own entity so that it would not be lost when deleting a feature that references it.
Good point Kevin!
I mentioned it as a timesaver, for when I create or work with large models I prefer not to do separate sketches for it increases the length of the tree and harder to work on the part model.
Thanks for the reminder.
If you could drag your sketch out of the feature like you can with a datum plane created on-the-fly, that would solve that problem.
Consistency is what I want in a computer program. If I do "x" over here, I want to be able to do "x" over there.
Agree 100%.
I'm sure I'll think of more.
Here HERE!
Dump the ribbon in drawing mode in it's entirety, dump the stupid "lead vs. follow" workflow garbage, and bring back the pre WF interface with intelligent updates. Get rid of the "click anywhere in the field of the drawing to exit a command" and use the escape key. Having to zoom out far enough to clear views, snap lines, etc. totally sux.
Please can we leave major interface changes for another discussion? I'm sure there are already several out there...
I was hoping to direct some attention to small, detail-level changes that otherwise get overlooked in the drive to change things completely - but that would actually help users day-to-day, for relatively little programming effort, and that the development team probably haven't even considered because they're not using the software the way we do.
Thanks!
Make a mapkey that goes Edit>Select>Deselect all. You'll no longer have to zoom out to find empty space to click in.
Why not PTC just abandons the "click" thing and go to the "Esc" key? The mapkey's will be useless next version anyways, like most of mine are now.....
Since text editing and layout is difficult to manage in a multi-line note, be able to remove external lines of a table. Then item number and text can be easily tabulated and modified. Also, be able to attach an arrow to that multi-line note.
Off the top of my head:
That's all I can think of right now.
This has to be the most annoying (and plain stupid) thing in Pro/E. It makes you wonder if any of the developers have ever tried to model anything... ever. Does anyone have a solution for this? It seems like something that should at least be in config.pro already.
I also agree with the comment about what order we can do things in (select then function vs function then select). This was a bad move on PTC's part. There's no reason why you shouldn't be able to do either; especially since once you're in a function you can start over with a fresh selection.
And "refit" should work properly, even if I have to define my model size manually.
And there should be a quick way to add a datum plane mid-way between two parallel planes.
And they should stop limiting draft angles to 30 degrees.
I was going to add this to my above list (model zooming off screen). It's so frustrating when that happens. It also sometimes happens when I resume a feature. This is especially annoying because sometimes I want to look closely at a part of my model to see how it's affected by a feature. I can't easily do that if I have to zoom back in to the same spot afterwards.
When editing a model, It would be nice to add a feature when in the Info > Feature mode, to add a "Highlight in Model Tree" action (in addition to the "Highlight Object in Graphic Window").
When I am concerned about editing impact(s) on children features, it is hard to quickly identify and edit them without going back and forth between the information and graphic windows while highlighting, clicking and Locate in Model Tree action(s).
When "replacing" sketcher entities, you should not have to keep answering "yes". In fact, you should be able to replace a chain or loop with another chain or loop.
... and when you replace them, they should actually be replaced! The child features should use the replaced reference, otherwise what am I actually doing? I don't know how many times I've gone through that whole rigmarole and then the next feature fails exactly the same way that it would fail if I had just hit deletedeletedeletedelete.
I've seen that on occasion too, although, for the most part, it actually works. I like that in WF4 in sketcher mode you can actually replace the refs, as well.
When loading an assembly that has a failed component, there should be a way to cancel out of it without having to freeze or suppress every goddam child item in the rest of the assembly.
Provide the ability to remove multiple holes from an imported model fast. Very time consuming to do with remove feature.
When you select multiple holes by geometry rules inside of flexible modeling extension and then click remove Creo tries to find all possible stupid solutions and crashes instead of starting to remove holes one by one to finish it.
So you have to manually decide which holes to remove and in what order. And I am talking about solid model.
When loading an assembly that has a failed component, there should be a way to cancel out of it without having to freeze or suppress every single child item in the rest of the assembly
Robert McKibben wrote:
When loading an assembly that has a failed component, there should be a way to cancel out of it without having to freeze or suppress every single child item in the rest of the assembly
Quit retrieve?