Skip to main content

Filter by idea status

Filter by product

6851 Ideas

More intellegent SUPPRESS pop-up windowArchived

I often work on very large models with many features.  They are often created by other team members and can have questionable modeling techniques. So when I select a feature from the model tree for suppression and the message window pops-up informing me that the "Highlighted features will be SUPPRESSED. Please confirm." I always have to worry what dependent children were automatically selected for me.  This means searching the model tree for the other features that were "software" selected or visually scanning the graphic window for unintended feature highlights.  Both can be prone to error.  The worst part is you could be looking for nothing if the original selection has no dependent children.  Even when there is a single item in the collector, the message is still plural, as in "features".  I'm never really confident that the software isn't doing something I don't intend.So I'd like to make this an improvement request:Please make the pop-up msg box have more intelligence.  Provide feedback to the user the quantity of "user selected" features and the number of additionally selected dependent features.For example: "29 Total Highlighted Features will be SUPPRESSED; 3 SELECTED and 26 Additional Dependents"I'd settle for just the total number, I generally know how many I've selected and can do the math in my head. Or maybe just the number of unselected dependents that were added.Maybe I'm missing the config.pro option that disables the dependent child addition to the suppression collector with the result being a bunch of failed dependent features.I also hate the fact that when a failed feature is in a pattern, the failure isn't visible in the model tree until you expand the pattern feature to reveal the fails inside it.  But that's for another discussion.Are there workarounds for this behavior?

Explode View offset line - redefine function needed.Archived

Creo 2.0 - Offset Lines in exploded viewI've been doing explodes for many years and I have always wondered why?Why isn't there a "Redefine" option for an offset line that was working fine but is now broken because of a replaced component? I find the only choice here is to delete the old broken offset line and recreate it even if only one of the end attachment definitions is invalid.Why isn't there a "Pattern" option when creating offset lines - even if the only pattern type available is "Reference"? I often have a reference pattern of fasteners assembled to a pattern of holes all exploded off together. The only choice is to create each offset line individually when what I really want to do is to create the first one and pattern the rest following the reference.Why is it that the only place anywhere in the software that requires you to explicitly "save" after completing a redefine (soft) is at the end of an exploded view edit? Everywhere else when you complete a definition with an OK or and APPLY you are DONE. The constraints are complete and saved when the file is saved. Not so in the world of exploded views. Here, when you end an "edit" your changes only stick while the model is in session even if you file/save. You have to deliberatly use the save option burried inside View Manager's Explode Edit tab. It (the "save" option) never shows on the way out of the explode state define/redefine. You have to go to a different/unscene menu pick to find it.  It just seems so inconsistant with the rest of the define/redefine paradigm used in Creo.I think the main reason is that this functionality is "intended" and PTC believes it works and doesn't need to be continually developed and improved. I see this in many areas of the software, they get it most of the way and there it sits - unfinished. I still get occurance when Menu Manager (of all things) pops up and were back to the old days before the ribbon. Pro/Process is the other best example (though there are other). It hasn't been enhanced or even fix for many years. It still can't deal with a component replacement in the source assembly even if all the models affected are in session.

Allow Visual Basic API COM to Register Multiple Releases On Same MachineArchived

We have written custom applications at our company using VB API.  We'd like to run multiple releases of Pro/Engineer and Creo on the same machine with each of them using our custom applications.  This can be done, but is a bit of a hassle.Here's the process.  Pro/E WF4 needs registration of Visual Basic API COM server (pfclscom.exe) through vb_api_register.bat (<proe_loadpoint>\<datecode>\bin).  When switching to run Creo 3.0 we need to first unregister Pro/E WF4 and then register Creo 3.0 using its own version of vb_api_register.bat (<creo_loadpoint>\<datecode>\Parametric\bin).  Also, when going back into Pro/E, Creo gets un-registered and WF4 needs to be re-registered again.  They cannot both be registered at the same time.  One must first be unregistered for the other to work.I opened a call with PTC tech support asking if there is a way to have both CP3 and WF4 registered at the same time on the same machine?  Here is the response."it's impossible to have Registry based registered both versions.  This can be done with manifest based registration, but it requires a new project and approvals for enhancement."It was recommended by PTC tech support that I submit this new product idea in the hopes of gaining some traction.  It would be nice to be able to register each version one time and be done with it!