PATEXP/obj[,GROUP][,LAYER][,NOVIEW][,PLMODS,value][,IFERR,label:]
Expands the specified pattern object into the full geometry it represents. This statement deletes the specified pattern object and then merges the corresponding part using the scale, orientation, and location of the pattern object.
NOTE: The interactive defaults for File¡ª>Import¡ª>Part sets
values for the following parameters:
Create named group = ON
Layer Mode = WORK
Import views = OFF
To match these settings use the GROUP and NOVIEW minor words. Please see the UG Gateway Help for a detailed description of File¡ª>Import¡ª>Part.
Parameter |
Description |
obj |
A previously defined pattern object which is to be expanded. |
GROUP |
Minor word which indicates that a group containing all of the objects in the part being merged is to be created during the retrieval. If not specified, no group is created. |
LAYER |
Minor word which retrieves the part onto the same layers as when it was created. If not specified, the part is retrieved onto the work layer. |
NOVIEW |
Minor word which indicates that no views are merged when the part is merged. The geometry is merged into the existing views based on the current construction mode (model or view dependent). If not specified, the views in the part being merged are also merged. |
PLMODS |
Minor word which indicates that a parts list parameter is to be specified. |
value |
Integer value which specifies how parts list data associated with the part being merged is handled. Value must range from 1 to 4 as follows: |
Value |
Description |
1 |
No parts list information is merged. This is the default value. |
2 |
Default parts list format data is merged. When merged, this data replaces the parts list format data of the current part. |
3 |
The merged part is added to the parts list as a single group (one object entry). |
4 |
All parts list entries on the merged part are added individually to the parts list data of the current part. The parts list format data is also merged. |
IFERR,label: |
Specifies a label to which program execution jumps if an error occurs during part file retrieval. Possible errors include: parts list parameter must be [1,4]; invalid object specified; object is not a pattern; part file not found; part failed revision check; unable to read solids. |