Intermec PC43d Fingerprint Developer's Guide (PC23d, PC43d/t, PM23c, PM43, PM4 - Page 99

Using the LAYOUT Command

Page 99 highlights

Chapter 6 - Designing Bar Code Labels Using the LAYOUT Command Many applications require the label layout, variable input data, and logotypes to be sent to the printer as files or arrays. This requires less programming in the printer and less data transfer between printer and host, but some kind of overhead program in the host to handle data input and file transfer is typically of great help. The program instruction is a statement called LAYOUT. Before using this statement, a number of 52-byte files or arrays must be created: • A layout file that specifies the type of field to be printed, along with any fieldspecific information such as position, direction, or font type. Use a layout file to set up single-line text fields, line and box fields, bar code fields, bar code extended fields, or bar code interpretation fields. • A logotype file that specifies a graphic field to be printed, along with the name of the image file to be printed in the field. This file is required even if your label does not need or use a graphic field in this way. • A data file (or data array) that specifies the data to be printed in the fields. • An error file (or error array) that sets up error handling for the layout. Each file starts with a 2-byte hexadecimal element number (bytes 0 and 1) which is used to link the layout record with a variable input record or a record in a layout name file as explained later. Byte 2 contains a single character that specifies the type of record: • A = Logotype (specified by its name) • B = Bar Code • C = Character (single-line text) • E = Bar Code Extended File - Corresponds to the last six parameters in the BARSET statement. Must have lower element number than the corresponding bar code record (B). • H = Bar Code Font • J = Baradjust (corresponds to BARADJUST statement) • L = Logotype (specified by its number) • S = Separation line • X = Box The remaining bytes are used differently depending on record type, and may specify direction, position, or some other parameter. Each such instruction corresponds to a Fingerprint instruction (for example, direction corresponds to DIR, alignment to ALIGN, and x- and y-positions to PRPOS). Note that there are only 10 bytes available for the font and bar font names. Since most names of standard fonts are longer, you may need to use font aliases. Fingerprint Developer's Guide 87

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163

Chapter 6 — Designing Bar Code Labels
Fingerprint Developer’s Guide
87
Using the LAYOUT Command
Many applications require the label layout, variable input data, and logotypes to be
sent to the printer as files or arrays. This requires less programming in the printer
and less data transfer between printer and host, but some kind of overhead program
in the host to handle data input and file transfer is typically of great help.
The program instruction is a statement called LAYOUT. Before using this
statement, a number of 52-byte files or arrays must be created:
A layout file that specifies the type of field to be printed, along with any field-
specific information such as position, direction, or font type. Use a layout file to
set up single-line text fields, line and box fields, bar code fields, bar code
extended fields, or bar code interpretation fields.
A logotype file that specifies a graphic field to be printed, along with the name of
the image file to be printed in the field. This file is required even if your label
does not need or use a graphic field in this way.
A data file (or data array) that specifies the data to be printed in the fields.
An error file (or error array) that sets up error handling for the layout.
Each file starts with a 2-byte hexadecimal element number (bytes 0 and 1) which is
used to link the layout record with a variable input record or a record in a layout
name file as explained later.
Byte 2 contains a single character that specifies the type of record:
A = Logotype (specified by its name)
B = Bar Code
C = Character (single-line text)
E = Bar Code Extended File - Corresponds to the last six parameters in the
BARSET statement. Must have lower element number than the corresponding
bar code record (B).
H = Bar Code Font
J = Baradjust (corresponds to BARADJUST statement)
L = Logotype (specified by its number)
S = Separation line
X = Box
The remaining bytes are used differently depending on record type, and may specify
direction, position, or some other parameter. Each such instruction corresponds to
a Fingerprint instruction (for example, direction corresponds to DIR, alignment to
ALIGN, and x- and y-positions to PRPOS). Note that there are only 10 bytes
available for the font and bar font names. Since most names of standard fonts are
longer, you may need to use font aliases.