Before You Begin
Before adding an element, ensure you have:
Notes About Adding Images to Tickets
If you want to add to images to tickets, note the following:
- If working with an FGL device on a BOCA printer, the image must be a 1-bit PCX file.
 |
Caution
PCX image files cannot be printed by FGL2 devices. |
- If working with a Windows device on a BOCA printer, the image must be a 24-bit colour Windows bitmap file (*.bmp). Ensure the image is dense enough to print in the correct size. For example, if you test with a 203 DPI printer and then use that same image on a 305 DPI printer, the image will print about two-thirds the size you saw during your testing.
- You must define the X-Size and Y-Size when adding images to PDF devices, which must be the same as the actual image size. If the size does not match the actual image size, the application may distort your image. For other devices, do not include the X-Size and Y-Size.
Adding an Element
The Tickets|Elements page displays a preview of the ticket based on the device settings. You can use this preview as a guide when adding elements to the ticket.
To add elements to a ticket template, complete the following:
- Open the General Configuration application from the AudienceView Desktop.
- Select the Tickets tab.
The Tickets|Search page.
- Search for and select the template that you want to add an element to. For more information, refer to the General Configuration Tickets-Search Page and Performing Searches.
The Tickets|Basic page appears. The devices are displayed in the devices section. The current device is highlighted for editing.
- Select the device to which you want to add elements from the Devices list. The current device is highlighted for editing.
- Select the Elements tab.
The Tickets|Elements page appears.
- Click
next to the Element title bar.
The Element window displays.
Click 'Apply' at any time during the ticket template design process to save your changes.
- Click 'Add Element'.
For more information on the fields used to create elements, refer to General Configuration Tickets-Elements Page.
Once a template element is visible on the preview image, you can drag and drop it into a new position; AudienceView automatically updates its X and Y coordinates.
- Complete the element information.
For more information, refer to General Configuration Tickets-Basic Page.
- Click 'OK'.
As you edit the element, the X and Y details along with any display text appears in the 'existing elements' dropdown list.
As you add more elements, you can view the details of an element by clicking the element or selecting it in the dropdown list.
- To add another element to the ticket template, repeat the process from Step 7.
- Click 'Apply'.
A window confirms the application updated the template.
- Click 'OK'.
 |
Hint
You can click 'Test Print' at any time during the ticket template design process to print a sample of your template to your currently select printer. |
Supported Barcode Encoding Standards
The following barcode encoding standards are supported:
- One Dimensional Barcodes (Line Barcodes): Code 39, Code 128
- Two Dimensional Barcodes:
- datamatrix *
- QR in FGL/Boca format
FGL Version 2 Font Sizes
When creating a template for an FGL2 (rebranded Lemur), we recommend that you use the following font sizes (or multiples of them).
| Font |
Font Size |
| Font1 |
7 |
| Font2 |
16 |
| OCRB |
31 |
| OCRA |
8 |
| Font5 |
31 |
| large OCRB |
52 |
| large OCRA |
29 |
| tight courier |
28 |
| small OCRB |
20 |
| Prestige |
41 |
| Script |
49 |
| Orator |
91 |
| Courier |
28 |
Ticket Template Conditional Operators
| Operator |
Definition |
| begins with |
begins with a character or characters |
| contains |
contains a character or characters |
| does not equal |
does not equal a value |
| ends with |
ends with a character or characters |
| equals |
equals a value |
| greater than |
greater than a value |
| greater than or equal to |
greater than or equal to a value |
| is empty |
has no value |
| less than |
less than a value |
| less than or equal to |
less than or equal to a value |
Date Codes
| Desired |
Format Code |
Definition |
| Day |
%d
%#d |
Day of month as decimal number (01 - 31).
%#d – Same as above with leading zeros removed (if any) |
| |
%a |
Abbreviated weekday name
It is not recommended to use this format if your application supports multiple languages. |
| |
%A |
Full weekday name
It is not recommended to use this format if your application supports multiple languages. |
| Month |
%m
%#m |
Month as decimal number (01 - 12)
%#m – Same as above with leading zeros removed (if any) |
| |
%b |
Abbreviated month name
It is not recommended to use this format if your application supports multiple languages. |
| |
%B |
Full month name
It is not recommended to use this format if your application supports multiple languages. |
| Year |
%y
%#y |
Year without century, as decimal number (00 - 99)
%#y – Same as above with leading zeros removed (if any) |
| |
%Y
%#Y |
Year with century, as decimal number
%#Y – Same as above with leading zeros removed (if any) |
| Hour |
%H
%#H |
Hour in 24-hour format (00 - 23)
%#H – Same as above with leading zeros removed (if any)
For example, %H:%M:%S will give you 04:00:00 while %#H:%M:%S gives you 4:00:00. |
| |
%I
%#I |
Hour in 12-hour format (01 - 12)
%#I – Same as above with leading zeros removed (if any)
For example, %I:%M:%S %p will give you 04:00:00 AM while %#I:%M:%S %p gives you 4:00:00 AM. |
| Minute |
%M
%#M |
Minute as decimal number (00 - 59)
%#M – Same as above with leading zeros removed (if any) |
| AM/PM |
%p |
Current locale's am/pm indicator for 12-hour clock
It is not recommended to use this format if your application supports multiple languages. |
| Seconds |
%S
%#S |
Seconds as decimal number (00 - 59)
%#S – Same as above with leading zeros removed (if any) |
*Copyright 2005-2011 Mike Laughton and others. All rights reserved.
Redistribution and use in source and binary forms, with or without modification,
are permitted provided that the following conditions are met:
- Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
- Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
The views and conclusions contained in the software and documentation are those of the authors and should not be interpreted as representing official policies, either expressed or implied, of the libdmtx project.