"graminator" <grahamew@[EMAIL PROTECTED]
> wrote in message
news:01ef9b9d-cc3b-4de4-ae3c-688ad72c7e45@[EMAIL PROTECTED]
Mar 5, 7:56 pm, "Janes" <dja...@[EMAIL PROTECTED]
> wrote:
> "graminator" <graha...@[EMAIL PROTECTED]
> wrote in message
>
>
news:e714ced5-79e9-43db-9905-1eaeec3e2bc3@[EMAIL PROTECTED]
>
>
>
>
>
> > You're in part mode and you've modified your model somehow, which has
> > caused a feature to fail, so you use clip/suppress. Then when you look
> > at your tree, the arrow indicating where you are in the model has gone
> > to the bottom, after all the features you've just suppressed. If you
> > need to create a feature in order to get the rest of the suppressed
> > features to regen, it will of course be after all the suppressed ones.
>
> > I do this several times a day and after using ProE for 12 years. I
> > create a new feature and - woops - it's at the bottom of the tree
> > after all those suppressed ones. "Damn I did it again!" Buts what's
> > even more annoying is I can't just drag the new feature up the tree
> > and place it after the last regenerated one, because ProE won't place
> > the new feature *before* a suppressed feature. Why?
>
> > Also I can't just drag the arrow up the tree to after the last
> > regenerated feature for the same reason - ProE won't put you *before*
> > a suppressed feature. WHY? This seems like such a simple thing so I
> > don't understand why it doesn't work this way.
>
> No, I've never done that, don't think I even knew clip/suppress does as
> you
> say. I just go into the Dreaded Resolve Mode and fix the feature
failure,
> including, as Geesaman suggested, using Fix Model (for features that
need
> fixing before the failed one because they caused the current feature to
> fail). I guess I'm also left with questions, such as why you'd ignore
the
> built in "insert" (Resolve Mode) and try to do that by the back door
> (suppressing a bunch of features, then trying to ignore and make a big
end
> run around them). All I can think is that this is something you learned
a
> long time ago and have been beating your head against the wall ever
since.
> You might reconsider doing it this way, bite the bullet and learn to use
> Resolve Mode (other than clip/suppress).
>
> The only reason I can think of for using clip/suppress is to quickly get
> out
> of the DRM so you can reload the part and start to figure out what went
> wrong. If you're using Intralink, you can reload the part easily by
doing
> 'File>Update>Current' and it restores the file to the last saved
version.
> If
> you wanted to learn resolve feature failures, I'm sure I saw webcast
> specifically on that topic at PTC.com
>
> David Janes- Hide quoted text -
>
> - Show quoted text -
You're right Dave, I could do this, and it's habit that makes me do it
the way I do. When the feature fails, if I:
#Fix Model
#Feature
#Confirm
#Insert Mode
#Activate then pick the last feature before the failed one I am
then where I want to be and I can save it at that point if I want.
Of course it's a lot more menu picks this way. If I could just drag
that arrow up the tree....
I think I will make this one of those enhancement requests.
__________________________________________
Would "Roll Model" (before failed feature) do what you want? However, the
most frequent repair scenario I've come across involves simpler stuff than
Fix Model, for example, Quick Fix>Redefine or Replace references
(investigating with a backup model usually helps with figuring out what
references need to be replaced). If that worked then no need for
clip/suppress and no need to slide the Insert bar up through dozens or
hundreds of suppressed features. Talk about tedious and time consuming!
just
try to get that bar to slide when your destination requires the bar to
scroll above the last visible feature, hopping up one feature at a time.
Or
you do the scroll bar and drag some more, scroll bar, drag some more, etc.
Think I'll pass on this "easy" way.
David Janes
|
