System Control Overview | Statement List
A pattern is a collection of objects from a "master" part file that can be placed into your current part file as many times as necessary.
A pattern is a single object, both from your point of view (e.g. transformations, etc.) and from the system's point of view. From the system's point of view, a pattern is counted as only one object in the part file data base. This means that your current part can contain many patterns created from extremely large files without making your current part file large.
Keeping the data in your part file as small as possible enhances system performance, and reduces the disk space and memory requirements of your system.
Filing a part with pattern data makes that part file larger than it would be if it did not contain pattern data. This space is however saved in all other part files in which this part is represented as a pattern rather than the individual objects.
Each time a part file containing a pattern is retrieved, the pattern graphics is re-retrieved from the master file. This has several implications.
Any changes that have been made and filed with the master are automatically reflected in the part file containing the pattern when the part file is retrieved. This fact can be an advantage or a detriment.
This is advantageous since it allows you to quickly make changes to standard parts such as bolts, symbols, or drawing formats. You simply retrieve the master file, make your changes, and refile the part.
However, this also means that when you make changes to a master file, your changes automatically affect anyone else who has used that file to merge a pattern. This means that you should be very conscious of the effect of a change before you incorporate it.
The following GPAs and EDAs support patterns:
&PATPRT
&PATSCL
&PATDAT
For more detailed information on patterns, see the Gateway Help.