30.07.2013 Views

T-FLEX Parametric CAD. Fundamentals. 2D Design

T-FLEX Parametric CAD. Fundamentals. 2D Design

T-FLEX Parametric CAD. Fundamentals. 2D Design

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Creating Custom Lines and Hatches<br />

When creating a pattern, one can use graphic elements of different color and different width. However, the<br />

color and width of a graphic line created from a custom type can be modified only if the whole pattern uses<br />

the same color and line width.<br />

The line elements may be of a quite complex shape. When a hatch is created based on graphic lines of a<br />

custom type, the hatch contour will not follow the line shape by default; instead, it will be composed of line<br />

segments passing through the characteristic points of the line elements. To make the hatch contour exactly<br />

follow the line or assume other arbitrary shape, you would need to specify additional <strong>2D</strong> paths with special<br />

names in the line pattern drawing defining the hatch contour route.<br />

The paths are created separately for each line element. Each path must lie on the same page as the respective<br />

line element. The path must start and end at characteristic nodes of its element and be named as one of the<br />

following: “Polyline” – the path of the periodical part, “TailPolyline” – the start path, “HeadPolyline” – the<br />

end path, and “CenterPolyline” – the path of the center part.<br />

Working with Custom-type Line<br />

To start using a created line type, simply place the line pattern file in the folder<br />

…\Program\LinePatterns. Upon restarting T-<strong>FLEX</strong> <strong>CAD</strong>, the line types found in this folder will be<br />

automatically added to the lists of line types in <strong>2D</strong> commands. To delete a custom line type, simply delete<br />

the pattern drawing file from …\Program\LinePatterns and restart T-<strong>FLEX</strong> <strong>CAD</strong>.<br />

When using a custom line type in a document, the line pattern is saved with that document. Relation with the<br />

source file is lost at this point. Therefore, when porting a document file to a computer without the given line<br />

type, the image does not get lost.<br />

When porting a document containing custom line types to a computer with existing line type pattern under<br />

the same name, the line image stays unchanged in the form of the image saved in the document. To update a<br />

line image, you would need to redefine its type over again. To make an update, all you need is to bring up the<br />

parameters dialog box for one of the lines and confirm the existing value. New graphic lines of the same type<br />

that will be created in this document will take on the current pattern.<br />

Example of Creating Custom Line<br />

Let’s review custom line creation on a simple example. We will create the line pattern shown on the figure.<br />

First of all, let’s decide on the elements to be included in this line. The figure features: the periodical part –<br />

interlaced crosses and segments; center part entered just once – the text “Test”; start and end as special<br />

symbols.<br />

Periodic part<br />

Start Center part<br />

End<br />

To create the pattern, let’s open a new <strong>2D</strong> drawing (the command “FN: Create New Model”).<br />

Description of each line element shall be placed on a separate page of the document. We will create four<br />

pages in the pattern document. For working convenience, each page can be renamed according to its purpose.<br />

To create or rename document pages, use the command “PG: Pages”.<br />

When creating descriptor drawings of line types, one can use either use simple sketched lines, or graphic<br />

lines snapped to construction lines. For simplicity, we will use free-hand sketching.<br />

703

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!