"graminator" <grahamew@[EMAIL PROTECTED]
> wrote in message
news:a72dfd27-f27a-452f-84f1-cb4922bc15ee@[EMAIL PROTECTED]
Mar 7, 6:59 am, "gluteous maximus equus" <n...@[EMAIL PROTECTED]
> wrote:
> > 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.
>
> Model Tree Items Display; clear the Suppressed Objects tick box.
>
> A person such as myself reading this discussion might get the impression
> that there's something inherently 'bad' about Clip Suppress or slovenly
> about anyone that would us it. If that is so would someone please
> make that case.
>
> On a parallel, re: "slide the Insert bar up through dozens or hundreds
of
> suppressed features"; I don't often work with a Model Tree longer than a
> page or two in length having Grouped features solely for the purpose of
> keeping it short, use them as 'volatile' structures, Grouping and
> Ungrouping to ****ft relevant and irrelevant to task at hand features
into
> view. Doesn't everyone?
I group things too, but sometimes it's a pain because if one of the
features in the group fails, then the whole group fails.
__________________
This might be a different subject in assemblies where I also use groups a
lot. The behavior is certainly different. There you can have the group
regenerate, but have all the components in the group frozen, no indication
unless you run Model Check. However, using the Search tool, search on
Component and select Frozen on the Status page will find all those
components for you.
David Janes
|
