Autodesk 00128-051462-9310 - AUTOCAD 2008 COMM UPG FRM 2005 DVD, User Manual

Page: 2199 / 2268

<AcadHatchProps>
<HatchAlias>brick</HatchAlias>
</AcadHatchProps>
<AcadHatchProps>
<HatchAlias ref="dbTable">PAT_ALIAS</HatchAlias>
</AcadHatchProps>
<AcadHatchProps>
<PatternName>Escher</PatternName>
<PatternScale>4.0</PatternScale>
<PatternAngle>45.0</PatternAngle>
</AcadHatchProps>
The following Elements can be specified within < AcadHatchProps >:
Description Element
The name of an Alias from the Detail Component database’s Hatches
table. This table is used so that you can centrally define the Pattern,
Scale, and Angle for representative materials used throughout the
database. Most RecipeSpecs will use a Hatch Alias to define all the
parameters of the Hatch. However, you can specify these values
directly by using the other elements. <HatchAlias> [Optional]
Possible values are: “PreDefined” (the default), “User”, or “Custom”. <PatternType> [Optional]
If the <PatternName> specified (or indirectly referenced from
<HatchAlias>) does not exist, the pattern “ANSI31” is used. <PatternName> [Optional]
<PatternScale> [Optional]
<PatternMultiplier> [Optional]
<PatternAngle> [Optional]
<PatternDouble> [Optional]
<PatternSpace> [Optional]
<Params>
This Element specifies the parameters specific to this particular Recipe. These are typically values that the Recipe needs,
but that are not hardwired into the code, and thus are customizable. Here are a few examples:
<Item idStr="boundary">
<Params>
<Tongue>0.125</Tongue>
<GrooveSpacing>0.03125</GrooveSpacing>
</Params>
</Item>
<Item idStr="boundary">
<Params>
<Chamfer>0.5</Chamfer>
</Params>
</Item>
The Element names are defined by the Rcp function itself and must be known in advance of editing them in the Recipe
Spec.
NOTE One way to find out the implied contract of the Rcp function is to turn on logging. For more information, see “ Recipe
Logging ” on page 2165 .
<Options> Section
This section provides customization data that is used by the placement phase (Jig) of the Rcp function. In most cases,
Recipe functions divide their labor into two phases:
1 Creation of the component
2 Placement of the component
Recipe Specifications | 2159