WF2 lost some functionallity (or it is difficult to find), regarding to
ProE2001 (although, most of our users didn't fully understand and didn't use
it). In 2001, it was easy to add geometry entities to layers, in addition
to features. So far, I haven't found an easy way to add geometry to layers.
An example : you have two ruled or default layers, (1) for datum axis, and
(2) for thread surfaces. Now, you construct a threaded hole as standard
hole. In 2001, the layer for datum axis contained only the axis entity, not
the hole feature. And the thread layer contained only the thread entity,
not the hole feature. In WF2, both layers contain the hole feature !
Consequently, if you hide the axis layer in WF2, also the threads are hidden
Another function not fully understood was 'isolation of a layer'. This
helps when features/geometry is on multiple layers. But very few of my
users understand it, and non of them used it. In WF2, this option moved a
level deeper in the menu structure.
<-> wrote in message news:155416@model...
> I created a standard for our company's layering techniques in Pro/E for
> 2001 some years ago. Now our switch to Wildfire 2.0 has got me looking
> pretty heavily at layering rules, as I feel the automation of placing
> entities on layers would benefit our users a great deal. My problem is
> that in my testing, in certain situations I am getting a few entities that
> end up on multiple layers because of the geometry in that entity.
> In my current standard, I discourage entities on multiple layers, because
> they are both layers need to be on to show the entity. My question is
> this...is it such a bad thing that entities can reside on multiple layers?
> What is everyone's thoughts and experience on this topic, and what do your
> standard's say?
> Any and all help would be appreciated.
> Britt D. Mott
> Design Engineer
> EATON Automotive
> 19218 B Drive South
> Marshall, MI 49068