default_layer_model configuration

[cadmunky69]

howdy folks. has anybody toyed around with this option? i'm setting up layer rules in start models, but came across this option looking for alternatives. at first it looks like a layer "template" object.

can more than one object type be listed? seems silly to point to a part model for drawing layers.

Ed Lee
Sr. Designer
H2Gen
Alexandria, VA

 

[cadmunky69]

ah, yes:

Description
It is possible to have "default_layer_model" for "part.prt" or for "assembly.asm" or "drawing.drw", but not for all types at the same time. How to set all types at same time ?

Resolution
Yes, it is possible to have "default_layer_model" defined for part, assembly and drawing at the same time.
All three file types must have the same name and Pro/ENGINEER will select the correct one by the file type.
Example:
Set the config option "default_layer_model" to "layer_setup_file". Note: No file type extention .prt or .asm or .drw is entered here !
Then create the files with the layer rules named 'layer_setup_file' and with the extentions .prt , .asm and .drw.
So the files in the directory are:
layer_setup_file.prt
layer_setup_file.asm
layer_setup_file.drw
Pro/ENGINEER will select the correct file by its file type.


Ed Lee
Sr. Designer
H2Gen
Alexandria, VA

 

[jeff4136]

Thanks for coming back with the explanation, Ed. I've never used layer template files and was curious.

You are aware of def_layer config options, as well?

 

[cadmunky69]

i'm trying to determine a suitable scheme for controlling layers with a combination of configurations. still fairly new to WF3, so i wanted to explore the different functionalities. just not sure if the layer templates give any more advantage over setting up rules in the start parts.

i'm thinking of using the templates or start parts to control default layers and def_layer options to control newly created features. for now i'm using ptc's numbered heirarchy (01_ALL_DT, 01__ASM_ALL_DT, etc) to observe the interactions.

from the description of default_layer_model, it sounds like every time a new feature is created, the template is read to create the proper layer and place the item on it, just like a rule. if there's an advantage to this, i'm not seeing it.

Ed Lee
Sr. Designer
H2Gen
Alexandria, VA

 

[jeff4136]

> ... template is read to create the proper layer ...
> if there's an advantage to this, i'm not seeing it.

It sounds like it would be useful if start parts are not (create, new, empty) used.

Another advantage ~might~ be where a number of different start models are used if it means you don't have to set up and maintain rules in each template file.

Not sure, but I think your's is the first question or mention I've seen regarding the use of layer templates. Wonder if it's sort of a relic function that's been succeeded by newer functions and methods?

Sorry, just yammerin'. `;^)

 

[cadmunky69]

by all means, yammer away. from your assessment, i see a glimmer of use to be had from this. i just didn't see the need to "ping" an external object for info.

while improving (i hope!) the way we create and control models, i'm trying to severely limit the creator's ability to veer from the standards i'm imposing. but i know there's always gonna be some joker (sometimes me =P) who will bypass my carefully laid out object creation routines, and instead of picking on the pretty new icons i made for just such a purpose, will click create, new, empty. i can at least protect the layer structure somewhat with this method. maybe keep the options in the config.sup. >

still picking at it....

Ed Lee
Sr. Designer
H2Gen
Alexandria, VA

 

[cadmunky69]

more from the help files:

To use predefined ruled layers, you must define a template model with the required ruled layers specified. This model is designated as the template layer model. To access the template layer model set the default_layer_model config option to <layer_model_name>. Where <layer_model_name> specifies the model name that would be used to define predefined ruled layers for all models (*.prt, *.asm, and *.drw) in session. You must specify the name of the default layer models without an extension. You can create template layer models for a part (*.prt), assembly (*.asm), and drawing (*.drw). For example, if the default_layer_model config option is set to DEF_LAYER_MODEL_NAME, then for a part, Pro/ENGINEER will search for def_layer_model_name.prt, and for an assembly, Pro/ENGINEER will search for def_layer_model_name.asm in the working directory, workspace, and template directory.

If you create a new entity in a part, assembly, or drawing that matches the criteria of any of the predefined rules in a template layer model, a new layer is added to the current model automatically, and the new entity is added to that layer. However, if the template model is not available in the current session and if it is undesignated, then the ruled layers are no longer driven by the template layer model.

When the template layer model is not available, then the existing ruled layers become non-ruled layers and do not collect any items or objects. Additionally, a layer driven from the template layer model (or default layer config) will have the option of making the layer independent of the default layer model. Models that already have layers before a default layer model is used will always have layers that are independent of the default layer model if rules are already defined for the previous layers.

looks like def_layer can go away completely, right?

our start parts contain the 3 default datums and csys, so there's 4 layers: DT_ALL, DT_DEF, CS_ALL, and CS_DEF, with rules DT_ALL contains DT_DEF and all subsequently created datums, DT_DEF contains only DT_RT, DT_TP, and DT_FT. etc.

if i create all other layers and rules in the default layer model, then i guess there's no need for any other layers in the start parts, correct? or is there some combination of the options that make more sense? oh! and don't forget layersetup.pro files!

i know, it may be too soon after new year's. may be exactly why i'm not grasping this right away.

WF3 m030


Ed Lee
Sr. Designer
H2Gen
Alexandria, VA