TROUBLESHOOTING
| Table | Hints and tips (continued) |
|
|
|
|
|
Keywords | Hints and tips |
|
|
|
|
| |
Coding text | · 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 an approximation. |
| |
| · Use the TEXT SPACED AT command to force exact text placement. |
| |
| · Avoid placing too many small characters in one area of the page. |
| |
| · Avoid overlapping characters to achieve bolding or other effects. Use the correct |
| |
| font whenever possible. |
|
|
| · Avoid too many font switches on the same text line. This creates overhead in the |
| |
| printing process. |
|
|
Coding sections · Use a COMMENT command.
·Use coordinates based at 0,0 when defining a section. Then place the section at the locations you want.
Source copy | If the source filename (.FSL) and the form name (the name that follows the FORM |
| keyword) do not agree, an .FSL file is created that has the same name as the form name. |
| Therefore, when you copy X.FSL to Y.FSL and compile 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, you need to 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. |
Image complexity factors
Form design is limited by physical restrictions on the amount of image data (characters and lines) that can be printed on a scan line and on a page.
Line tables
Forms Description Language (FDL) line tables are internal FDL data structures that provide a record in memory of the lines to be drawn on a page. These tables allow the system to find the corners and edges of boxes when they are referenced later.
Since excessive amounts of memory would be required to store every line, the FDL compiler retains only the memory of the longest lines that pass through any given coordinate in a particular direction. FDL replaces dotted or broken lines with an invisible line of the same length.
Line table limits The FDL line tables can store 1,999 vertical and 1,999 horizontal lines in memory. When you exceed either of these line table limits, the following message is displayed:
TOO MANY HORIZONTAL OR TOO MANY VERTICAL LINES
This message warns you that the new
XEROX 4050/4090/4450/4650 LPS FORMS CREATION GUIDE |
