<!DOCTYPE html
  PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

<!--
Copyright (c) 2006 UGS Corp.

All Rights Reserved.

This software and related documentation are proprietary to UGS Corp.
-->
<html>
   <head>
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <title>Settings tab</title>
      <script language="javaScript">
        abridged="false";
        displayConditions=new Array();
      </script>
      <link type="text/css" href="../css/main_styles.css" rel="stylesheet">
   </head>
   <body class="bodydocs" onload="top.pageLoader()" bgcolor="#FFFFFF">
      <div class="title_topic5" id="xps10_pagetitle">Settings tab</div>
      <hr noshade="true">
      <p class="para_topic">The <b class="uiTerm">Settings</b> tab allows options that direct specified overall control of <b class="uiTerm">Create Path</b>. 
      </p>
      <ul>
         <li>
            <p class="para_item"><b class="uiTerm">Create Smart RCPs</b> &ndash; Checking this option causes RCPs created by <b class="uiTerm">Create Path</b> to be associative if you select objects in the work part during path creation. RCPs created in space (no objects selected, only cursor position or absolute positioning) are still created unassociative (as they have nothing with which to be associated to). To expand the scope of <b class="uiTerm">Create Smart RCPs</b>, see <b class="uiTerm">Use Interpart Extracts</b>.
            </p>
         </li>
         <li>
            <p class="para_item"><b class="uiTerm">Use Interpart Extracts</b> &ndash; This option is only available if <b class="uiTerm">Create Smart RCPs</b> is selected. Selecting <b class="uiTerm">Use Interpart Extracts</b> allows RCPs to be associative to objects outside of the current work part.
            </p>
         </li>
         <li>
            <p class="para_item"><b class="uiTerm">Assign Stock</b> &ndash; The <b class="uiTerm">Assign Stock</b> drop down menu specifies the stock to assign to segments as they create. The available methods are:
            </p>
            <ul>
               <li>
                  <p class="para_item"><b class="uiTerm">None</b> &ndash; No stock is assigned to segments as they are created.
                  </p>
               </li>
               <li>
                  <p class="para_item"><b class="uiTerm">Default</b> &ndash; The stock specified as the default stock in the <b class="uiTerm">Preferences</b>, assigns to newly created segments.
                  </p>
               </li>
               <li>
                  <p class="para_item"><b class="uiTerm">Start Object</b> &ndash; The assigned stock is determined by the <b class="uiTerm">Destination Characteristic</b> assigned to the selected start object. For example, if the selected start object is a port on a value having the <b class="uiTerm">Destination Characteristic</b> NPS with a value of 10, the assigned stock is that stock with NPS=10. If the <b class="uiTerm">Destination Characteristics</b> are not sufficient to determine a specific stock type, the default stock is used.
                  </p>
               </li>
            </ul>
         </li>
         <li>
            <p class="para_item"><b class="uiTerm">Assign Default Elbow</b> &ndash; <b class="uiTerm">Preferences</b> has a setting for the default elbow type. &nbsp;If you turn on <b class="uiTerm">Assign Default Elbow</b>, elbows are automatically placed into the path, provided a suitable elbow is available.
            </p>
         </li>
      </ul>
      <p class="para_topic">A suitable elbow is one that:</p>
      <ol type="1" start="1">
         <li>
            <p class="para_item">Belongs to the same part table as the default elbow defined in <b class="uiTerm">Preferences</b>.
            </p>
         </li>
         <li>
            <p class="para_item">Is the one and only elbow in the part table that matches the <b class="uiTerm">Destination Characteristics</b> of the path.
            </p>
         </li>
         <li>
            <p class="para_item">Has the same value for the characteristic ELBOW_ANG as the angle between the current segment created and the last previous segment created.</p>
         </li>
      </ol>
      <p class="para_topic">If the system does not find a suitable elbow, path creation continues by simply not placing an elbow. If you are not sure why an elbow does not place, see the NX Log File for a message that explains the reason the elbow could not be placed.</p>
      <ul>
         <li>
            <p class="para_item"><b class="uiTerm">Assign Default Corners</b> &ndash; When turned on, this automatically creates a bend corner at the junction of two newly created segments. The bend radius used is the default bend radius from <b class="uiTerm">Preferences</b>.
            </p>
         </li>
         <li>
            <p class="para_item"><b class="uiTerm">Generate Splines</b> &ndash; When turned on, splines create during path creation for the <b class="uiTerm">Simple Path Specify Points</b> mode and <b class="uiTerm">Heal Path</b> mode. The program must allow splines for this functionality to be available.
            </p>
         </li>
         <li>
            <p class="para_item"><b class="uiTerm">By Points</b> &ndash; The spline construction is done by through points when you create segments with splines. When in <b class="uiTerm">Shape</b> mode, adopted splines create by points.
            </p>
         </li>
         <li>
            <p class="para_item"><b class="uiTerm">By Poles</b> &ndash; The spline construction will be done by poles when you create segments with splines. Adopted splines are created by poles when in <b class="uiTerm">Shape</b> mode.
            </p>
         </li>
      </ul>
   </body>
</html>