ALL DATUMS - OFF

[agaribay]

I'm sure this has been asked before, but...



Is it possible to create a layer that would turn off ALL Datums whether
it be a part or assembly.



Thank you!



-Art



WF2


.

.

This message (including any attachments) contains

confidential and/or proprietary information intended

only for the addressee. Any unauthorized disclosure,

copying, distribution or reliance on the contents of this

information is strictly prohibited and may constitute a violation

of law. If you are not the intended recipient, please notify the

sender immediately by responding to this e-mail, and delete the

message from your system. If you have any questions about this

e-mail please notify the sender immediately.

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.

[brianlynn]

Yes it is possible, it might be a struggle for those who do not understand
layers well.

Brian S. Lynn
Technical Coordinator, Product Engineering

[kimndave9]

Yes and no. Why do you ask? If the following doesn't cover it well
enough, more detail will help.

The yes part is that layers are maintained as lists within the relevant
items. Each list is separate, but if the lists share a name they are
collected under that name at higher assembly levels.

If all the parts and assemblies along the way have all their layers on
identically named lists, then you can select the name at the top of the
list and switch it to being invisible. It is easiest to do this with a
layer rule that is applied to all layers. My preference is a rule that
puts datums on a 'datums' layer unless the datum is a shown datum (via
the Set Datum command) in which case it does not go on the 'datums'
layer. A separate rule adds the set datums to the 'Set_datum' layer so
their forced visibility can be countered.

The no part is that datums that are not on a layer won't turn off via
layers. If the part/assy is protected from change, the layer change may
not be permanent, depending on how long permanent is and if the
protection can be overridden.



Art Garibay wrote:
>
> I'm sure this has been asked before, but...
>
>
>
> Is it possible to create a layer that would turn off *_ALL Datums_*
> whether it be a part or assembly.
>
>
>
> Thank you!
>
>
>
> -Art
>
>
>
> WF2
>
> . . This message (including any attachments) contains confidential
> and/or proprietary information intended only for the addressee. Any
> unauthorized disclosure, copying, distribution or reliance on the
> contents of this information is strictly prohibited and may constitute
> a violation of law. If you are not the intended recipient, please
> notify the sender immediately by responding to this e-mail, and delete
> the message from your system. If you have any questions about this
> e-mail please notify the sender immediately.
>

[gkbeer]

Art,

In your top assembly, and all submodels, delete all layers named PLANES. Alternately rename them, Alternately edit these mapkeys and replace PLANES with the name you prefer.

Run these three mapkeys in the order listed. Hide the layer PLANES.

Note: This only impacts datum planes that are features. Datums that are in copy geoms will not be impacted.

You can use a modification of the techniques embodied in the second mapkey, to find the planes(entities) instead of Datum plane features. In which case the planes layers will include the planes that are copy geoms.

Luck, Glenn Beer

mapkey /resetfind @MAPKEY_NAMEReset Find;@MAPKEY_LABELReset Find;\
mapkey(continued) ~ Activate `main_dlg_cur` `ProCmdMdlTreeSearch.edit_t`;\
mapkey(continued) ~ Update `selspecdlg0` `SelOptionRadio` `Feature`;\
mapkey(continued) ~ Activate `selspecdlg0` `SelOptionRadio`;\
mapkey(continued) ~ Update `selspecdlg0` `LookByOptionMenu` `Feature`;\
mapkey(continued) ~ Activate `selspecdlg0` `LookByOptionMenu`;\
mapkey(continued) ~ Select `selspecdlg0` `RuleTab` 1 `Attributes`;\
mapkey(continued) ~ Select `selspecdlg0` `RuleTypes` 1 `Name`

mapkey /lay_planes ~ Activate `main_dlg_cur` `ProCmdMdlTreeSearch.edit_t`;\
mapkey(continued) ~ Activate `selspecdlg0` `SelScopeCheck` ;0;\
mapkey(continued) ~ Update `selspecdlg0` `SelOptionRadio` `Feature`;\
mapkey(continued) ~ Activate `selspecdlg0` `SelOptionRadio`;\
mapkey(continued) ~ Update `selspecdlg0` `LookByOptionMenu` `Feature`;\
mapkey(continued) ~ Activate `selspecdlg0` `LookByOptionMenu`;\
mapkey(continued) ~ Select `selspecdlg0` `RuleTab` 1 `Attributes`;\
mapkey(continued) ~ Select `selspecdlg0` `RuleTypes` 1 `Type`~ Select `selspecdlg0` \
mapkey(continued) `ExtRulesLayout.ExtTyperuleLayout.TyperuleComp`1 ` == `;\
mapkey(continued) ~ Update `selspecdlg0` \
mapkey(continued) `ExtRulesLayout.ExtTyperuleLayout.TyperuleCatsList``Datum`;\
mapkey(continued) ~ Update `selspecdlg0` \
mapkey(continued) `ExtRulesLayout.ExtTyperuleLayout.TyperuleTypesList``Datum Plane`;\
mapkey(continued) ~ Activate `selspecdlg0` \
mapkey(continued) `ExtRulesLayout.ExtTyperuleLayout.TyperuleTypesList`;\
mapkey(continued) ~ Close `selspecdlg0` `CascadeButton1`;\
mapkey(continued) ~ Activate `selspecdlg0` `SaveResults`;\
mapkey(continued) ~ Update `save_rules_dlg` `LayNamePanel` `planes`;\
mapkey(continued) ~ Activate `save_rules_dlg` `OKBtn`;~ Activate `selspecdlg0` `CancelButton`;

mapkey /ext @MAPKEY_NAMEPropagate selected layers and rules to submodels;\
mapkey(continued) @MAPKEY_LABELExtend Layers;\
mapkey(continued) ~ RButtonArm `main_dlg_cur` `PHTLeft.PHLayerUI.AssyTree` `node0`;\
mapkey(continued) ~ PopupOver `main_dlg_cur` `LayerActionMenu`1 `PHTLeft.PHLayerUI.AssyTree`;\
mapkey(continued) ~ Open `main_dlg_cur` `LayerActionMenu`;\
mapkey(continued) ~ Close `main_dlg_cur` `LayerActionMenu`;\
mapkey(continued) ~ Activate `main_dlg_cur` `ActionMenuTreeSearch`;\
mapkey(continued) ~ Activate `layertreequery` `AddBtn`;\
mapkey(continued) ~ Select `layertreequery` `ValueList`1 `PLANES`;\
mapkey(continued) ~ Activate `layertreequery` `AddBtn`;\
mapkey(continued) ~ Activate `layertreequery` `FindNextBtn`;\
mapkey(continued) ~ Activate `layertreequery` `SelectAllBtn`;\
mapkey(continued) ~ Activate `layertreequery` `layertreequery`;\
mapkey(continued) ~ Select `main_dlg_cur` `PHTLeft.PHLayerUI.LayerEditCasc`;\
mapkey(continued) ~ Close `main_dlg_cur` `PHTLeft.PHLayerUI.LayerEditCasc`;\
mapkey(continued) ~ Activate `main_dlg_cur` `PropagateBtn`;\
mapkey(continued) ~ Activate `layertreequery` `CloseBtn`;

[gkbeer]

Dave,

I find it works well to have all datum planes on one layer, including the set datums.

Then have another layer with the set datums only.

Compounded rules are not needed.

The key to making it work is to use the Hide to make all items on all layers invisible, then use Isolate to make the items on selected layers visible.

(Just know that if attention isn't paid as to what kinds of items are being put on layers the results may be surprising.)

[brianlynn]

Another great solution is once you have all your datums on an appropriate
layer like AXIS, then create a layer call 00_ALL_DATUMS, which will sort
to the top of the list because of the "00" at the beginning, and then
assign the datum appropriate layers to this one then all you have to do is
hide the 00_ALL_DATUMS layer and all the other datum layers will hide
automatically. This will also allow you to hide everything and then if you
are working allow you to unhide the datum planes without unhiding
everything else.

This is how we have been doing things since 1999, after I went to Ted
Bradshaw's MAD (Master Assembly Design) class at the end of the PTC/User
conference. People were slow to understand the benefits now I think
someone who get smacked down if they attempt to change our layer scheme.

Hope that helps,

Brian S. Lynn
Technical Coordinator, Product Engineering