Xerox DocuPrint 96MX Forms Creation Manual page 99

Laser printing system
Hide thumbs Also See for DocuPrint 96MX:
Table of Contents

Advertisement

Keywords
Form id
GRID command
Coding lines
Coding boxes
Use of shading
Coding text
Coding sections
Source copy
XEROX DOCUPRINT 96/DOCUPRINT 96MX LPS FORMS CREATION GUIDE
Table 5-1 shows tips, tricks, and pitfalls.
Table 5-1.
Explanation
Develop a logical, systematic approach to naming conventions.
Take care not to choose a previously used form id.
Choose a format that is compatible with the data.
Use a COMMENT command.
Code all horizontal lines, then all vertical lines. Precede each set with a comment
statement.
Code longer lines first. Then follow with the shorter segments that may overlay the basic
long lines.
Code lighter lines first. Then code shorter segments that are heavier in density.
Code a SOLID 0 line first whenever you have a set of collinear segments, whether they
are touching or not.
Use a COMMENT command.
Use a BOX command only when the lines generated by that command are not
duplicated by another command.
Do not use a REPEAT command when drawing lines that create boxes if you need to
find the coordinates of those boxes at a later time.
Use back from borders by three to five dots (or about 0.1 units for most coordinates).
This conserves memory and results in a cleaner appearance.
Try to avoid shading on portrait forms.
Use a COMMENT command.
Remember that different fonts of a given point size are not necessarily the same physical
size.
Be aware that vertical error messages generated when the system calculates that too
much text has been specified for placement in a box are at best an approximation.
Use the TEXT SPACED AT command to force exact placement of text.
Use a COMMENT command.
Use coordinates based at 0,0 when defining a section. Then place the section at the
desired locations.
If filename (.FSL) and the form name (name that follows the FORM keyword) do not
agree, an FSL file is created that has the same name as the form name. Therefore, you
copy X.FSL to Y.FSL and compiles Y.FSL without changing the form name in Y.FSL, the
original X.FSL is deleted and a new X.FSL is created from the Y.FSL source.
Furthermore, the form file (.FRM) that is created is X.FRM and not Y.FRM. If you wish
to create a distinct source using another FSL as a base, it is necessary that you change
the form name to the same name as the source name or to some other name that does
not already exist. Two files with the same name and type cannot reside on the system.
FORMS LAYOUT CONSIDERATIONS
Tips, tricks, and pitfalls
5-17

Advertisement

Table of Contents
loading

This manual is also suitable for:

Docuprint 96

Table of Contents