Adobe FRAMEMAKER 10 - Page 113

ADOBE FRAMEMAKER 10
MIF Reference
108
DashSegment values
If the DashedStyle statement has a value of Dashed, the following DashSegment statements describe the dashed
pattern. The value of a
DashSegment statement specifies the length of a line segment or a gap in a dashed line. See
the online manual Customizing Adobe FrameMaker for information on changing default dashed patterns in UNIX
versions of FrameMaker. In Windows versions, edit the
maker.ini file in the directory where FrameMaker is
installed. See Customizing Adobe FrameMaker for more information. You can also define custom dash patterns. For
examples, see “Custom dashed lines” on page 225.
Values for the RunaroundType and RunaroundGap statements
The RunaroundType and RunaroundGap statements specify the styles used for the runaround properties of objects:
• If the RunaroundType statement is set to Contour, text flows around objects in the shape of the contours of the
objects. The
RunaroundGap statement specifies the distance between the objects and the text that flows around
them.
• If the RunaroundType statement is set to Box, text flows around objects in the shape of boxes surrounding the
objects. The
RunaroundGap statement specifies the distance between the objects and the text that flows around
them.
• If the RunaroundType statement is set to None, text doesn’t flow around objects, and the value specified by the
RunaroundGap statement is ignored.
Objects inherit the values of these statements from previous objects. Since these statements are used only to change
the inherited value from a previous object, the statements are not needed for every object. For example, if you write
out a MIF file, not all objects will contain these statements.
If these statements do not appear in an object or MIF file, the following rules apply:
• If an object does not contain the RunaroundType statement or the RunaroundGap statement, FrameMaker uses
the values from the previous
RunaroundType and RunaroundGap statements.
• If no previous RunaroundType and RunaroundGap statements exist in the MIF file, FrameMaker uses the default
values
<RunaroundType None> and <RunaroundGap 6.0>.
• For example, if the <RunaroundGap 12.0> statement appears, all objects after that statement have a 12.0 point
gap from text that flows around them. If this is the only
RunaroundGap statement in the MIF file, all objects before
that statement have a 6.0 point gap (the default gap value) from the text that flows around them.
• If the MIF file does not contain any RunaroundType statements or RunaroundGap statements, FrameMaker uses
the default values
<RunaroundType None> and <RunaroundGap 6.0> for all objects in the file.
• For example, 3.x and 4.x MIF files do not contain any RunaroundType statements. When opening these files,
FrameMaker uses the default value
<RunaroundType None>, and text does not flow around any of the existing
graphic objects in these files.
AFrames statement
The AFrames statement contains the contents of all anchored frames in a document. A document can have only one
AFrames statement, which must appear at the top level in the order given in “MIF file layout” on page 52.
The contents of each anchored frame are defined in a Frame statement. Within the text flow, an AFrame statement
indicates where each anchored frame appears by referring to the ID provided in the original frame description (see
“ParaLine statement” on page 125).
Syntax
<AFrames