Tag 012 - Text and Graphics with Optional Buttons

The Text and Graphics with Optional Buttons Message can be used to display static (non-scrolling) user text and graphics, as well as optional buttons. Buttons and static text and graphics are placed in three screen areas, whose heights can be configured (0 = do not display). These areas are, from top to bottom:

  • Button area – IDENTICAL TO 011 – Up to four virtual buttons can be displayed at the top of the screen. As for Tag 010, a virtual button will only be displayed if data is entered in the request descriptor field for the button (ButtonNDesc). The vertical extent of this area is defined (as a percentage of screen height) by a request field; 20(%) is recommended. Buttons are centered in the button area. Button descriptor font size is defined by a request field (see samples below). Maximum button descriptor length is device-specific.
  • Static text area – IDENTICAL TO 011 – The vertical extent of this area is defined (as a percentage of screen height) by a request field. Other request fields define the font size and justification of static text. The maximum number of characters per line depends on the font size and device. The maximum number of lines of static text depends on the height of the area, the font size, and the device.
  • Graphics area – The vertical extent of this area is whatever is left over from the first two areas. It can contain up to two graphics side by side.

Pressing the Enter key is not required after pressing a virtual button.

The Text and Graphics with Optional Buttons Response returns the button pressed by the customer. Request fields (AllowEnter, AllowCancel) control whether the (hard) Enter and Cancel keys can be used.

Field 5001 Format

Request

note

Field separators must be sent for both button and label fields as shown below, even if some of these fields are null.

Field 5001 SubfieldLengthDescription
TTT3Tag (always = 012)
LLL3Length of the following data
AllowEnter1Allow Enter hard key (0=Not allow, 1=Allow)
AllowCancel1Allow Cancel hard key (0=Not allow, 1=Allow)
Beeper1Sound tone (0=No, 1=Yes)
FS1Field separator (Hex 1C)
ButtonAreaHeight2Height of Button area (as % of screen height)
FS1Field separator (Hex 1C)
ButtonFontSize1Button descriptor font size (0 = extra small to 6 = extra large)
FS1Field separator (Hex 1C)
ButtonADescVar.Descriptor for first button position (from left) on top (A)
FS1Field separator (Hex 1C)
ButtonBDescVar.Descriptor for second button position on top (B)
FS1Field separator (Hex 1C)
ButtonCDescVar.Descriptor for third button position on top (C)
FS1Field separator (Hex 1C)
ButtonDDescVar.Descriptor for fourth button position on top (D)
FS1Field separator (Hex 1C)
TextAreaHeight2Height of text area (as % of screen height)
FS1Field separator (Hex 1C)
TextFontSize1Text font size (0 = extra small to 6 = extra large)
FS1Field separator (Hex 1C)
TextJust1Text justification (1=Left; 2=Center; 3=Right)
FS1Field separator (Hex 1C)
TextVar.Text defined in semi-colon (;) delimited lines
FS1Field separator (Hex 1C)
Image1Var.First image
FS1Field separator (Hex 1C)
Image2Var.Second image

Response

Field 5001 SubfieldLengthDescription
TTT3Tag (always = 012)
LLL3Length of the following data
ActionButtonVar.If field 11 Completion Code = 000 (success), returns code for action button or key pressed:
  • 777=Enter (green) key
  • 888=Cancel (red) key
  • 1=ButtonA
  • 2=ButtonB
  • 3=ButtonC
  • 4=ButtonD

Sample Message (Two Buttons)

Request

The following request tells Simplify to display the screen shown below:

API Field #, ValueDescription
0001,36Transaction Type
0011,xxx..User Data. See Simplify-Controlled Field Definitions.
5001,[see value below]Non-Financial Data
  • 012=Tag
  • 057=Length of data
  • 1=Allow Enter key
  • 1=Allow Cancel key
  • 1=Beeper active
  • 20=Height (%) of Button area
  • 3=Button descriptor font size
  • Button 1 (etc.)=Descriptor for virtual button position A (etc.)
  • 25=Height (%) of text area
  • 2=Text font size
  • 2=Text justification
  • Text 1=Text of line 1
  • LOGO.PNG=First (left) image
  • TAP.PNG=Second (right) image

5001,012057111FS20FS3FSButton1FSFSFSButton4FS25FS2FS2FSText 1FSLOGO.PNGFSTAP.PNG

sample screen with two buttons

Response

API Field #, ValueDescription
0001,36Transaction Type
0011,xxx..User Data. See Simplify-Controlled Field Definitions.
5001,0120003888Non-Financial Data
  • 012=Tag
  • 003=Length of data
  • 888=Cancel key pressed
5002,80378002Device serial number (if present)