cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - Did you get an answer that solved your problem? Please mark it as an Accepted Solution so others with the same problem can find the answer easily. X

Config.Pro - am I missing a setting?

JWayman
1-Newbie

Config.Pro - am I missing a setting?

Of course I am not, but I need to ask...

I have, on a couple of occasions recently, got myself into a situation where
I wanted to stop my assembly being retrieved. I remember, in earlier
versions of Pro/E, the option 'Quit Retrieve' being available in the
suppress, suspend, delete, etc. box. In WF2, it no longer seems to be
available.
More in hope than expectation, I wondered whether there was a way to get my
'Quit Retrieve' button back. Any ideas?

I expect it's a feature/enhancement/intended functionality and the fix is to
always remember to unsuppress all the suppressed features in the skeleton
before retrieving the top-level model, but at my age...    🙂

WF2, M220

Thanks,





This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.
4 REPLIES 4
StephenW
23-Emerald II
(To:JWayman)

WF2 quit retrieve is still available, but only for when components are missing, not when features fail or when component placement fails.

Usually, if it is a big assy and I stand to lose nothing, I just use task manager and kill the xtop process. It's the fastest quit retrieve available.

I'm on WF2 M210. Soon to be moving to WF3...no wait...WF4...no maybe not...WF5...no, not compatible with other programs...no wait maybe in another year...

The biggest problem I have is that I will hit the stop button - and it
continues to regenerate, so I hit it again and it continues to
regenerate. Usually a kill is the only way to get the darn thing to
stop.

Richard A. Black
Lead Engineer
Eaton Corporation
440 Murray Hill Road
Southern Pines
NC 28387 USA
CBenner
5-Regular Member
(To:JWayman)


One of the nicer features of WF5 (and this is saying something), is that when a feature fails or a part fails or is missing, the assembly or model continues to load, and then tells you you have errors. Searching your model tree, they will be highlights red with a boxed X next to them... so you can click on them and figure out the problem. no more of the "suppress, freeze, clip-suppress" etc... that took forever to go through in loading an assembly with errors.
<u>

</u>
Chris Benner
Autodesk ® Expert Elite
dgschaefer
21-Topaz II
(To:JWayman)

Sounds just like Saladworks - the failed feature, and all it's children
are automatically suppressed. Well, SW does stop and ask if you want to
fix it now or continue with the rebuild, does WF5 ask first?

Come to think of it, that's exactly what WF4 and earlier did. They just
didn't ask so politely, I guess.

Doug Schaefer
--
Doug Schaefer | Experienced Mechanical Design Engineer
LinkedIn
Top Tags