CONFIG SETTING FOR DATUM FILTERS?

[timhelgren]

Hey all,

I am trying to see if there is a config setting that will leave the Datum Display Filters off on startup.

Thanks for the help,

Tim

[StephenW]

display_axes no
display_coord_sys no
display_planes no
display_points no

[timhelgren]

Thanks guys, I appreciate the responses.

For those of you searching:

display_planes no

display_ponits no

display_annotations no

display_axes no

display_coord_sys no

[ptc-936529]

I'd like to add a comment, you should create two mapkeys. One to toggle default datum feature on and one to toggle off

[ptc-4958087]

you camn use one mapkey to toggle on/off datums, in my example using F2 key:

mapkey $F2 @MAPKEY_LABELDatum Plan on/off;~ Command `ProCmdEnvDtmDisp`  1;

[mlocascio]

Personally I like the idea of creating macros for this type of thing also.
There are things that don't need to be fooled around with. I like seeing
datum planes when I start a part or assembly file. It's like having a
program at a baseball game. REF "You can't tell the players without a
program."



On the other hand this is Pro/E and NOT AutoCad. We can change things to
suit our specific wants and needs. I would certainly want to make sure that
the users are on board with those types of changes.



Michael P. Locascio

[davehaigh]

Actually, you don't need two mapkeys to turn the datums on and off. It's just a toggle. I do it like this:

!=========================================================
!== DATUM VIEWING ==
!=========================================================
mapkey ax @MAPKEY_LABELAxes On/Off;\
~ Command `ProCmdEnvAxisDisp` 1;

mapkey cx @MAPKEY_LABELCoordinate Systems On/Off;\
~ Command `ProCmdEnvCsysDisp` 1;

mapkey dx @MAPKEY_LABELDatum Planes On/Off;\
~ Command `ProCmdEnvDtmDisp` 1;

mapkey px @MAPKEY_LABELPoints On/Off;\
~ Command `ProCmdEnvPntsDisp` 1;

mapkey af @MAPKEY_LABELAll Datums Off;\
~ Command `ProCmdRibbonOptionsDlg` ;\
~ Select `ribbon_options_dialog` `PageSwitcherPageList` 1 `ConfigLayout`;\
~ Activate `ribbon_options_dialog` `ConfigLayout.Open`;\
~ Update `file_open` `Inputname` `P:\\mapkey_configs\\datums_no.pro`;\
~ Command `ProFileSelPushOpen@context_dlg_open_cmd` ;\
~ Activate `ribbon_options_dialog` `OkPshBtn`;\
~ FocusIn `UITools Msg Dialog Future` `no`;\
~ Activate `UITools Msg Dialog Future` `no`;

mapkey ao @MAPKEY_LABELAll Datums On;\
~ Command `ProCmdRibbonOptionsDlg` ;\
~ Select `ribbon_options_dialog` `PageSwitcherPageList` 1 `ConfigLayout`;\
~ Activate `ribbon_options_dialog` `ConfigLayout.Open`;\
~ Update `file_open` `Inputname` `P:\\mapkey_configs\\datums_yes.pro`;\
~ Command `ProFileSelPushOpen@context_dlg_open_cmd` ;\
~ Activate `ribbon_options_dialog` `OkPshBtn`;\
~ FocusIn `UITools Msg Dialog Future` `no`;\
~ Activate `UITools Msg Dialog Future` `no`;

The two configs look like this:
Datums_yes.pro:
=============
display_axes yes
display_axis_tags yes
display_planes yes
display_plane_tags yes
display_points yes
display_point_tags yes
display_coord_sys yes
display_coord_sys_tags yes

Datums_no.pro:
=============
display_axes no
display_axis_tags no
display_planes no
display_plane_tags no
display_points no
display_point_tags no
display_coord_sys no
display_coord_sys_tags no

David Haigh

[RonGrabau]

OK, I don't do this often but I am going to poke the pig and see what happens.

I am always amazed when parametric users don't use layers to control the display of datums. As a standard rule we put all datums on layers and then save the status as hidden. This way you never have to worry about what the state of the datum display is. I am sure that everyone has turned on the datums to work on a part only to switch windows and get the assembly which can no longer be seen due to the datums. I have no idea how someone can work in this environment. I have to assume that users toggle the display off and then are forced to select from the model tree. I personally find that process unproductive. I don't mean to pick on anyone here and get all the hate mail back but I guess I have a narrow perspective on this subject.

In my personal world I just turn on the datums for the assembly and any current parts that I am working on. I can do this since all models are saved with the datums in a hidden layer status. I would never want to see all the datums of all the parts while I am working on a part.

Some of my users complain that if they try and assemble a part with the layers hidden you cannot select the layer. I find this not to be true. You can switch to the layer tree and pick on the select icon and pick the model being assembled, you can then unhide the desired datums and do your work. When you are finished and save the layer status is still hidden and the next time you retrieve the assembly all the datums are off. You could argue that that process slows down the assembly of the component but I also would think it is difficult to place a component when you cannot see the assembly.

Here is a fairly simple board assembly. Why would you ever want to see this... ever?

[cid:image001.png@01CEF7E5.A7EFDFD0]

I would rather work with a model that looks like this

[cid:image004.jpg@01CEF7F6.47AA9460]

Maybe I am old fashion and just have not learned new tricks. Eventually I will retire and not bother people with my old way of thinking. But until then...

What I do hate is getting models from vendors that have layer names that are different from our standard. I see datums on all sorts of layers and this makes it difficult to work with. This is particularly true with set datums. For this reason I have a toolkit application that deletes all layers, creates the company standard layers and assigns features to the correct layers. You can run in on an entire assembly and it is recommended prior to putting it into our PDMLink system.

If you create layers with rules you get an automatic assignment so you don't have to worry about getting things left off a layer. I use templates for our standard parts, assemblies and drawings just as many of you do. I also have the layer setup file set just in case someone decides to not use a template. My point is that once you set up a standard it makes dealing with all the datums pretty simple.

Yes, I still have mapkeys to toggle datums on and off but I don't use them because I have too many datums showing in my assembly. I just want a picture with no datums or just don't want to see them at that moment. (Yes I know I can shade the model...)

Anyway, just my 2 cents worth of Friday thoughts.

Have a good day and weekend!

Ronald B. Grabau
HP PDE-IT
Roseville, CA
916-785-3298
-<">mailto:->

[mdebower]

No hate mail from me, I agree with you.

In fact, I tried to get this very idea implemented at my company to much gnashing of teeth and rending of cloth. Never did understand the problem with it. I must be an old timer now too!!

-marc
CAD / PLM Systems Manager
TriMark Corporation

[DonSenchuk]

I also agree with Ronald's rant. What I've mostly been able to glean is that a lot of people simply can't wrap their heads around how layers work.

[davehaigh]

You don't even have to turn the layers on if you want to assembly via the datums, you can use the search tool to find them. I'm still kind of stuck in the old way of picking off the screen, but those folks that use the search tool, can do this really quickly.

David Haigh

[jnelson]

It takes a brave man to put himself out on the front line, late on a Friday afternoon.

Well done. Well said



Sent from my Verizon Wireless 4G LTE DROID


"Grabau, Ronald" <-> wrote:

OK, I don’t do this often but I am going to poke the pig and see what happens.

I am always amazed when parametric users don’t use layers to control the display of datums. As a standard rule we put all datums on layers and then save the status as hidden. This way you never have to worry about what the state of the datum display is. I am sure that everyone has turned on the datums to work on a part only to switch windows and get the assembly which can no longer be seen due to the datums. I have no idea how someone can work in this environment. I have to assume that users toggle the display off and then are forced to select from the model tree. I personally find that process unproductive. I don’t mean to pick on anyone here and get all the hate mail back but I guess I have a narrow perspective on this subject.

In my personal world I just turn on the datums for the assembly and any current parts that I am working on. I can do this since all models are saved with the datums in a hidden layer status. I would never want to see all the datums of all the parts while I am working on a part.

Some of my users complain that if they try and assemble a part with the layers hidden you cannot select the layer. I find this not to be true. You can switch to the layer tree and pick on the select icon and pick the model being assembled, you can then unhide the desired datums and do your work. When you are finished and save the layer status is still hidden and the next time you retrieve the assembly all the datums are off. You could argue that that process slows down the assembly of the component but I also would think it is difficult to place a component when you cannot see the assembly.

Here is a fairly simple board assembly. Why would you ever want to see this… ever?

[cid:image001.png@01CEF7E5.A7EFDFD0]

I would rather work with a model that looks like this

[cid:image004.jpg@01CEF7F6.47AA9460]

Maybe I am old fashion and just have not learned new tricks. Eventually I will retire and not bother people with my old way of thinking. But until then…

What I do hate is getting models from vendors that have layer names that are different from our standard. I see datums on all sorts of layers and this makes it difficult to work with. This is particularly true with set datums. For this reason I have a toolkit application that deletes all layers, creates the company standard layers and assigns features to the correct layers. You can run in on an entire assembly and it is recommended prior to putting it into our PDMLink system.

If you create layers with rules you get an automatic assignment so you don’t have to worry about getting things left off a layer. I use templates for our standard parts, assemblies and drawings just as many of you do. I also have the layer setup file set just in case someone decides to not use a template. My point is that once you set up a standard it makes dealing with all the datums pretty simple.

Yes, I still have mapkeys to toggle datums on and off but I don’t use them because I have too many datums showing in my assembly. I just want a picture with no datums or just don’t want to see them at that moment. (Yes I know I can shade the model…)

Anyway, just my 2 cents worth of Friday thoughts.

Have a good day and weekend!

Ronald B. Grabau
HP PDE-IT
Roseville, CA
916-785-3298
-<">mailto:->

[ptc-1932745]

I agree 100%. Sometime ago (Pro2001 or so) we implemented the suggested layer scheme provided by PTC with their start parts. Before this we had some models with layers 1-32, but most with no layers defined, along with no default planes or csys. Definitely a pain to use parts without consistent defined layers for assembly, NC, etc...

It is such a standard now that when I bring up older parts (rare) that don't have the (standard) layering scheme, I apply Modelcheck to delete the old layers and put all of the features on the 'correct' layers. The only problem left is how to get layer rules enforced, as Modelcheck will not create these rules, but manually puts features on the layers.

The only problem with layering features and hiding/showing layers, is in some commands (in WF5-CEP) I can't change the layer status when I am in the middle of a command. Maybe this will change in CREO2 or maybe 3. BTW, who at PTC thought 'Unhide' was a better choice than 'show' for layer visibility?

I think some of the real power of layers is that you can have 'meta' layers that will hide other layers, esp. in Assembly mode. Such as: 01_ASM_ALL_DTM_PLN in the default PTC assembly template will hide all datum planes.


Christopher F. Gosnell

FPD Company
124 Hidden Valley Road
McMurray, PA 15317

[mdebower]

Chris,

The only way I have found to easily create rule based layers is with a mapkey, actually a set of mapkeys. Works well once you have it set up.

-marc

[dgschaefer]

I love layers and the search tool, use them both extensively.

That said, layers are more complicated than they need to be. There's a lot of power and flexibility, but getting it set up and training users on it is a bear. I went through this a few years ago with Glenn Beer's excellent layer presentation from PTCUser 2007, I think (look it up at mcadcentral.com, it's excellent). I have a nice set up that really works well, I think, but users' eyes glass over when you explain it to them.

Thing is, in our world, we use the client's start parts & layer standards, so having our own, no matter how nice, frequently isn't very helpful.

--

[davehaigh]

Here's a set of rule based layer mapkeys. Modify the layer names to what you want.

!=========================================================
!== Layers ==
!=========================================================
mapkey fal @MAPKEY_LABELFIX ALL MODEL LAYERS;\
@MAPKEY_NAMEThis will modify all sub model components;\
%_2_delete_all;\
%_2_add_layers;\
%_2_extend_layers

mapkey fcl @MAPKEY_LABELFIX CURRENT MODEL LAYERS;\
@MAPKEY_NAMEThis will only modify the current model;\
%_2_delete_current;\
%_2_add_layers;

mapkey _2_delete_all @MAPKEY_LABELDELETE ALL MODEL LAYERS;\
~ Command `ProCmdMdlTreeShowLyrs`;\
~ Activate `main_dlg_cur` `LayerExpandAll`;\
~ Select `main_dlg_cur` `PHTLeft.PHLayerUI.AssyTree` 1 `node0`;\
~ RButtonArm `main_dlg_cur` `PHTLeft.PHLayerUI.AssyTree` `node0`;\
~ Command `ProCmdLayer_SelectLayers` ;\
~ RButtonArm `main_dlg_cur` `PHTLeft.PHLayerUI.AssyTree` \
`node0`;\
~ Command `ProCmdLayer_DelLay` ;\
~ Activate `UI Message Dialog` `yes`;

mapkey _2_delete_current @MAPKEY_LABELDELETE CURRENT MODEL LAYERS;\
~ Command `ProCmdMdlTreeShowLyrs`;\
~ Select `main_dlg_cur` `rad_list_layers_for` 1 `act_obj_and_lays`;\
~ Activate `main_dlg_cur` `LayerExpandAll`;\
~ Select `main_dlg_cur` `PHTLeft.PHLayerUI.AssyTree` 1 `node0`;\
~ RButtonArm `main_dlg_cur` `PHTLeft.PHLayerUI.AssyTree` `node0`;\
~ Command `ProCmdLayer_SelectLayers` ;\
~ RButtonArm `main_dlg_cur` `PHTLeft.PHLayerUI.AssyTree` \
`node0`;\
~ Command `ProCmdLayer_DelLay` ;\
~ Activate `UI Message Dialog` `yes`;\
~ Select `main_dlg_cur` `rad_list_layers_for` 1 `all_objs_and_lays`;

mapkey _2_add_layers @MAPKEY_LABELADD LAYERS;\
~ Command `ProCmdMdlTreeShowLyrs`;\
%_2_axis;\
%_2_cosm_sketch;\
%_2_csys;\
%_2_curve;\
%_2_plane;\
%_2_point;\
%_2_set_datum;\
%_2_surface;\
%_2_thread;

mapkey _2_extend_layers @MAPKEY_LABELEXTEND LAYERS TO SUB MODELS;\
~ Command `ProCmdMdlTreeShowLyrs`;\
~ Select `main_dlg_cur` `PHTLeft.PHLayerUI.AssyTree` 1 `node0`;\
~ RButtonArm `main_dlg_cur` `PHTLeft.PHLayerUI.AssyTree` `node0`;\
~ Command `ProCmdLayer_SelectLayers` ;\
~ Command `ProCmdLayer_ExtendRules`;

mapkey _2_axis @MAPKEY_LABELAXIS LAYER;\
~ RButtonArm `main_dlg_cur` `PHTLeft.PHLayerUI.AssyTree` `node0`;\
~ Command `ProCmdLayer_NewLay` ;\
~ Update `newlayerprops` `LayerNameInput` `_2_AXIS`;\
~ Select `newlayerprops` `PropTab` 1 `RulesDefsettingsLay`;\
~ Activate `newlayerprops` `EditRulesBtn`;\
~ Select `selspecdlg0` `SelOptionRadio` 1 `Feature`;\
~ Select `selspecdlg0` `LookByOptionMenu` 1 `Feature`;\
~ Select `selspecdlg0` `RuleTab` 1 `Attributes`;\
~ Select `selspecdlg0` `RuleTypes` 1 `Type`;\
~ Select `selspecdlg0` `ExtRulesLayout.ExtTyperuleLayout.TyperuleCatsList` 1 \
`Misc`;\
~ Select `selspecdlg0` `ExtRulesLayout.ExtTyperuleLayout.TyperuleTypesList` \
1 `has axes#4, 92`;\
~ Activate `selspecdlg0` `AddRuleBtn`;\
~ Activate `selspecdlg0` `SelectButton`;\
~ Activate `newlayerprops` `AssocRulesChk` 1;\
~ Activate `newlayerprops` `OkBtn`;

mapkey _2_cosm_sketch @MAPKEY_LABELCOSMETIC LAYER;\
~ RButtonArm `main_dlg_cur` `PHTLeft.PHLayerUI.AssyTree` `node0`;\
~ Command `ProCmdLayer_NewLay` ;\
~ Update `newlayerprops` `LayerNameInput` `_2_COSM_SKETCH`;\
~ Select `newlayerprops` `PropTab` 1 `RulesDefsettingsLay`;\
~ Activate `newlayerprops` `EditRulesBtn`;\
~ Select `selspecdlg0` `SelOptionRadio` 1 `Feature`;\
~ Select `selspecdlg0` `LookByOptionMenu` 1 `Feature`;\
~ Select `selspecdlg0` `RuleTab` 1 `Attributes`;\
~ Select `selspecdlg0` `RuleTypes` 1 `Type`;\
~ Select `selspecdlg0` `ExtRulesLayout.ExtTyperuleLayout.TyperuleCatsList` 1 \
`All`;\
~ Select `selspecdlg0` `ExtRulesLayout.ExtTyperuleLayout.TyperuleTypesList` \
1 `Cosmetic#2, 45`;\
~ Activate `selspecdlg0` `AddRuleBtn`;\
~ Activate `selspecdlg0` `SelectButton`;\
~ Activate `newlayerprops` `AssocRulesChk` 1;\
~ Activate `newlayerprops` `OkBtn`;

mapkey _2_csys @MAPKEY_LABELCSYS LAYER;\
~ RButtonArm `main_dlg_cur` `PHTLeft.PHLayerUI.AssyTree` `node0`;\
~ Command `ProCmdLayer_NewLay` ;\
~ Update `newlayerprops` `LayerNameInput` `_2_CSYS`;\
~ Select `newlayerprops` `PropTab` 1 `RulesDefsettingsLay`;\
~ Activate `newlayerprops` `EditRulesBtn`;\
~ Select `selspecdlg0` `SelOptionRadio` 1 `Feature`;\
~ Select `selspecdlg0` `LookByOptionMenu` 1 `Feature`;\
~ Select `selspecdlg0` `RuleTab` 1 `Attributes`;\
~ Select `selspecdlg0` `RuleTypes` 1 `Type`;\
~ Select `selspecdlg0` `ExtRulesLayout.ExtTyperuleLayout.TyperuleCatsList` 1 \
`Datum`;\
~ Select `selspecdlg0` `ExtRulesLayout.ExtTyperuleLayout.TyperuleTypesList` \
1 ` Coordinate System#1, 979`;\
~ Activate `selspecdlg0` `AddRuleBtn`;\
~ Activate `selspecdlg0` `SelectButton`;\
~ Activate `newlayerprops` `AssocRulesChk` 1;\
~ Activate `newlayerprops` `OkBtn`;

mapkey _2_curve @MAPKEY_LABELCURVE LAYER;\
~ RButtonArm `main_dlg_cur` `PHTLeft.PHLayerUI.AssyTree` `node0`;\
~ Command `ProCmdLayer_NewLay` ;\
~ Update `newlayerprops` `LayerNameInput` `_2_CURVE`;\
~ Select `newlayerprops` `PropTab` 1 `RulesDefsettingsLay`;\
~ Activate `newlayerprops` `EditRulesBtn`;\
~ Select `selspecdlg0` `SelOptionRadio` 1 `Feature`;\
~ Select `selspecdlg0` `LookByOptionMenu` 1 `Feature`;\
~ Select `selspecdlg0` `RuleTab` 1 `Attributes`;\
~ Select `selspecdlg0` `RuleTypes` 1 `Type`;\
~ Select `selspecdlg0` `ExtRulesLayout.ExtTyperuleLayout.TyperuleCatsList` 1 \
`Datum`;\
~ Select `selspecdlg0` `ExtRulesLayout.ExtTyperuleLayout.TyperuleTypesList` \
1 ` Curve#1, 949`;\
~ Activate `selspecdlg0` `AddRuleBtn`;\
~ Activate `selspecdlg0` `SelectButton`;\
~ Activate `newlayerprops` `AssocRulesChk` 1;\
~ Activate `newlayerprops` `OkBtn`;

mapkey _2_plane @MAPKEY_LABELPLANE LAYER;\
~ RButtonArm `main_dlg_cur` `PHTLeft.PHLayerUI.AssyTree` `node0`;\
~ Command `ProCmdLayer_NewLay` ;\
~ Update `newlayerprops` `LayerNameInput` `_2_PLANE`;\
~ Select `newlayerprops` `PropTab` 1 `RulesDefsettingsLay`;\
~ Activate `newlayerprops` `EditRulesBtn`;\
~ Select `selspecdlg0` `SelOptionRadio` 1 `Feature`;\
~ Select `selspecdlg0` `LookByOptionMenu` 1 `Feature`;\
~ Select `selspecdlg0` `RuleTab` 1 `Attributes`;\
~ Select `selspecdlg0` `RuleTypes` 1 `Type`;\
~ Select `selspecdlg0` `ExtRulesLayout.ExtTyperuleLayout.TyperuleCatsList` 1 \
`Datum`;\
~ Select `selspecdlg0` `ExtRulesLayout.ExtTyperuleLayout.TyperuleTypesList` \
1 ` Datum#1, 923`;\
~ Activate `selspecdlg0` `AddRuleBtn`;\
~ Activate `selspecdlg0` `SelectButton`;\
~ Activate `newlayerprops` `AssocRulesChk` 1;\
~ Activate `newlayerprops` `OkBtn`;

mapkey _2_point @MAPKEY_LABELPOINT LAYER;\
~ RButtonArm `main_dlg_cur` `PHTLeft.PHLayerUI.AssyTree` `node0`;\
~ Command `ProCmdLayer_NewLay` ;\
~ Update `newlayerprops` `LayerNameInput` `_2_POINT`;\
~ Select `newlayerprops` `PropTab` 1 `RulesDefsettingsLay`;\
~ Activate `newlayerprops` `EditRulesBtn`;\
~ Select `selspecdlg0` `SelOptionRadio` 1 `Feature`;\
~ Select `selspecdlg0` `LookByOptionMenu` 1 `Feature`;\
~ Select `selspecdlg0` `RuleTab` 1 `Attributes`;\
~ Select `selspecdlg0` `RuleTypes` 1 `Type`;\
~ Select `selspecdlg0` `ExtRulesLayout.ExtTyperuleLayout.TyperuleCatsList` 1 \
`Datum`;\
~ Select `selspecdlg0` `ExtRulesLayout.ExtTyperuleLayout.TyperuleTypesList` \
1 ` Datum Point#1, 931`;\
~ Activate `selspecdlg0` `AddRuleBtn`;\
~ Activate `selspecdlg0` `SelectButton`;\
~ Activate `newlayerprops` `AssocRulesChk` 1;\
~ Activate `newlayerprops` `OkBtn`;

mapkey _2_set_datum @MAPKEY_LABELSET DATUM LAYER;\
~ RButtonArm `main_dlg_cur` `PHTLeft.PHLayerUI.AssyTree` `node0`;\
~ Command `ProCmdLayer_NewLay` ;\
~ Update `newlayerprops` `LayerNameInput` `_2_SET_DATUM`;\
~ Select `newlayerprops` `PropTab` 1 `RulesDefsettingsLay`;\
~ Activate `newlayerprops` `EditRulesBtn`;\
~ Select `selspecdlg0` `SelOptionRadio` 1 `Set Datum Tag`;\
~ Select `selspecdlg0` `RuleTypes` 1 `All`;\
~ Activate `selspecdlg0` `AddRuleBtn`;\
~ Select `selspecdlg0` `SelOptionRadio` 1 `Shown Datum Axis`;\
~ Select `selspecdlg0` `RuleTypes` 1 `All`;\
~ Activate `selspecdlg0` `AddRuleBtn`;\
~ Select `selspecdlg0` `SelOptionRadio` 1 `Dtl Datum`;\
~ Select `selspecdlg0` `RuleTypes` 1 `All`;\
~ Activate `selspecdlg0` `AddRuleBtn`;\
~ Activate `selspecdlg0` `SelectButton`;\
~ Activate `newlayerprops` `AssocRulesChk` 1;\
~ Activate `newlayerprops` `OkBtn`;

mapkey _2_surface @MAPKEY_LABELSURFACE LAYER;\
~ RButtonArm `main_dlg_cur` `PHTLeft.PHLayerUI.AssyTree` `node0`;\
~ Command `ProCmdLayer_NewLay` ;\
~ Update `newlayerprops` `LayerNameInput` `_2_SURFACE`;\
~ Select `newlayerprops` `PropTab` 1 `RulesDefsettingsLay`;\
~ Activate `newlayerprops` `EditRulesBtn`;\
~ Select `selspecdlg0` `SelOptionRadio` 1 `Feature`;\
~ Select `selspecdlg0` `LookByOptionMenu` 1 `Feature`;\
~ Select `selspecdlg0` `RuleTab` 1 `Attributes`;\
~ Select `selspecdlg0` `RuleTypes` 1 `Type`;\
~ Select `selspecdlg0` `ExtRulesLayout.ExtTyperuleLayout.TyperuleCatsList` 1 \
`All`;\
~ Select `selspecdlg0` `ExtRulesLayout.ExtTyperuleLayout.TyperuleTypesList` \
1 ` Surface#1, 942`;\
~ Activate `selspecdlg0` `AddRuleBtn`;\
~ Activate `selspecdlg0` `SelectButton`;\
~ Activate `newlayerprops` `AssocRulesChk` 1;\
~ Activate `newlayerprops` `OkBtn`;

mapkey _2_thread @MAPKEY_LABELTHREAD LAYER;\
~ RButtonArm `main_dlg_cur` `PHTLeft.PHLayerUI.AssyTree` `node0`;\
~ Command `ProCmdLayer_NewLay` ;\
~ Update `newlayerprops` `LayerNameInput` `_2_THREAD`;\
~ Select `newlayerprops` `PropTab` 1 `RulesDefsettingsLay`;\
~ Activate `newlayerprops` `EditRulesBtn`;\
~ Select `selspecdlg0` `SelOptionRadio` 1 `Feature`;\
~ Select `selspecdlg0` `LookByOptionMenu` 1 `Feature`;\
~ Select `selspecdlg0` `RuleTab` 1 `Attributes`;\
~ Select `selspecdlg0` `RuleTypes` 1 `Type`;\
~ Select `selspecdlg0` `ExtRulesLayout.ExtTyperuleLayout.TyperuleCatsList` 1 \
`Misc`;\
~ Select `selspecdlg0` `ExtRulesLayout.ExtTyperuleLayout.TyperuleTypesList` \
1 `is thread#4, 93`;\
~ Activate `selspecdlg0` `AddRuleBtn`;\
~ Activate `selspecdlg0` `SelectButton`;\
~ Activate `newlayerprops` `AssocRulesChk` 1;\
~ Activate `newlayerprops` `OkBtn`;



David Haigh

[TimMcLellan]

Did you know... You can actually just, select all layers from a part/assembly, copy and paste them directly into a new part/assembly.

I think Karl Krahmer wrote this up on the exploder at some point.
Tim McLellan
Mobius Innovation and Development, Inc.

[mlocascio]

That's a pretty cool idea! Did you try it to see if it works?



Michael P. Locascio

[TimMcLellan]

Yes, I have been using it for some time. The only minor annoyance if you automate (mapkey) is you have to include an "activate window" in order to paste the layers... but all rules included.
Cheers,
Tim McLellan
Mobius Innovation and Development, Inc.

[mlocascio]

I really like what you had to say. For most models I am inclined to keep the
display of datum planes as visible as possible. Then I find that your
methods are necessary when I am working with complex assemblies.



Somehow I find that having the options of layering and switching off display
of items helps me out rather well. When life gets tough I go for the
simplified rep. That's just another tool for us Pro/E users.



Michael P. Locascio