Stop the regeneration of an assembly?

[fiebigc]

How can I stop or freeze the regeneration of an assembly when an error occurs?

Example:
I forget to resume all of the features in a skeleton model after editing a feature. I click regenerate on the assembly and now every part is broken.

The simple thing to do would be to stop the regeneration go back and resume the skeleton model and then re-regenerate. I feel like something like this should be possible but I haven't figured out how to do it. Any suggestions? Thanks.

 

[rudresh.hm]

when the assembly component placement fails select clip suppress. this is what I do. I am also interested to know if there is something better than this, even to stop regenerating the firstcomponent.

 

[mcgowanp]

Charles, I know your pain, pretty much all you can do is clip surpress every part till all are done. You can try clicking the stop button on the regen dialogue box but this doesn't seem to do much.


I removed the regen button from my display and just left on the custom regen button, saves me a bit of heart ache!

 

[jason_]

You can always hit the stop sign in the lower right hand corner during regen, that will abort the regen but this doesn't really "freeze" it.


You may as well just blast through the regen, clip suppressing and freezing components and then once it's done go back and fix the ones you forgot about.


There is a config setting that automatically freezes failed components. Then, in your model tree you candisplay a column'Status' and this will show you any components that are frozen(among other status'). Use it knowing that there is a riskthat you may have failed components in your assembly that need addressing. You can also check your regen log to see what has failed.


freeze_failed_assy_comp yes
Edited by: jason_

 

[fiebigc]

Yeah but what if you have an assembly with a couple of hundred components? You would have to clip suppress everyone of these. Right now I've gotten in the habit of saving everything before I do a major regeneration. If something really goes wrong then I pull the plug on ProE and start over.

There has to be a better way.