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

Community Tip - Learn all about the Community Ranking System, a fun gamification element of the PTC Community. X

Layers. Was Missing cosmetic threads in model and drawing - SUMMARY

kimndave9
1-Newbie

Layers. Was Missing cosmetic threads in model and drawing - SUMMARY

It is a puzzle about putting threads on an axis layer - I'd think a
thread layer for the cosmetic thread and put the feature axis on the
axis layer.
I've trimmed layers considerably by using function rather than simply
type as the key.

Datums that are set go on the set_datums layer. Axes (but not the
features that have axes) go on the axis layer.

Geometry that is used to construct things goes on the construction layer.

Anything else can be found by type anyway, but the usage is what's
important.

Besides, though PTC can call them layers, they are actually lists. In
the normal sense an item can only occupy a single layer at a time. An
item can appear on many lists or no list at all - which is how the PTC
'layers' works. The nice thing about viewing them as lists is that
understanding the behavior is easier, Like Exclusive** layers - it's not
to show items that are on a list, it is to not show items that are not
on the list. Items -not- on the exclusive 'layer(s)' show up even though
it is not expected to happen that way.

The mental model of 'list' has been much clearer to me than that of 'layer'


Dave S.

** Now called Isolate. Unless Isolate does the opposite and only shows
those items on the list. I use simplified reps, which are also lists,
rather than layers, to control visibilities of components.


chwerdlin, Bob wrote:
>
> Several people responded that the problem may be with layers and they
> were correct to a certain degree.
>
>
>
> The problem reared its ugly head because he had Fast-HLR turned ON.
> Once turned off, everything was fine. This is just another case where
> NOT using Fast-HLR is the way to go. Regarding the drawing...
> cosmetic threads default to the FEATURE and AXIS layers in the drawing
> and that's where the problem was.
>
>
>
> Problem solved.
>
>
>
> Thanks everyone.
>
>
>
> Bob
>
>
>


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

An isolated layer will show only the items on that layer, and hide all
items that are on other layers. Items not on any layer will not be
effected. If an item is on two layers, the isolate status if one layer
trumps both a 'hidden' or 'unhidden' status on any other layers. Also,
FWIW, the 'hidden' status of one layer will trump the 'unhidden' status
of another. That's an overly simple explanation because there are other
things that can affect an item's display. A great (if long) read on
this is at the MCAD central forums, including Glenn Beer's excellent
layers presentation from PTC|User 2007:


www.design-central.com
--
Doug Schaefer | Experienced Mechanical Design Engineer
LinkedIn

Perhaps that's why PTC offers training classes just for LAYERS. It's complicated enough that it needs its own classes. Hmmm ?

Bob

The important part Doug didn't mention has to do with basic visibility of
items.

As an example: Take the lowly point feature. One point feature can contain
one, or many, geometric point entities. You can put the feature itself, onto
a layer, or one, or many of the geometric point entities. The difference can
make or break a layer implementation.

if the point FEATURE is put on one layer (blanked), and the point geometric
entity is put on a second layer(isolated), the point will not be visible.

3pointFeature on layer1
point1 on layer1
point2 on layer2
point3 on layer3

isolate only layer 1 and point1 will be visible.
isolate only layer 2 and nothing will be visible.

Why: Point2 will not be visible because, the basic visibility rule kicks
in, "the feature is invisible, all of its geometry is invisible." This
includes feature geometry that might be on isolated layers.
--
The comment that layers in proe are nothing more than lists, is exactly
right, but the Cad community is stuck with the word layer.
--
On layers, holes and axis...
Engineered holes in proe consist of a number of geometric elements, the hole
surface and edges, the axis, and maybe a cosmetic thread. PTC for some
reason chooses to associate the axis of a hole with the thread geometery if
it exists. So you can't choose to show the thread or axis independent of
each other.
I did see one release of proe once where the axis could be layered
independently of the thread. When I asked why it didn't stay that way. I was
told that the change had been deemed too disruptive to the legacy of models
currently in existance
--

Glenn Beer

On Mon, Jun 22, 2009 at 5:58 AM, Doug Schaefer <
> wrote:

> An isolated layer will show only the items on that layer, and hide all
> items that are on other layers. Items not on any layer will not be
> effected. If an item is on two layers, the isolate status if one layer
> trumps both a 'hidden' or 'unhidden' status on any other layers. Also,
> FWIW, the 'hidden' status of one layer will trump the 'unhidden' status of
> another. That's an overly simple explanation because there are other things
> that can affect an item's display. A great (if long) read on this is at the
> MCAD central forums, including Glenn Beer's excellent layers presentation
> from PTC|User 2007:
>
> http://www.mcadcentral.com/proe/forum/forum_posts.asp?TID=34733

Hi Glenn,

Is there a best practice you can share? Especially on threads and axes?

When I arrived here, layer definitions in our templates were a mix of
feature driven layers and entity driven layers. I moved away from the
entity driven layers, but as you indicate, for threaded holes, there
isn't much alternative then implementing entity driven layers. It's
even worse with inheritance features, in which case you have to have
entity driven layers for axes and threads.

Tia, Hugo.
Top Tags