Pinned Datums

Datums can be Pinned to the location at which they were created using RMB > Pinned.

Pinned Datums will move if their creation references are moved.

If a Datum is created and subsequently moved from its original (created) position (with respect to its creation references) Pinned will be grayed out.

The following apply to all pinned datums:

• Pinned datum icons in the tree are highlighted to distinguish them from normal.
• Ctrl+drag to copy in the Move tool works for all pinned datums. The original datum remains pinned but the new copy is unpinnable.
• Datum Planes and Axes are now automatically unpinned when they can no longer be constructed from the reference objects. For example, when a reference face is changed from a plane to a cylinder.
• The Datum Plane, Line, and Point tools are sticky (they stay on until you enter another tool) like normal tools.
• If any of a Pinned Datum's references are deleted, the system forces the datum to be unpinned. The datum will not be placed with respect to the remaining references. This applies to Planes, Lines, and Points.
• Datum Planes, Lines, and Points that are constructed exclusively from other pinned datums become pinned by default. For example, a datum axis will be pinned by default if it is constructed from a point pinned to a face.
• The Move handle is disabled when all selected objects are pinned datums (axes, planes). Since they are pinned, these objects cannot be Moved. If unpinned datums, or other objects, are included in the selection, the Move handle is enabled, but the pinned datums will not Move. To allow copying, the Move handle becomes enabled when the Ctrl key is pressed.

The following apply to pinned datums in components:

• You can Cut/Copy/Paste by parent component.
• You can set the Visibility by parent component.
• Note that when pinned datums are moved to a new component, they become unpinned and subsequently unpinnable
• Datums can only be pinned if All of the references are in the same component. Allowing references from multiple components can result in unintentional Assembly-like constraints.