E000ies0-09sum D

Alenia Marconi Systems
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
SOFTWARE USER MANUAL

INTERFACE EDITOR SYSTEM F.D.
Tabular Editor
ISSUED BY:
Alenia Marconi Systems S.p.A.
Via Tiburtina Km 12.400 - Roma
ITALY
The copyright in this document is the property of Alenia

Marconi Systems S.p.A. The document is supplied on the
express understanding that it is to be treated as confidential
and that it may not be copied, used or disclosed to others in
whole or in part for any purpose except as authorised in
writing by Alenia Marconi Systems S.p.A.
UNCLASSIFIED
D
28/02/2003
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
DOCUMENT SECURITY CLASSIFICATION:

This document is intended for the use of the recipient only, and for communication to such persons as may be
required to be acquainted with its contents in the course of their duties.
The recipient, and any other person to whom the recipient has communicated the contents of this document,
shall treat this document in accordance with the requirements of Alenia document Security Instructions ,
15 February 1992.
Any person others the authorised holder upon obtaining possession of this document, by finding or otherwise,
should forward it by registered post, together with his name and address, in a sealed envelope to:
Ufficio Sicurezza
Via Tiburtina 12.400
00131 Roma
ITALY
Any questions arising from this document should be addressed to:
Luciano CAMINITI
Air Traffic Management & Airports Systems
ATM Software
Via Tiburtina, Km 12.400 - 00131 Roma
ITALY
Telephone
+39-06 4150-3327
Fax
+39-06 4131133 / 4131436 / 4131091
205678826.doc
UNCLASSIFIED
Page ii
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
This document contains a total of 259 pages1

consisting of 9 pages of front matter and 250
pages of text and figures
Issue Authority
Prepared by :
(Software Team Leader)
......................................................
(Luciano CAMINITI)
Date:
Approved by:
(Software System Manager)
......................................................
(Franco BINI)
Date:
Checked by:
(SQAR )
......................................................
(Paolo VIGNALE)
Date:
The Total of Pages includes the Distribution List page. This page is located at the end of document and may be missing in external
distribution document.
205678826.doc
UNCLASSIFIED
Page iii
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
AMENDMENT RECORD SHEET

To record the incorporation of an amendment list in this publication, sign against the appropriate AL No and
insert the date of incorporation.
AL No
Amended by
Date
AL No
25
26
27
28
29
30
31
32
33
10
34
11
35
12
36
13
37
14
38
15
39
16
40
17
41
18
42
19
43
20
44
21
45
22
46
23
47
24
48
205678826.doc
UNCLASSIFIED
Amended by
Date
Page iv
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
REVISIONS RECORD SHEET

This sheet is a record of revisions to this document.
Issue/AL
Date
Revised Pages
Document Change Note

(DCN)
28/10/1999
First Issue
05/01/2001
Added paragraphs for New Menus
First Revision
18/06/2002
Paper Strip management added
Second Revision
28/02/2003
List Upgrade Sytnax changes
Third Revision
205678826.doc
UNCLASSIFIED
Page v
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
1 SCOPE................................................................................................................................1
1.1 IDENTIFICATION................................................................................................................................3
1.2 SYSTEM OVERVIEW..........................................................................................................................3
1.3 DOCUMENT OVERVIEW...................................................................................................................4
2 REFERENCED DOCUMENT.........................................................................................5
3 EDITING TABULAR COMPONENTS..........................................................................6
3.1 TABULAR GRAPHIC OBJECTS DESCRIPTION...........................................................................6
3.2 LOADING AN EXISTENT TABULAR COMPONENT ..................................................................7
3.2.1 Identifing Name And Location Of Objects................................................................................10
3.3 TABLE AND TABLE LIST RESOURCES......................................................................................12
3.3.1 Table Node Events Resource.......................................................................................................22
3.3.2 Table Node Groups Resource.....................................................................................................23
3.3.3 Table Node Actions Resource.....................................................................................................24
3.3.4 Table Global Assign Resource Editing.......................................................................................26
3.4 TABLE TITLE SECTION...................................................................................................................27
3.4.1 Header Grid Field And Generic Field Resources....................................................................29
3.4.1.1 Selecting A Graphical Attribute To Be Assigned To The "attribute_name" Field
Resource ..........................................................................................................................................33
3.4.1.2 Selecting A Graphical Symbol To Be Assigned To The "default_symbol" SymbolField
Resource ..........................................................................................................................................35
3.4.1.3 Using The Graphical Symbol Properties Editor...............................................................40
3.4.1.4 Using The Graphical Attribute Properties Editor...........................................................41
3.5 TABLE HEADER SECTION..............................................................................................................42
3.6 TABLE LIST SECTION......................................................................................................................44
3.6.1 List Grid Field And Generic Field Resources..........................................................................46
3.6.1.1 Field "events" Resource Example ....................................................................................48
3.6.1.1.1 Calling Functions On Event............................................................................................49
3.6.1.1.2 Calling Dialogs On Event.................................................................................................51
3.6.1.2 Field "actions" Resource Example ...................................................................................52
3.7 TABLE TEMPLATES.........................................................................................................................54
3.7.1 EntryTextField Properties Editor Within A Template............................................................61
3.7.1.1 Changing The Fields position Using A Template.........................................................62
3.7.1.2 The Way To Request Continous Update For Fields Using A Template.........................62
3.7.2 Template Resources.....................................................................................................................63
3.7.2.1 Entry Template Sort Resource...........................................................................................66
3.7.3 Merging "Actions" Resource, "Groups" Resource, "Sort_Template" Resources To Define
Table List Entries Grouping And Ordering. ....................................................................................68
3.7.3.1 Defining Table List Entries Grouping, Ordering And Layout: "Entry Strip Bay" : A
Case Study........................................................................................................................................69
3.7.3.1.1 Within The Example: Used Constants And References...............................................70
3.7.3.1.2 Within The Example: Viewing Different Strip Layouts Depending On The Flight
Type Attribute.................................................................................................................................72
3.7.3.1.3 Within The Example: Flight Strips Table List Entries Ordering Depending On The
Flight Type Attribute......................................................................................................................73
3.7.3.1.4 A Parenthesis: Something More About The Groups Syntax........................................77
3.7.3.1.5 Within The Example: Flight Strips Table List Entries Ordering Depending On The
Flight Type And Group Identifier Attribute................................................................................78
3.7.3.1.6 Within The Example: Building A Header For Table List Entries Groups ................80
3.7.3.1.7 Within The Example: Building A Header For Table List Entries Groups ................86
3.7.3.1.8 Within The Example: Flight Status Depending Layouts .............................................89
205678826.doc
UNCLASSIFIED
Page vi
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
3.7.3.1.9 Within The Example: Ordering Table List Entries Within Groups By Resources
Values ...............................................................................................................................................92
3.8 TABLE STRUCTURE ARCHITECTURE........................................................................................96
3.9 CREATING A NEW LIST..................................................................................................................99
3.9.1 COPY OR MOVE OBJECTS FROM AN EXISTENT TABLE...........................................101
3.10 CREATING A NEW TRANSPARENT TABLE...........................................................................101
4 USING MENUS..............................................................................................................103
4.1 MENU BAR MENUS.........................................................................................................................103
4.1.1 MENU "FILE"...........................................................................................................................104
4.1.1.1 MENU ITEM "LOAD"...................................................................................................104
4.1.1.2 MENU ITEM "NEW"......................................................................................................107
4.1.1.3 MENU ITEM "SAVE"....................................................................................................109
4.1.1.3.1 AUTOMATIC BACKUP...............................................................................................109
4.1.1.4 MENU ITEM "SAVE AS"..............................................................................................110
4.1.1.4.1 AUTOMATIC BACKUP...............................................................................................111
4.1.1.5 MENU ITEM "EXIT".....................................................................................................111
4.1.2 MENU "EDIT"..........................................................................................................................112
4.1.2.1 MENU "EDIT", ITEM "PRIMITIVE"..........................................................................112
4.1.2.1.1 SUB_MENU "EDIT" - "PRIMITIVE" - "LOCAL PRIMITIVE"..........................112
4.1.2.1.2 SUB_MENU "EDIT" - "PRIMITIVE" - "GLOBAL PRIMITIVE" ......................119
4.1.2.1.3 SUB_MENU "EDIT" - "PRIMITIVE" - "PARAMETRIC PRIMITIVE".............120
4.1.2.1.4 SUB_MENU "EDIT" - "PRIMITIVE" - "PARAMETRIC MULTI_PRIMITIVE"
.........................................................................................................................................................120
4.1.2.1.5 SUB_MENU "EDIT" - "PRIMITIVE" - "ALL PRIMITIVES"..............................121
4.1.2.2 MENU "EDIT", ITEM " ATTRIBUTE " .....................................................................122
4.1.2.2.1 SUB_MENU "EDIT" - "ATTRIBUTE" - "LOCAL ATTRIBUTES".....................122
4.1.2.2.2 SUB_MENU "EDIT" - "ATTRIBUTE" - "GLOBAL ATTRIBUTE"....................123
4.1.2.2.3 SUB_MENU "EDIT" - "ATTRIBUTE" - "PARAMETRIC ATTRIBUTE"..........124
4.1.2.2.4 SUB_MENU "EDIT" - "ATTRIBUTE" - "ALL ATTRIBUTES"...........................125
4.1.2.3 MENU "EDIT", ITEM "TEMPLATE"........................................................................125
4.1.2.4 MENU "EDIT", ITEM "INCLUDE_FILES"...............................................................126
4.1.2.5 MENU "EDIT", ITEM "GENERAL_VARIABLES".................................................127
4.1.3 MENU OPTIONS.......................................................................................................................129
4.1.3.1 MENU "OPTIONS" - ITEM "VIEW NAME FIELDS"..............................................129
4.1.4 MENU "CREATE"...................................................................................................................131
4.1.4.1 MENU "CREATE", ITEM "NEW PRIMITIVE"........................................................131
4.1.4.1.1 SUB MENU "CREATE" - "NEW PRIMITIVE" - "RECTANGLE"......................131
4.1.4.1.2 SUB MENU "CREATE" - "NEW PRIMITIVE" - "POLYLINE"..........................132
4.1.4.1.3 SUB MENU "CREATE" - "NEW PRIMITIVE" - "LIST OF PRIMITIVE"........132
4.1.4.2 MENU "CREATE", ITEM "NEW ATTRIBUTE".....................................................133
4.1.4.2.1 SUB MENU "NEW ATTRIBUTE", ITEM "TEXT ATTRIBUTE".......................133
4.1.4.2.2 SUB MENU "NEW ATTRIBUTE", ITEM "SYMBOL ATTRIBUTE"..................134
4.1.4.3 MENU "CREATE", ITEM "NEW TEMPLATE"........................................................135
4.1.4.3.1 SUB MENU "CREATE" - "NEW TEMPLATE" - "TABLE TEMPLATE".........135
4.1.4.3.2 SUB MENU "CREATE" - "NEW TEMPLATE" - "ENTRY TEMPLATE".........137
4.1.4.3.3 SUB MENU "CREATE" - "NEW TEMPLATE" - "ENTRY STATE"..................137
4.1.5 MENU "SEL_TABLE".............................................................................................................138
4.1.5.1 MENU "SEL_TABLE", ITEM "SELECT".................................................................138
4.1.6 MENU "BROWSER"................................................................................................................139
4.1.6.1 MENU "BROWSER", ITEM "EDITOR".....................................................................139
4.1.6.1.1 Using The Text Editor Facility Starting From A Properties Editor..........................142
4.1.6.2 MENU "BROWSER", ITEM "LOG WINDOW".........................................................142
4.1.6.3 MENU "BROWSER", ITEM "LISTS"..........................................................................144
4.1.6.4 MENU "BROWSER", ITEM "LISTS CONFIGURATION"......................................145
4.1.7 MENU "REMOVE"..................................................................................................................148
205678826.doc
UNCLASSIFIED
Page vii
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
4.1.7.1 MENU "REMOVE", ITEM "TEMPLATE".................................................................148

4.1.8 MENU "PAPER STRIP"..........................................................................................................149
4.2 POP-UP MENUS................................................................................................................................150
4.2.1 POP-UP MENU, ITEM "PROPERTIES EDITOR".............................................................150
4.2.2 POP-UP MENU, ITEM "ADD LIST"....................................................................................151
4.2.3 POP-UP MENU, ITEM "ADD GRID"...................................................................................152
4.2.4 POP-UP MENU, ITEM "ADD TEXT"..................................................................................153
4.2.5 POP-UP MENU, ITEM "ADD SYMBOL"............................................................................155
4.2.6 POP-UP MENU, ITEM "ADD ENTRYGRID".....................................................................156
4.2.7 POP-UP MENU, ITEM "DUPLICATE"...............................................................................156
4.2.8 POP-UP MENU, ITEM "REMOVE".....................................................................................157
4.2.9 POP-UP MENU, ITEM "COPY "......................................................................................157
4.2.10 POP-UP MENU, ITEM "MOVE "...................................................................................157
4.2.11 POP-UP MENU, ITEMS "ATTACH BEFORE", "ATTACH AFTER", "ATTACH
UNDER"..............................................................................................................................................158
4.3 USING THE RADIO BUTTONS......................................................................................................160
4.3.1 STRUCTURE RADIO BUTTON.........................................................................................160
4.3.2 TEMPLATES RADIO BUTTON.........................................................................................160
4.3.3 CHECK GEOMETRY TOGGLE BUTTON......................................................................161
5 PAPER STRIP CUSTOMIZATION............................................................................163

5.1 SWITCHING ON "PAPER STRIP" CUSTOMIZATION STATE..............................................163
5.1.1 Entry Fields Resources In Paper Strip Customization State.................................................165
5.1.1.1 Entry Fields Used As Static Text.....................................................................................169
5.1.2 MENU "Paper Strip", ITEM "Edit Paper Strip Grid.........................................................170
5.2 PAPER STRIP TEMPLATES...........................................................................................................172
5.2.1 PaperStripTemplate Resources................................................................................................172
5.2.2 Modifing An Existing PaperStripTemplate.............................................................................173
5.2.3 Paper Strip Template Menus....................................................................................................177
5.2.3.1 MENU "Paper Strip", ITEM "New Paper Strip Template "...................................177
5.2.3.2 MENU "Paper Strip", ITEM "Edit Paper Strip Template "...................................177
5.2.3.3 MENU "Paper Strip", ITEM "Remove Paper Strip Template ".............................178
5.2.3.4 MENU "Paper Strip", ITEM "Clone Paper Strip Template "................................179
5.2.3.5 "Paper Strip", ITEM "Export Electronic To Paper Strip Template "...................180
5.2.3.6 MENU "Paper Strip", ITEM "Edit Flight States Template Matrix"......................181
5.3 PSEUDO GRAPHIC PRIMITIVES.................................................................................................184
5.3.1.1 MENU "Paper Strip", ITEM "Create Paper Strip Pseudo Graphic Layout"...........184
5.3.1.1.1 Linking Pseudo Graphic Primitives to Templates......................................................187
5.3.1.2 MENU "Paper Strip", ITEM "Edit Paper Strip Pseudo Graphic Layout"................189
5.4 EXPORT TO FDM CSCI COMMANDS.........................................................................................190
5.4.1 MENU "Paper Strip", ITEM "Print Paper Strip Template "..........................................191
5.4.2 MENU "Paper Strip", ITEM "Print All Paper Strip Templates".......................................192
5.4.3 MENU "Paper Strip", ITEM "Generate Final Configuration"...........................................192
5.5 SOFTWARE PREPARATION.........................................................................................................194
6 APPENDIX ....................................................................................................................195
6.1 APPENDIX A .....................................................................................................................................195
..................................................................................................................................................................195
6.1.1 Calling Functions On Events Examples...................................................................................195
6.2 APPENDIX B......................................................................................................................................197
6.2.1 Current CLASSES/SUBCLASSES..........................................................................................197
6.3 APPENDIX C......................................................................................................................................199
6.3.1 ATC Glossary.............................................................................................................................199
6.4 APPENDIX D......................................................................................................................................206
6.4.1 Reference Help...........................................................................................................................206
205678826.doc
UNCLASSIFIED
Page viii
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
6.4.1.1 Flight reference help..........................................................................................................207

6.4.1.2 Alarm reference help ........................................................................................................317
6.4.1.3 Supervisor reference help ................................................................................................325
205678826.doc
UNCLASSIFIED
Page ix
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
INTERFACE EDITOR SYSTEM

TABULAR EDITOR
205678826.doc
UNCLASSIFIED
Page x
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
SCOPE
This User Manual describes the Tabular objects interactive editor of the Alenia Interface Editor System. It is
primarily addressed to software engineers and technicians that need to change the Alenia HCI application
layout and behaviour.
Throughout this manual, we will assume that the reader is familiar with basic software components such as
the UNIX operating system, OSF/Motif and the X Window System.
Using the Alenia I.E.S. Tabular Builder (IESTB), the user can create or customise the HCI tabular objects; the
user, with the IESTB, can define tables structure and templates containing all the information to give to
tabular objects the desired layout and behaviour.
Tabular objects are realised using the standard X-Window library.
The IESTB reads, manages the interactive edit phase, and re-generates syntax files. These ASCII files
describe the layout and the behaviour of each desired tabular component. They must be re-parsed to generate
resource files for the application and the base graphic library.
Possible tabular facility configurable aspects are:
- Graphic appearance
- Runtime behaviour
- Data exchange with application program flow
- Events handled by application program procedure
In the CWP system three conceptual objects are represented with tabular graphical objects:
-
Flights
Alarms
Supervisor Information
205678826.doc
UNCLASSIFIED
Page 1
E000IES0-09SUM
UNCLASSIFIED
Issue
Date:
D
28/02/2003
I.E.S. TABULAR
Tabular parser
and
compiler
<tabular
component#1>.pre
<tabular
component#n>.pre
Configuration Files :
lists.dsp
- <tabularcomponent #1>.dsp
-
- <tabular component#n>.dsp
Graphics
Configuration
Files
Symbols
Ascii
Files
CWP
Genset
compiler
- multi_list.bin
<tabularcomponent
#1>.bin
<tabular
component#n>.bin
Fig._ 1-1 Tabular Parsing And Compiling Phases
In the previous figure, the following information can be observed:

The "I.E.S. Tabular" is made up of a graphical interactive tool that includes a dedicated "Tabular
parser".
205678826.doc
UNCLASSIFIED
Page 2
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
This tool loads the configuration files: lists.dsp, <tabularcomponent #1>.dsp, , <tabular
component#n>.dsp. This repository is the tabular facility project file.
The "I.E.S. Tabular" tool allows the user to add-change-remove graphical, structural and
behavioural resources, for each tabular representation, referred to a conceptual object that is
provided by A.M.S. Air Traffic Control - Human Computer Interface System.
To compile this project file, the I.E.S. environment allows the start of a compile phase.
The "Configuration File" is pre-compiled, generating three outputs:
- "Graphics Configuration Files" used to initialise the Quickget graphic library
(within the "CWP" program).
"Symbols Ascii Files" that have C-code like header files format.
A ".pre" file.
These last two outputs are merged together, by means of another common compiler ("Genset
compiler"), to allow the generation of a ".bin" file. This last one is used for the Human Computer
Interface section, of the CWP program, initialisation.
1.1
IDENTIFICATION
This document contains the Software User Manual (SUM) for the Computer Software
Configuration Item (CSCI) identified as IES (Interface Editor System).
The following ones are the CSCI identification data:
System Identification Number:
System Title:
System Abbreviation:
CSCI Identification Number:
CSCI Title:
Abbreviation:
1.2
Not Applicable
AMS Air Traffic Control Automatic System
SATCAS
E000IES0
Interface Editor System
IES
SYSTEM OVERVIEW
This document represents the Software User Manual of the Interface Editor System. The IES CSCI
is unique for all systems, that is not specifically developed and/or customised for a specific system.
205678826.doc
UNCLASSIFIED
Page 3
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
1.3
D
28/02/2003
DOCUMENT OVERVIEW
This document describes how is possible to configure tabular objects using the Interface Editor
System Tabular Builder tool. At the end of the document there are an Appendix for examples of
Calling Functions On Events, one for the acronyms used (ATC Glossary), and another one for
the References usage.
This document is organised in the following sections:
Section 1: Scope
It defines the scope of the document, including both a high level overview of the CSCI and
a description of the document structure.
Section 2: Referenced Documents
It provides a list of the documents referenced in this document.
Section 3: Editing Tabular Components
It explains how to edit all types of Tabular objects.
Section 4: Using Menus
It describes all menus of the tabular editor and their meanings.
Section 5: Paper Strip Customization
It describes all the functionality of the Paper Strip management.
Section 6: Appendix
It provides readers with any other suitable information for a complete document
comprehension.
205678826.doc
UNCLASSIFIED
Page 4
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
REFERENCED DOCUMENT
Standards:
This document organization does not observe a specific standard.
Procedures:
[PR-1] PPA-D-01 rev. A AMS - Processo Software 2 giugno 1999.

[PR-2] MAM-Q-01 AMS Manuale per la Qualit.
[PR-3] PPA-D-05 rev. A AMS Gestione della Configurazione del Prodotto Software.
Specifications:
[1] . Software User Manual For The Controller Working Position - Open System Feb. 1999.
[2] . X Window System Digital Press Third Edition.
[3] . Xlib Programming Manual The defenitive Guides to the X Window System
OReilly & Associates, Inc. Third Edition.
[4] . Xlib Reference Manual The defenitive Guides to the X Window System OReilly &
Associates, Inc. Third Edition.
[5] . IER 411 Manuale di Programmazione Stampa e Controllo dei Caratteri Carlo Gavazzi
Systems SpA Copyright 1992.
205678826.doc
UNCLASSIFIED
Page 5
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
3.1
D
28/02/2003
EDITING TABULAR COMPONENTS
TABULAR GRAPHIC OBJECTS DESCRIPTION
The IESTB tool allows the customization of the flight, alarms and supervisor conceptual objects
graphical templates and runtime instances.
Tabular objects are composed by the following components:
- Table title: it contains the elements (grids, text fields, symbol fields) concerning the title of the
table.
- Table header: it contains the elements (grids, text fields, symbol fields) concerning the header or
subtitle of the table. Generally the TextFields of this section are used to create, at the top of the
list, a single text header for each EntryTextField.
- Table list: it contains the elements (grids, text fields, symbol fields) concerning the dynamically
changed items of the list. Generally the TextFields of this section are used to refer to some field
of the handler database-tables for a single EntryTextField.
An example of a tabular graphical object is shown in the following image.
Table Title
Table Header
Table list
Fig.__ 3.1-1 FLDI Tabular Component Graphical Appearance Example
205678826.doc
UNCLASSIFIED
Page 6
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
3.2
D
28/02/2003
LOADING AN EXISTENT TABULAR COMPONENT
When the IESTB tool is started, some existing tabular interface has to be loaded: select the
application "File" menu, and then the "Load" submenu. A cascade button, listing the already
configured tabular components, is displayed. Let's select, for insatance, the "ARR" table.
Fig.__ 3.2-2 Loading A Tabular Component From I.E.S. Tabular Main Menu
The following figure shows the I.E.S. Tabular main window, when the ARR table is loaded:
205678826.doc
UNCLASSIFIED
Page 7
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig.__ 3.2-3 Tabular Component ("ARR") Structural Tree
The root node of the structural tree is a "Table" node type ("ARR" stands for "Arrival List Table").
A child of a "Table" node type may be a "List" node or a "Grid" node.
A "List" node is a manager node that allows the allocation of a list of entries. The list resources may
be customized using the "Table" node properties editor (list section).
A "Grid" node (and "EntryGrid" node "List" child) is a manager that provides the positioning of
elementary tree nodes as "TextField" and "SymbolField" (and, under "EntryGrid", "EntryTextField"
205678826.doc
UNCLASSIFIED
Page 8
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
and "EntrySymbolField"). These last objects are used to implement the graphical representation,
since they can contain graphical primitives (rectangles, polylines, segments, list of primitives),
and text fields, belonging directly to the table or belonging to a specific entry of the table list.
When a pre-defined tabular component is loaded, a preview window showing how the table is
graphically represented will be opened near to the structural tree representation:
Fig.__ 3.2-4 Tabular Component ("ARR") Preview
Clicking on the "Table" structural tree node, the Preview window will show also the table frame
structure, as in the following figure:
Fig.__ 3.2-5 Tabular Component ("ARR") Preview With Layout Frame
In the next paragraphs are described the different objects represented.
205678826.doc
UNCLASSIFIED
Page 9
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
3.2.1
D
28/02/2003
Identifing Name And Location Of Objects
The IESTB tool helps to identify the represented objects: once a given table is loaded, clicking on a
node of the tree structural view, the clicked node is highlighted and on the BlackBoard window is
shown a graphical representation of the size, structure and position of the selected node (for the
graphical representation of each kind of node please refer to the specific paragraph).
On the contrary, clicking an item (for instance, TextField or SymbolField) on the BlackBoard
window, the item and its corresponding node in the tree structure are both highlighted. While, right
clicking an item on the BlackBoard or the corresponding node in the tree structure a pop up window
will be displayed from which to choose one of the available options. (refer to par.4.2)
Fig.___ 3.2.1-1 Picking A TextField On The BlackBoard
205678826.doc
UNCLASSIFIED
Page 10
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig.___ 3.2.1-2 Picking A PrimitiveP_CSL_ENTRY_BOTTOM_SYMBOL, Referred By A

SymbolField, On The BlackBoard Of The CSL Table
205678826.doc
UNCLASSIFIED
Page 11
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
3.3
D
28/02/2003
TABLE AND TABLE LIST RESOURCES
Right clicking on the "Table" tree root node a pop-up menu is displayed: select the submenu
"Properties Editor":
Fig.__ 3.3-6 Opening The Properties Editor For Table Node
The enabled submenu vary from node to node, for instance only the "Properties Editor", "Add Grid"
and "Add List" are enabled for the "table" tree root node in the "ARR" table.
In this case, selecting "Add List" a Warning dialog will remind that the table already manages a list.
Moreover, it is not possible to directly add an elementary node ("Text"/"EntryText" or
"Symbol"/"EntrySymbol"), without inserting an intermediate "Grid" or "EntryGrid" manager node.
Opening the "Table" node Properties Editor, a window will be displayed allowing to see and edit
the values of the different resources connected to the selected object, among those that are listed
hereafter, like in the following figure:
205678826.doc
UNCLASSIFIED
Page 12
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig.__ 3.3-7 Table Node Properties Editor (1st half)
The following figure shows the accessible resources in the second half of the Properties Editor,
which is visible when the panel is scrolled down.
205678826.doc
UNCLASSIFIED
Page 13
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig.__ 3.3-8 Table Node Properties Editor (2nd half)
Here are listed and described all the resources accessible from the Properties Editor.
Syntax
name:
<string>
conceptual object:
table name: cannot be edited, but may be

defined when the table is to be created.
{ alarm | sup | flight }
enumerative resource that defines the
handler whose conceptual object is
205678826.doc
UNCLASSIFIED
Page 14
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
realised as presentation object.

{ numeric identifier | numeric positive integer expression }
defines the default char width used
within the default "Table" "Grid".
char_height:
defines the default char height used
within the default "Table" "Grid".
position x:
{ numeric identifier | numeric non-negative integer expression }
defines the default table horizontal position
with respect to the top left screen origin.
position y:
defines the default table vertical position with
respect to the top left screen origin.
position width:
shows the table width expression and value
(cannot be edited)
position height:
shows the table height expression and value
(cannot be edited)
max_clonable:
{numeric identifier | numeric positive integer expression }
if the value of this resource is greater than 1, the current
table can be cloned within the same output device
(see the case of transparent tables on the radar windows)
geometry_unchangeable: {boolean option}
it declares, for opaque tables (those with a
Motif container), whether the table container can be
resized.
container background color: {string identifier} color identifier chosen in the available gsl
colors.
container title length: {numeric non-negative integer expression }
it refers to the table motif container title,
at the top of the table itself.
container title height: {numeric non-negative integer expression }
it refers to the same table motif container title
container title:
{string}
it refers to the same table motif container title
container scroller offset: {numeric non-negative integer expression }
container scrollbar position
container scroller width: {numeric non-negative integer expression }
container scrollbar horizontal width
container legend height: {numeric non-negative integer expression }
it refers to the table motif container legend,
at the top of the table itself, below the
container title.
container toplevel shell: {string identifier}
must match the name of one of the system
defined Motif interfaces
container screen:
{ numeric non-negative integer expression }
default screen connection number on which the Motif
shell table container shall be created on start-up,
if the referred screen connection is provided
by hardware and software configuration
char_width:
205678826.doc
UNCLASSIFIED
Page 15
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
container min height:
{numeric non-negative integer expression }

it defines the minimum height for the table
container
container max height: {numeric non-negative integer expression }
it defines the maximum height for the table
container; this resource overrides the default
container height, as evaluated by the table
structure
container recording functions : {numeric non-negative integer expression }
it defines the identifier for the table
container; this resource is used by the recording facility
to evaluate the functions (used on the container)
to be checked in the current recording phase.
container recording identifier : {numeric non-negative integer expression }
it defines the table container identifier; this resource is
used by the recording facility
to evaluate the container id.
container icon name: {string}
short name to be displayed on the container

icon, when minimised (to an icon)
container events: <event syntax>
See the related following paragraphs
title: <string>
string resource that should match with the

string resource of a possible title section
text title field (this string is used only for
title length computation).
title_font: <font_identifier>
used only for title size computation.
title_top_offset:
title_bottom_offset:
title_rows:
{ numeric identifier | numeric non negative integer expression }

number of pixels from the table top beginning to
the first row of the table title section
number of pixels that follow the last title row,
before next table section (might be header if
existent)
number of rows of the table title.
header_top_offset:

number of pixels from the table top beginning (or
table title section end)
header_bottom_offset: { numeric identifier | numeric non negative integer expression }
number of pixels that follow the last header
row, before next table section (might be
the list section, if existent)
header_interline:
number of pixels to skip between two
consecutive header rows.
205678826.doc
UNCLASSIFIED
Page 16
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
header_rows:
D
28/02/2003
actions:

number of rows of the table header section
<actions syntax>
See a forward paragraph
assign:
<assign syntax>
See a forward paragraph (par. 3.3.4)
events:
<events syntax>
visible: {boolean option}
Refers to the default table visibility.
priority: {float value}

It goes from 0.0 (lower priority) to
1.0 (higher priority); this resource is used
mainly when more than one (transparent)
table is used within the same Motif container,
and when tables are layered with other radar
objects (tracks, plots, geographic cursor).
de_iconify:
205678826.doc
{enumerated resource: undefined | auto | manual }

It defines the action modality from icon to window if set on
manual or automatic position.
UNCLASSIFIED
Page 17
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Similarly, right clicking on the unique "List" tree node, a pop-up menu will also be displayed: the
following figure shows the window that is opened selecting again the "Properties Editor" submenu:
Fig.__ 3.3-9 Table List Properties Editor (1-st Part)

Syntax
position x:

defines the default entries horizontal start position
with respect to the top left table origin.
position y:
defines the default entries vertical start position with
respect to the top left table origin.
row_spacing x:
defines the horizontal distance between two eventual
205678826.doc
UNCLASSIFIED
Page 18
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
row_spacing y:
column_spacing x:
column _spacing y:
limit:
D
28/02/2003
columns of the same list.

Fixed value for back-compatibility (allowed value 0.0).
Fixed value for back-compatibility (allowed value 0.0).
defines the vertical distance between two consecutive rows
of the same list.
identifies the number of graphically buffered entries.
Should be greater than the
(default_rows * default_columns) value, at least
entries_top_offset:

offset in pixels from table header
section end
entries_bottom_offset: { numeric identifier | numeric non negative integer expression }
number of pixels that follow the list section
end: it's the number of pixels to add to
calculate table height.
entries_left_offset:
offset in pixels from table left beginning.
entries_right_offset:
number of pixels that follow the list section
right end: it's the number of pixels to add to
calculate table width.
when_first:
{enumerated resource: not_present | present | iconize | undefined }
Defines the behaviour of the current list in case of
the first entry.
when_empty:
{enumerated resource: not_present | present | iconize | undefined }
Defines the behaviour of the current list without entries.
sort_direction:
{enumerated resource: NO_SORT | ASCENDING |
DESCENDING | APPEND_TOP | APPEND_BOTTOM |
NEVER_ENDING | undefined }
Defines the sort modality for the entries.
default_rows:
default number of table list rows visible.
default_columns:
default number of table list columns
visible.
max_rows:
maximum number of table list rows visible.
max_columns:
maximum number of table list columns
visible.
entry_top_offset:
top offset in pixels from list entry
application point.
entry_bottom_offset: { numeric identifier | numeric non negative integer expression }
number of pixels that follow the single
entry end: it's the number of pixels
to add to calculate single list
205678826.doc
UNCLASSIFIED
Page 19
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
entry_left_offset:
entry_right_offset:
entry_interline:
entry_rows:
slot_rec:
total_chars_in_row:
box_offset:
D
28/02/2003
entry height.
left offset in pixels from list entry
application point.
number of pixels that follow the single
entry right end: it's the number of pixels
to add to calculate single list entry width.
number of pixels to skip between two
consecutive list entry rows.
number of list entry rows
maximum number of slot for each list entry
number of row chars for each list entry
(allows calculating the entry width)
scroller_width:

number of pixels to be assigned to the list
Motif scrollbar width resource
groups:
<groups syntax>
Scrolling down this properties editor panel, other list or list entry resources could be accessible.
205678826.doc
UNCLASSIFIED
Page 20
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig.__ 3.3-10 Table List Node Properties Editor (2-nd Part)
205678826.doc
UNCLASSIFIED
Page 21
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
3.3.1
D
28/02/2003
Table Node Events Resource
The IESTB tool allows the editing of this section as a free text.
Fig.___ 3.3.1-3 Table Node "events" Resource Example
205678826.doc
UNCLASSIFIED
Page 22
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
3.3.2
D
28/02/2003
Table Node Groups Resource
The IESTB tool allows the editing of this section as a free text.
Fig.___ 3.3.2-4 Table Node "groups" Resource Example
This "groups" syntax means that the items of the whole list belong to a unique group. There are no
sub-groups (i.e. arrival/enroute/departure sub-groups). So the number of items that must be counted
and assigned to the list total items presentation field is to be calculated from that unique group of
items.
For a wider explanation of this syntax please refer to a forward specific paragraph.
205678826.doc
UNCLASSIFIED
Page 23
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
3.3.3
D
28/02/2003
Table Node Actions Resource
The IESTB tool allows to edit this section as a free text.
Fig.___ 3.3.3-5 Table Node "actions" Resource Example
The "actions" syntax example used by the "ARR" Table is briefly explained hereafter.
These actions are related to the global Table and/or Entry action: it is therefore applied to all the
fields of the global Table or Entry. Field specific actions might override these global actions.
205678826.doc
UNCLASSIFIED
Page 24
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
1. - The "HEADER_PRELIMINARY_ACTION" must always be present: it refers to the

assignment of the Table default template. In this case the assigned Table template is the so-called
"MAXIMIZE_TEMPLATE" (it calls the implicit function "set_header_template").
2. - The "ENTRY_PRELIMINARY_ACTION" must be present when the Table has a List section.
This action refers to the assignment of the default template single entry. In this case the assigned
Entry template is the so-called "NORMAL_TEMPLATE" (it calls the implicit function
"set_template"). This action also allows to assign the way in which items in the List are sorted (it
calls the "set_sort" implicit function, with a parameter depending on the value contained in the
conceptual object resource "FLY_STATUS_REF").
For a wider explanation about the Table and Entry templates please refer to a forward specific paragraph.
3. - The "HEADER_BACKGROUND_ACTION" is optional. It allows to assign resources like "all

fields background color", "all fields foreground color", "single field attribute", "single field
visibility", for header fields (using the built-in functions "set_template_background",
"set_template_foreground", "set_field_attribute", "field_on", "field_off")
4. - The "ENTRY_BACKGROUND_ACTION" is optional too. It allows to assign resources like
"all fields background color", "all fields foreground color", "single field attribute", "single field
visibility", depending on the value contained in some conceptual objects resource (using the built-in
functions "set_template_background", "set_template_foreground", "set_field_attribute", "field_on",
"field_off").
205678826.doc
UNCLASSIFIED
Page 25
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
3.3.4
D
28/02/2003
Table Global Assign Resource Editing
This section is made of one or more assign statements. The IESTB tool allows to edit this section as
a free text, use the table node properties editor to edit this section.
Syntax
assign:
identifier
assign_value
Fig.___ 3.3.4-6 Table Node "assign" Resource Editor
205678826.doc
UNCLASSIFIED
Page 26
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
3.4
D
28/02/2003
TABLE TITLE SECTION
Click on the "ARR" Table Grid called "TITLE_GRID". Selecting this Table tree node the grid
frame drawn on the preview window will be shown. The selected grid manager parameters can also
be visualized and edited, as shown in the following figure:
Fig.__ 3.4-11 Table Title Grid And Structure
Syntax
name:
<string>
grid name: this name may be duplicated
more than once within the Table
structural tree.
type:
{GRID | ENTRY_GRID }
enumerated resource: it is a static resource
205678826.doc
UNCLASSIFIED
Page 27
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
offset_x:
offset_y:
char_width:
char_height:
interline:
D
28/02/2003
defined at creation time

number of horizontal pixels from the table
origin (top -left) to the grid origin.
number of vertical pixels from the table
origin (top -left) to the grid origin.
horizontal single char spacing: it is used for
field column positioning, when
expressions as C#<non negative integer>
are used
vertical single char spacing: it is used for
field row positioning, when
expressions as R#<non negative integer>
are used; the row spacing value depends
also on the interline grid resource
vertical spacing to be left between two
adjacent rows: it is used for
field row positioning, when
expressions as R#<non negative integer>
are used; the row spacing value depends
also on the char_height grid resource
In the top left window of the previous figure, the Grid manager called TITLE_GRID has two
primitive children: the "ARR_TITLE" TextField and the "ARR_MOVING" SymbolField. The
positioning of these fields depends on their Grid manager only if positional expressions as "
R#<non negative integer>" and/or "C#<non negative integer>" are used, or if positional expressions
containing dynamic constants inherited by the Grid parent manager, such as offset_x, offset_y,
char_width, char_height, interline are used.
205678826.doc
UNCLASSIFIED
Page 28
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
3.4.1
D
28/02/2003
Header Grid Field And Generic Field Resources
Before explaining the specific Header Grid Field And Generic Field Resources it is necessary to
introduce the different characteristics of the Text and Symbol fields. The former (Text), is used to
visualise a string within a table, thus, its properties define the aspect and behaviour of the text to be
shown (dimension, position, length, etc.). The latter, (Symbol field) is used to show graphical
objects within a table (for instance one is the Hook symbol, used to select a row in a list of
entries); its properties define the characteristics in order to do so; which means that, for instance,
the symbol fields, used to refer a primitive and show it, do not manage resources such as
default_string, length or similar.
Right click on the "LANDING LIST:" Text field on the Preview Window of the "ARR" Table.
Select from the popped up menu the "Properties Editor" menu item.
Fig.___ 3.4.1-7 Opening The Properties Editor For A Title TextField From The Previewer
The "ARR_TITLE" TextField properties editor will be opened, like in the following figure:
205678826.doc
UNCLASSIFIED
Page 29
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig.___ 3.4.1-8 Properties Editor For Title TextField "ARR_TITLE"
Syntax
name:
<string>
field name: this name must be unique

within the whole tabular component
type:
{TextField | SymbolField | EntryTextField | EntrySymbolField }
defined at creation time (see the interactive
menu items)
default_string: <string>
it's the initial string value used for default
visualization of a TextField or an
EntryTextField; it's not a valid resource
for a SymbolField and an
EntrySymbolField
default_symbol: <primitive identifier>
it's a symbolic identifier of a graphical
primitive for default
205678826.doc
UNCLASSIFIED
Page 30
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
visualization of a SymbolField or an
EntrySymbolField;
it's not a valid resource for a TextField and
an EntryTextField
default_status: {enumerated reasource : On | Off}
It defines the field visibility, must be
set Off in the Structure declaration
phase. At the contrary the same object
default_status must be set On
in the Templates declaration phase, if
the field has to be represented
in the template (see par.3.7.1.2).
position_x:
{ C#<non negative integer> |
numeric non negative integer expression }
pixel horizontal positioning value obtained
using the parent grid manager resources or
evaluating a numeric expression using
other pre-assigned parameters
position_y:
{ R#<non negative integer> |
pixel vertical positioning value obtained
using the parent grid manager resources or
evaluating a numeric expression using
other pre-assigned parameters.
The expression is negatively signed to
obtain pixel values X-Server compatible
coordinates
length:
<numeric positive integer>

maximum string length for a TextField or
an EntryTextField; it's not a valid resource
EntrySymbolField
attribute_name: <attribute identifier>

identifier of a pre-defined graphical
attribute: it may be a combination of color,
and/or style for a SymbolField and an
EntrySymbolField, and/or font for a
TextField and an EntryTextField (see the
example of next figure)
reference:
<reference_identifier>
reference to a resource of a conceptual
object managed by a specified
ATC handler within the internal database
events:
<events syntax>
actions:
<actions syntax>
truncation:
<char>
it's the character used to stop
a TextField or an
EntryTextField string when their
205678826.doc
UNCLASSIFIED
Page 31
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
length is greater then the

declared "length" value;
it's not a valid resource
EntrySymbolField
reference_param :
for a dynamic reference usage;
EntrySymbolField
( see the following picture )
start_ref_pos:
<integer>
index of the first character used within
the string to compose the drawn string;
EntrySymbolField
Fig.___ 3.4.1-9 "reference_param" editor for "ARR_SEP_NAME" TextField
205678826.doc
UNCLASSIFIED
Page 32
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
3.4.1.1 Selecting A Graphical Attribute To Be Assigned To The "attribute_name"

Field Resource
The attributes are a combination of color, and/or style for a SymbolField and anEntrySymbolField,
and/or font for a TextField and an EntryTextField. They are classified in three catergories : Local,
Global and Parametric.
The Local attributes can only be used in the current table; their definitions, in fact, are stored within
the <table_name>.dsp file.
The Global attributes can be used in all the defined tables; their definitions are stored in the file
global_table_attribute.dsp.
The Parametric attributes can also be used in all the defined tables. Their usage makes it possible to
obtain from a single attribute definition different attributes names for different tables. To have this
outcome an attribute name must be assigned containing the table_name prefix ( for instance if in
the FLDI table there is an FLDI_DEMO_ATTRIBUTE then in the ESB table there will be the
same attribute called ESB_DEMO_ATTRIBUTE). Their definitions are stored within the file
parametric_table_attribute.dsp.
Clicking on the " >> " button on the right of the "attribute_name" resource a selection Box with
graphical preview will be displayed in which one of the defined graphical attributes could be
selected:
205678826.doc
UNCLASSIFIED
Page 33
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig.____ 3.4.1.1-1 Selecting A Graphical Attribute For The TextField "ARR_TITLE"
In order to Edit and Create Attributes please see at par. 4.1.2.2, 4.1.4.2
205678826.doc
UNCLASSIFIED
Page 34
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
3.4.1.2 Selecting A Graphical Symbol To Be Assigned To The "default_symbol"

SymbolField Resource
The primitives are graphical objects used by SymbolFields and anEntrySymbolFields, They are
classified in four catergories : Local, Global, Parametric and Parametric Multi.
The Local primitives can only be used in the current table; their definitions, in fact, are stored
within the <table_name>.dsp file.
The Global primitives can be used in all the defined tables; their definitions are stored in the file
raster_symbol.dsp.
The Parametric primitives and Parametric Multi primitives (used by multi-table components, like
transparent tables) can also be used in all the defined tables. Their use makes it possible to obtain
from a single primitive definition different attributes names for different tables. To have such an
outcome, a primitive name must be assigned containing a prefix such as P_<table_name> ( for
instance if in the FLDI table there is an FLDI_DEMO_PRIMITIVE then in the ESB table there will
be the same attribute called ESB_DEMO_PRIMITIVE); in case of Parametric_Multi the prefix is
also required to have different expression results for different tables. Their definitions are stored
within the files parametric_table_symbols.dsp, parametric_table_multi_list_symbols.dsp.
The use of a Parametric Multi Primitive (P_<table_name>_ENTRY_BOTTOM_SYMBOL) that
contains some expression recalculated for every table used - in this case SIL and CSL is
shown in the following pictures:
Fig.____ 3.4.1.2-2 Csl Table With The Field Referring P_CSL_ENTRY_BOTTOM_SYMBOL Multi
Primitive Selected
205678826.doc
UNCLASSIFIED
Page 35
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig.____ 3.4.1.2-3 Properties Editor Of The P_CSL_ENTRY_BOTTOM_SYMBOL Multi Primitive
Fig.____ 3.4.1.2-4 Sil Table With P_SIL_ENTRY_BOTTOM_SYMBOL Multi Primitive Selected
205678826.doc
UNCLASSIFIED
Page 36
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig.____ 3.4.1.2-5 Properties Editor Of The P_SIL_ENTRY_BOTTOM_SYMBOL Multi Primitive
205678826.doc
UNCLASSIFIED
Page 37
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig.____ 3.4.1.2-6 Runtime Representation Of CSL And SIL Tables
Clicking on the Table "ARR_MOVING" (SymbolField) tree node of the structural tree
representation, and selecting the menu item "Properties Editor" from the popped-up menu, the
properties editor of the selected field will be displayed:
205678826.doc
UNCLASSIFIED
Page 38
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig.____ 3.4.1.2-7 Properties Editor For Title SymbolField "ARR_MOVING"
The "default_symbol" resource is clearly active and set to "P_ARR_MOVING": in fact the field is
of "SymbolField" type. The "attribute_name" resource is not set: the referenced graphical primitive
"P_ARR_MOVING" may itself contain graphical attributes. The "length" resource is not valid for
this type of field. Since the "position_x" and "position_y" resources are not set, the default position
(0,0) is assumed: this means that the primitive pixel coordinates will not be relative to any
("position_x", "position_y") offset.
Please refer to par. 4.1.2.1, 4.1.4.1 to learn how to Edit and Create Primitives.
205678826.doc
UNCLASSIFIED
Page 39
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
3.4.1.3 Using The Graphical Symbol Properties Editor

Here is the "P_ARR_MOVING" primitive properties editor:
Fig.____ 3.4.1.3-8 Properties Editor For The Rectangle Graphical Primitive ("P_ARR_MOVING")
Related To The SymbolField "ARR_MOVING"
As it is clearly shown in the previous figure, the graphical primitive "P_ARR_MOVING" is a

"Rectangle". Even though no "color" or "Style" resource is defined in the Properties Editor, they
might be grouped within the "Attribute" resource. Clicking on the " >> " button on the right of the
"Attribute" resource, a selection Box with a graphical preview is displayed to help the user to select
the desired graphical attribute (in this case "A_BORDER").
Rectangle geometrical parameters are the "Lower Left X-Y" and "Upper Right X-Y" vertex
(evaluated as float values, then rounded to integer pixel position).
205678826.doc
UNCLASSIFIED
Page 40
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
3.4.1.4 Using The Graphical Attribute Properties Editor

Now have a look at the description of the graphical attribute "A_BORDER". Further explanation of
this kind of editing panel will be given in a forward specific paragraph. The properties editor for the
"A_BORDER" graphical attribute is the following:
Fig.____ 3.4.1.4-9 Properties Editor For The Primitive Graphical Attribute "A_BORDER" And
Viewing The Symbol Style Assigned ("OUTLINE0")
205678826.doc
UNCLASSIFIED
Page 41
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
3.5
D
28/02/2003
TABLE HEADER SECTION
Lets now have a look to the "HEADER_GRID": for instance in the "ARR" Table, selecting this
Table tree node the grid frame will be drawn on the preview window. The selected grid manager
parameters can also be visualized and edited, as shown in the following figure:
Fig.__ 3.5-12 Table Header Grid And Structure
Within a Table, the Header section is normally used as a legend for the list entries that follow it. It
explains the content of each entry field, especially when the entry is composed of a single row. In
205678826.doc
UNCLASSIFIED
Page 42
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
this case the Grid manager is made of eight TextFields with no related actions and events (only
static texts are present).
Syntax
The syntax for this (header) Grid manager is the same explained in Par. 3.4
205678826.doc
UNCLASSIFIED
Page 43
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
3.6
D
28/02/2003
TABLE LIST SECTION
Lets now have a look to the " ENTRY_GRID ": for instance in the "ARR" Table, selecting this
Table tree node the grid frame will be drawn on the preview window. The selected grid manager
parameters can also be visualized and edited, as shown in the following figure:
Fig.__ 3.6-13 Table List Grid And Structure
Within a Table, the List section is normally the most important and useful one. The same concept of
tabular facility is basically focused on the necessity to have fast graphical lists.
Each item of a list is normally a presentation object related to a conceptual object (instance)
managed by handlers and stored within the internal database.
The Grid properties editor has obviously the same parameters of other Grids previously reviewed.
205678826.doc
UNCLASSIFIED
Page 44
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
In our example, the "ENTRY_GRID" manager node has 9 children fields: one EntrySymbolField
and eight EntryTextFields.
A Grid that is child of a "List" node is itself positioned relatively to the following Table List node
resources: "entries_top_offset", "entries_bottom_offset", "entries_left_offset",
"entries_right_offset", "entry_top_offset", "entry_bottom_offset", "entry_left_offset",
"entry_right_offset", "entry_interline"
Syntax
The syntax for this (entry) Grid manager is the same explained in Par. 3.4
205678826.doc
UNCLASSIFIED
Page 45
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
3.6.1
D
28/02/2003
List Grid Field And Generic Field Resources
Lets right-click on one of the "ENTRY_GRID" structural tree child nodes ("ARR_ETL") to open
the pop-up menu, and select from that menu the "Properties Editor" item. The EntryTextField
"ARR_ETL" properties editor will be opened, and will look as follows:
Fig.___ 3.6.1-10 Properties Editor For A List EntryTextField ("ARR_ETL")
The resource "default_symbol" is clearly not significant, while the resource "default_string" is
significant though its initial value is the NULL_STRING ( "" ): the field is in fact of
"EntryTextField" type.
The "attribute_name" resource is set to "ARR_A_TEXT" (a Text Attribute).
The "length" resource is set to 4, which means that any string assigned to this presentation field that
will be longer than that will be truncated after its fourth character.
The "position_x" and "position_y" resources are directly referred to the "ENTRY_GRID" Grid
parameters (the evaluated pixel position can be read on the right of the expression).
205678826.doc
UNCLASSIFIED
Page 46
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
This presentation field is related to the conceptual field referenced by the "FLIGHT_ETL_REF"
identifier.
205678826.doc
UNCLASSIFIED
Page 47
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
3.6.1.1 Field "events" Resource Example

This field is provided with events managed after some interaction with the operator. To open the
events syntax editor, click on the "" events resource button:
Fig.____ 3.6.1.1-10 "events" Resource For The EntryTextField "ARR_ETL"
In this case the <events syntax> can easily be interpretated: when the operator clicks the mouse left
button (ABCK stands for Action Button Clicked, that usually correspond within the Graphics
Service Layer to "Btn1 down"), a built-in function without parameters, called "HOOKING( )", is
consequently activated (all the information will be caught by default, so the current table, the
current item of the list, the current field, and the current compound event).
205678826.doc
UNCLASSIFIED
Page 48
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
3.6.1.1.1 Calling Functions On Event

The event syntax allows to call some application predefined functions. The following list of
functions and examples shows how to deal with the basic ones.
APPLICATION
PREDEFINED
FUNCTIONS-ID
PARAMETERS TYPE AND ALREADY USED

PARAMETERS
ACTION
DESCRIPTION
SCROLLING
Command Identifier
BRW_ID
Event Identifier
SCROLLING_DOWN
Scrolls a list
BRW_ID
-
SCROLLING_UP
-
Event Identifier
CLEARANCE_id
PopupMenu
Widget Name
'ClearanceMenu'
EXECUTIVE_id
'ExecutieMenu'
PASSIVE_id
'PassiveMenu'
BRW_SCROLL
FORCED_HOOK
POPPINGUP
EXECUTING
Event Reference Identifier

GET_S_FILENAME_PREVIEW GET_R_FILENAME_PREVIEW
APPLYING
HOOKING
Identifier
ALL_CONTEXT
Command Identifier
ALV_ID
Choice Name String

'choice_ALV'
TKF_ID
LND_ID
PKB_ID
FCK_ID
PEL_ID
XFL_ID
FEL_ID
-
'choice_TKF'
'choice_LND'
'choice_PKB'
'choice_FCK'
'choice_PEL'
'choice_XFL'
'choice_FEL'
-
GARBAGING
EXEC_DOUBLE_TURN
TOGGLE_GROUP
SHIFTING
MINIMIZING
MAXIMIZING
205678826.doc
UNCLASSIFIED
Scrolls down a browse

list
Scrolls up a browse list
Forces the hooking of a
flight item
Opens the popupMenu

widget identified by the
PopupMenu Widget
Name parameter
Opens a preview motif

interface identified by
the first parameter
Executes the apply
application predefined
function
Hooks a flight item
Resets the whole list, if
allowed by the list itself
(application dependent)
Executes a double turn
operation when a choice
menu, containing
information defined by
the Command Identifier,
is opened.
The second parameter is
the choice name.
Executes a reverse
ordering within each
group of a list, if allowed
by it.
Executes a shift of the
current list item.
Applies the minimize
template to the current
table.
Applies the maximize
template to the current
Page 49
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
Enabling Identifier
-
Order Identifier
-
JOINING
TOGGLE_ORDERING
SCROLLING_DOWN
SCROLLING_UP
MOVING
EXEC_HIDDEN_ORDER
S
NOTHING
D
28/02/2003
table.
Requests table
positioning as defined by
its keyword (for multitable output devices
only)
Executes a reverse
ordering within a single
group of a list, if allowed
by it
Scrolls down the list
items
Scrolls up the list items
Executes table
positioning (for multitable output devices
only)
Executes hidden orders
No operation
For a more exaustive example of events syntax please refer to the Appendix (6.1.1 Calling
Functions On Events Examples)
205678826.doc
UNCLASSIFIED
Page 50
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
3.6.1.1.2 Calling Dialogs On Event

Within an event syntax, "dialogs" can be called to communicate a request. The "dialog" call syntax
is the following.
Syntax On Event
f.dialog <dialog_name> <preview_name> <generic_string>

[ <fdm_order> ] [<grp_order>] [<generic_value]
where :
dialog_name:
<string>
It is the name of a existing dialog.
preview_name:
<string>
It is the name of the MMI interface

involved in the dialog
generic_string:
<string>
fdm_order:
grp_order:
generic_value:
It is a generic string used within the dialog

(at least the string: "" )
fdm.{<identifier> | <integer> }
It is an optional parameter used within the
dialog to identify the order (or
command) used on the dialog requested
(see it in dialog parameters).
grp.{<identifier> | <integer> }
It is an optional parameter used during the
dialog to identify where does the
dialog produce its effect (grp or srp).
gen.{<identifier> | <integer> }
Generic identifier:
The order of the last three parameters is irrelevant. For instance see the following example
text: PDL_CS
(
event: ABCK (function: FORCED_HOOK())
event: ABCK (f.dialog: "DOUBLE_TURN" "preview_RCR" "" fdm.RCR_ID;)
)
205678826.doc
UNCLASSIFIED
Page 51
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
3.6.1.2 Field "actions" Resource Example

Lets open the following "ARR_CS" EntryTextField properties editor to see an example of [Entry]
{Text|Symbol}Field "actions":
Fig.____ 3.6.1.2-11 Properties Editor For A List EntryTextField ("ARR_CS")
The EntryTextField resources are similar to those of the previously seen "ARR_ETL" field.
Nevertheless, clicking on the "" actions resource button, the following editor will be opened:
205678826.doc
UNCLASSIFIED
Page 52
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig.____ 3.6.1.2-12 "actions" Resource For The EntryTextField "ARR_CS"
In this case, the <actions syntax> means that if the value of the related conceptual object reference
"DEV_AL_REF" is equal to the constant value "DEV_AL_TRUE_CASE" (true), the foreground
color of the presentation text field will be set according to the color defined within the graphical
attribute named "FG_DEVIATION_ALERT" (the function that sets a field attribute is called
"set_field_attribute").
205678826.doc
UNCLASSIFIED
Page 53
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
3.7
D
28/02/2003
TABLE TEMPLATES
Select the "ESB" ("Entry Strip Bay") tabular component from the "File" menu "Load" item. Its
structural tree representation will look like that of the following figures.
Fig.__ 3.7-14 Loading the "ESB" (Entry Strip Bay) Table: Structural Tree View (1 st)
205678826.doc
UNCLASSIFIED
Page 54
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig.__ 3.7-15 Loading the "ESB" (Entry Strip Bay) Table: Structural Tree View (2 nd)
205678826.doc
UNCLASSIFIED
Page 55
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig.__ 3.7-16 Loading the "ESB" (Entry Strip Bay) Table: Structural Tree View (3 rd)
This structural tree is quite complex. This happens because the table list entry has many fields; in
fact they are the union of all the fields that appear for all the entry states (or templates).
The preview window will show a graphical representation similar to the following figure. In this
case as well, all the fields are visible, independently by the specific Entry State. In the following
pages will be shown how these fields can be switched on and off, and/or can be repositioned; these
205678826.doc
UNCLASSIFIED
Page 56
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
information are grouped and linked to a specific state of the table or of a table list entry. Assigning
this state to the table or to one of the existing table list items, is equivalent to assign each single
resource like visibility and position to the involved fields, and to define some other behaviour, as
table list items ordering or positioning.
Fig.__ 3.7-17 "ESB" Table Preview
To understand what is the effect of the application of a template to a table, the properties editor of a
table list entry elementary field should be opened, like in the following figure:
205678826.doc
UNCLASSIFIED
Page 57
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig.__ 3.7-18 "ESB_IN_FIX" EntryTextField Structure Declaration Properties Editor
Now let's select a table template. Click on the main panel "Templates" toggle button. A selection
box will pop-up similar to the following:
Fig.__ 3.7-19 Selecting A Template

205678826.doc
UNCLASSIFIED
Page 58
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Loading, for instance, the template called "ESB_ARR_ACT_TEMPLATE" the table structural tree
view will look like the following (scrolling down the tree panniers):
Fig.__ 3.7-20 Applying "ESB_ARR_ACT_TEMPLATE": Structural Tree View
As can be observed, many of the elementary tree nodes background colour are lighter than the
corresponding tree nodes in the structural tree. This means that in the template some changes have
205678826.doc
UNCLASSIFIED
Page 59
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
occured to the nodes properties. Similarly, the node "ESB_IN_FIX" label foreground is higligted
meaning that such a node has been selected for some interaction.
Fig.__ 3.7-21 Applying "ESB_ARR_ACT_TEMPLATE": Table Preview
Hereafter is shown what happens to the "ESB" table, and particularly to one of its list entries, when
the "ESB_ARR_ACT_TEMPLATE" entry template is applied (this template is a sort of layout
prototyping activity). Unlike to the previously discussed "ESB" Table Preview example, in this
figure there are some fields that have disappeared (because their visibility is set to Off), and some
other who are differently positioned (probably because within the basic table and table list entry
structure declaration no position declaration was provided).
Lets analyse an entry field properties editor, when a template is still applied, to better understand
how these changes can be declared.
205678826.doc
UNCLASSIFIED
Page 60
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
3.7.1
D
28/02/2003
EntryTextField Properties Editor Within A Template
So let's open again the "ESB_IN_FIX" EntryTextField properties editor.
Fig.___ 3.7.1-11 EntryTextField Within "ESB_ARR_ACT_TEMPLATE" Template Declaration

Properties Editor
The only resources of the EntryTextField that can be modified (i.e. whose interaction operator is
"sensitive") are clearly the so called "default_status" (that is the field visibility, switched to On)
and the "position_x" and "position_y" resources declared as a row-column grid referenced
expression. This means that the same field may assume different values for these three resources
within each differently declared (entry) template.
205678826.doc
UNCLASSIFIED
Page 61
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
3.7.1.1 Changing The Fields position Using A Template

Beware: the position resource in the Template modality, refers, for the pixel coordinates
computing, to the char width and char height, declared in the Table node, with offset equal to (0,0).
If some fields are declared under grids with different CHAR WIDTH and/or CHAR HEIGHT or
offset declarations, some wrong re-positioning will occur. In order to avoid undesired effects it is
suggested to use the "position" resource only in Structure mode. The use of the "position"
resource in the Template mode requires homogeneous declarations for the grids.
3.7.1.2 The Way To Request Continous Update For Fields Using A Template
In order to refresh a presentation object with values taken from the related conceptual object (in
this, like in any other, case an EntryTextField), the following considerations are very important.
The presentation object resource visibility (default_status) should be set Off in the Structure
declaration phase. On the contrary, its default_status must be set to On in the Templates
declaration phase.
This does not apply to presentation objects that dont need to be updated, like the title or legend
Texts, or static graphical Symbols. All these objects normally have no reference resource.
205678826.doc
UNCLASSIFIED
Page 62
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
3.7.2
D
28/02/2003
Template Resources
The "template" entity has its own resources, that can be accessed by means of the "Edit"
"Templates" main menu. For instance, lets have a look to the "ESB_ARR_ACT_TEMPLATE"
properties editor:
Fig.___ 3.7.2-12 Properties Editor For "ESB_ARR_ACT_TEMPLATE"

Syntax
Template Type: {EntryTemplate |
TableTemplate |
EntryState }
enumerated resource.
The EntryTemplate type groups
information that have to be applied to a
table list entry; these resources are:
fields visibility, fields re-positioning,
entry ordering within other
existing list entries
The EntryState type is used as an
EntryTemplate modifier; normally it
is limited to fields visibility changes
and fields repositioning, it does not
allow changes to the entry order that
is managed by the main EntryTemplate;
it allows entry horizontal shifting.
Number Of Slots:
integer positive value resource

(normal value is 1)
Horiz. Shift:
valid only for EntryState template, it means
205678826.doc
UNCLASSIFIED
Page 63
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
the number of pixels the entry can

be shifted when the EntryState is applied.
sort syntax : see further information later
Entry Template Sort:

Bottom Symbol: <EntrySymbolField identifier>
It is the name of an Entry Symbol Field,

that uses as default_symbol a special
graphical primitive.
The use of this Entry Template
resource consists in allowing the automatic
visualization of this graphical primitive,
only for the last entry of a table-list.
Normally this resource is used for
transparent tables (within a
radar window, for instance), to close
the resizable table itself, at the bottom.
It's a valid resource only for an
EntryTemplate (see the following)
205678826.doc
UNCLASSIFIED
Page 64
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig.___ 3.7.2-13 Selecting A Bottom Symbol For The SIL_NORMAL_TEMPLATE
To switch off the bottom symbol, please select the first empty item of the EntrySymbolField
Selection selection box.
205678826.doc
UNCLASSIFIED
Page 65
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
3.7.2.1 Entry Template Sort Resource

Lets now open the "Entry Template Sort" resource in the the text editor to see how it works:
Fig___ 3.7.2.1-1 Editor For "Entry Template Sort" "ESB_ARR_ACT_TEMPLATE" Resource
The way in which this behavioural resource can be written and how it relates to other resources as
"actions" and "groups" will be better explained in the following paragraphs.
The "sort_template" resource syntax is a named resource. The scope of this resource is the
"template" declaration. This means that different templates (EntryTemplate) may declare the same
"sort_template" identifier. The table "ENTRY_PRELIMINARY_ACTION" section syntax may
reference the same "sort_template" identifier as a parameter of a "set_sort" built-in function call.
This parameter will be searched within the currently assigned entry template declaration, and the
local "sort_template" declaration will be used.
205678826.doc
UNCLASSIFIED
Page 66
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Each "sort_template" syntax defines a sort key string, composed by the sub-strings obtained from
the right side of the "sort_template" "reference" syntax. Its syntax is:
Syntax
reference:
<sort_reference_identifier>
(
[order: {ASCENDING | DESCENDING}] |
[length: <length_identifier>]
)
where:
<sort_reference_identifier> could be for example
one of the identifiers described in the paragraph
3.7.3.1.1;
the token "order" is followed by one of the two
keywords: ASCENDING - meaning that the
numerical string has not to be complemented - and
DESCENDING - meaning that the numerical string
has to be complemented (its value gives inverse
ordering, in other words the "bigger" string value
causes the entry positioning on the top of the list);
the token "length" is used when the value related to
the <sort_reference_identifier> must be repeated to
generate a key string of the desired length
205678826.doc
UNCLASSIFIED
Page 67
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
3.7.3
D
28/02/2003
Merging "Actions" Resource, "Groups" Resource, "Sort_Template"

Resources To Define Table List Entries Grouping And Ordering.
"Actions" table resource may have up to four subsections: these are

"HEADER_PRELIMINARY_ACTION", "HEADER_BACKGROUND_ACTION",
"ENTRY_PRELIMINARY_ACTION" and "ENTRY_BACKGROUND_ACTION".
The first two subsections concern the behaviour of the pure table elementary objects, while the
remaining two define the behaviour of the table list entry.
Later on we are going to concentrate on the "ENTRY_PRELIMINARY_ACTION" capabilities and
on the relation of this very important section with the other resources "groups" and "sort_template".
The "ENTRY_PRELIMINARY_ACTION" is the main table list entry action; it is the first one that
is executed when the HCI application has to insert a new entry within a table list.
This "action" resource section allows the definition of the "EntryTemplate" that has to be applied to
the new entry; it also allows the definition of the "sort_template" to be applied for the entry
ordering within all the list entries. It also allows to assign an entry to a pre-declared group.
The meaning of the following syntax tokens or resources must be clear in mind to better understand
what we is going to be described further on:
reference: it is used as a variable within a standard syntax : its name is a constant keyword (which
depends on the application specific "database table" structure), allowing to inquiry the value of the
current object resource related to the keyword itself. When this syntax element is used within the
tabular tool - list entry environment - it could refer, for instance, to an attribute (i.e. resource) of an
entry that might be a flight, or an alarm recorded event, and so on.
template: as it was previously stated a template is a set of information regarding a tabular object
layout and behaviour, that are applied all together when the application sets the current state of a
tabular object (table or table list entry) to the specified template. Within the table "actions"
resource it is possible to use the "switch" program control section, and to call built-in functions such
as "set_template", "set_group", "set_sort" and other.
205678826.doc
UNCLASSIFIED
Page 68
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
3.7.3.1 Defining Table List Entries Grouping, Ordering And Layout: "Entry Strip
Bay" : A Case Study
One of the most complex syntax at present used in table list managing is the one written for the
"ESB" (or "Entry Strip Bay") table. Our intention is to define the related syntax, using the tabular
syntax capabilities by steps: so we will define some intermediate easy requirements first, then we
will develop them, and we will gradually increase the requirements complexity to reach the final
target.
205678826.doc
UNCLASSIFIED
Page 69
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
3.7.3.1.1 Within The Example: Used Constants And References

We have to define the meaning of some constants and references used during this exercise:
Constants:
MAX_AIRPORT_NUM : application constant that defines the maximum number of airports
supported within a system
MAX_FIX_NUM : application constant that defines the maximum number of route fixes supported
within a system
SORT_TIME_LENGTH : application constant that defines the (string) length of every "reference"
relative to "time" resources (Estimated Time Of Departure, Estimated Time Of Landing, ).
SORT_ALV_LENGTH : application constant that defines the (string) length of the "reference"
relative to the "flight" object "clearance level" resource.
Template constants:
ESB_DEP_PEN_TEMPLATE : template to be applied to departure flights when they are in
pending state
ESB_ARR_PEN_TEMPLATE : template to be applied to arrival flights when they are in pending
state
ESB_ENR_PEN_TEMPLATE : template to be applied to en-route flights when they are in pending
state
ESB_DEP_ACT_TEMPLATE : template to be applied to departure flights when they are in active
state
ESB_ARR_ACT_TEMPLATE : template to be applied to arrival flights when they are in active
state
ESB_ENR_ACT_TEMPLATE : template to be applied to en-route flights when they are in active
state
DEP_MALTA_SEPARATOR_TEMPLATE : template to be applied to departure flights groups
headers (or separators)
ARR_MALTA_SEPARATOR_TEMPLATE : template to be applied to arrival flights groups
ENR_MALTA_SEPARATOR_TEMPLATE : template to be applied to en-route flights groups
References:
RECORD_TYPE_REF : refernce allowing to know if the entry is an effective one (it could be a
flight strip) or an entry group header (separator); it can assume two values : SEPARATOR_CASE
or ENTRY_CASE.
GROUP_CASE_REF : reference allowing to know the group to which belongs the entry or
separator. For the values provided by this example scripts please refer to the "groups" syntax
declaration paragraph. As stated over there, the three declared groups are: DEP_GROUP_CASE for
departure airport group entry, ARR_GROUP_CASE for arrival airport group entry,
ENR_GROUP_CASE for en-route fix group entry.
TOGGLE_SORT_REF : reference allowing to know if the global inverse ordering has been
activated. Acceptable values for this reference resource are TRUE_CASE and FALSE_CASE.
205678826.doc
UNCLASSIFIED
Page 70
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
TOGGLE_GROUP_REF : reference allowing to know if the alternative single entry manual

ordering is active (after manual CWP operator action). Acceptable values for this reference resource
are TRUE_CASE and FALSE_CASE.
FLY_TYPE_REF : reference allowing to know the "section" to which belongs the entry.
Acceptable values are DEP_CASE for departure section, ARR_CASE for arrival section,
ENR_CASE for en-route section.
FLY_STATUS_REF : reference allowing to know the flight status. Acceptable values are:
FLY_STATUS_PENDING_CASE for pending status flights, FLY_STATUS_ACTIVE_CASE for
active status flights, FLY_STATUS_LIVE_CASE for live status flights,
FLY_STATUS_TERMINATED_CASE for terminated status flights.
Sort reference identifiers:
SORT_REF_CONST_0 : used within a "sort_template" syntax to define the char '0'.
SORT_REF_GROUP_IDX : used within a "sort_template" syntax, it returns the internal use
"group" index, evaluated through the sum of a "section" base value with a relative group identifier.
SORT_REF_ETD : used within a "sort_template" syntax, it returns the estimated time of departure
of the current flight (table list entry).
SORT_REF_ETL : used within a "sort_template" syntax, it returns the estimated time of landing of
the current flight (table list entry).
SORT_REF_ETO : used within a "sort_template" syntax, it returns the estimated time off-block
(out of fix) of the current flight (table list entry).
SORT_REF_ALV : used within a "sort_template" syntax, it returns the clearance level of the
current flight (table list entry).
Group references:
$DEP_AIRP_IDX_REF : used as a parameter for a "set_group" built-in function, it allows to
identify the relative index for an airport used as departure airport.
$ARR_AIRP_IDX_REF : used as a parameter for a "set_group" built-in function, it allows to
identify the relative index for an airport used as arrival airport.
$FIX_I_IDX_REF : used as a parameter for a "set_group" built-in function, it allows to identify the
relative index for an rout fix seen as inbound fix.
205678826.doc
UNCLASSIFIED
Page 71
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
3.7.3.1.2 Within The Example: Viewing Different Strip Layouts Depending On The
Flight Type Attribute
Imagine we need to visualize each added flight strip with a different layout depending on the flight
type: "departure type" ("DEP"), "arrival type" ("ARR"), "en-route" type ("ENR").
To assign a different template, for each flight type, in the ENTRY_PRELIMINARY_ACTION
section of the table "actions" syntax the "set_template" build-in function shall call the template
correspondent to the current FLY_TYPE_REF reference value.
For instance, here is a sample syntax:
Fig._____ 3.7.3.1.2-1 Table "actions" Syntax For Flight Type Layout
205678826.doc
UNCLASSIFIED
Page 72
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
3.7.3.1.3 Within The Example: Flight Strips Table List Entries Ordering Depending
On The Flight Type Attribute
The IES Tabular tool allows to order each added flight strip according to the flight type resource.
For instance, if we want the list to begin with the "DEP" flight strips entries, followed by the
"ARR" type ones, and finnally by the "ENR" ones, within each assigned template (EntryTemplate),
a different "sort_template" syntax has to be inserted.
To do so, in each EntryTemplate an "Entry Template Sort" resource will have to be defined by
means of a "sort_template" syntax, having the same <sort_template_identifier> but different
declarations.
Here is an example of such a procedure:
Fig._____ 3.7.3.1.3-2 "ESB_DEP_PEN_TEMPLATE" EntryTemplate Properties Editor
Fig._____ 3.7.3.1.3-3 "sort_template" Resource Syntax Within The "ESB_DEP_PEN_TEMPLATE"

Properties Editor
205678826.doc
UNCLASSIFIED
Page 73
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig._____ 3.7.3.1.3-4 "ESB_ARR_PEN_TEMPLATE" EntryTemplate Properties Editor
Fig._____ 3.7.3.1.3-5 "sort_template" Resource Syntax Within The "ESB_ARR_PEN_TEMPLATE"

Properties Editor
205678826.doc
UNCLASSIFIED
Page 74
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig._____ 3.7.3.1.3-6 "ESB_ENR_PEN_TEMPLATE" EntryTemplate Properties Editor
Fig._____ 3.7.3.1.3-7 "sort_template" Resource Syntax Within The "ESB_ENR_PEN_TEMPLATE"

Properties Editor
Different "sort keys" are defined for each used EntryTemplate to order the flight strip: "sort key" '0'
for "DEP", "sort key" '1' for "ARR", and "sort key" '2' for "ENR". Note that the same
<sort_template_identifier> has been defined for all the involved EntryTemplates and will be used
as a parameter for the "set_sort" build-in function within the "actions" syntax that will look like that
of the following figure.
205678826.doc
UNCLASSIFIED
Page 75
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig._____ 3.7.3.1.3-8 Table "actions" Syntax Entries Ordering By Flight Type
The "set_sort" built-in function searches the <sort_template_identifier> parameter within the
assigned EntryTemplate. Which means that the <sort_template_identifier> parameter must have
been declared within the specified EntryTemplate.
With the following examples it will be shown that a template (i.e. EntryTemplate) may have more
than one "sort_template" sections, with different <sort_template_identifiers>.
205678826.doc
UNCLASSIFIED
Page 76
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
3.7.3.1.4 A Parenthesis: Something More About The Groups Syntax

I the current paragraph, the meaning and the syntax of the "groups" list node resource is going to be
better explained.
To define a "group", a parameter indicating the group to be created must be defined, and it can be
common for many entries.
Opening the "LIST" (the structural Entry root) node properties editor, and the "groups" related
syntax editor this is what can be seen:
Fig._____ 3.7.3.1.4-9 "groups" Table Resource Editing Example
In this syntax three "sections" are defined: "DEP_GROUP_CASE", "ARR_GROUP_CASE" and

"FIX_GROUP_CASE".
For each "section" the number of possible "sub-sections" (or "groups") is also defined. For instance,
for "DEP_GROUP_CASE" and "ARR_GROUP_CASE" there will be MAX_AIRPORT_NUM
groups, while for "FIX_GROUP_CASE" there will be MAX_FIX_NUM groups.
In the first three lines of the syntax the values to be assigned to the three identifiers have also been
declared: DEP_GROUP_CASE is assigned to 0, ARR_GROUP_CASE is assigned to
MAX_AIRPORT_NUM, FIX_GROUP_CASE is assigned to 2*MAX_AIRPORT_NUM. In this
way, they have been defined as constants that may be furtherly used in the same syntax.
The last line of the "groups" syntax declares a reference for internal use, called
"GRAN_TOT_CASE". Its value is the sum of the number of items of all the declared groups; from
DEP_GROUP_CASE group, to ARR_GROUP_CASE, FIX_GROUP_CASE, until index of the last
group FIX_GROUP_CASE+MAX_FIX_NUM-1.
This internal table list reference may be used to display the entries total number of all groups, if it is
the reference of a visible table text field.
205678826.doc
UNCLASSIFIED
Page 77
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
3.7.3.1.5 Within The Example: Flight Strips Table List Entries Ordering Depending
On The Flight Type And Group Identifier Attribute
Lets now have a look to what has to be done to order each added flight strip according to the flight
type resource, and to the "group" identifier resource.
The "group" mechanism meaning will be furtherly explained; lets now relate the group to an
airport or to a route fix.
For instance, on the top of the table list all the flight "DEP" type strip entries will have to be listed
according to the departure airport identifier: first the flights coming from the airport
<dep_name_1>, than those coming from the airport <dep_name_2>, and so on until the flights
coming from the airport <dep_name_MAX_AIRPORT_NUM>.
Similarly, the "ARR" type flight strips will be listed according to the arrival airport identifier:
starting from the flights directed to the airport <arr_name_1>, until those directed to the airport
<arr_name_MAX_AIRPORT_NUM>.
Finnaly, the "ENR" type flight strips will follow the same kind of rule: they will be listed according
to the inbound fix identifier: starting from the flights whose inbound fix identifier is <fix_name_1>
until those whose inbound fix identifier is <fix_name_MAX_FIX_NUM>.
To obtain this requirement we have to change the three previously seen EntryTemplates "Entry
Template Sort" resource. Using the syntax resource editor we must change the "sort_template"
syntax as shown in the following figures.

Properties Editor

Properties Editor
205678826.doc
UNCLASSIFIED
Page 78
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003

Properties Editor
Within the table "actions" syntax, we have to add the setting of the group identifier for each entry:
this is done calling the "set_group" built-in function.
Fig._____ 3.7.3.1.5-13 Table "actions" Syntax Entries Ordering By Flight Type And Group Identifier
For the meaning of the "set_group" parameters please refer to the paragraph 3.7.3.1.1
205678826.doc
UNCLASSIFIED
Page 79
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
3.7.3.1.6 Within The Example: Building A Header For Table List Entries Groups
The requirement that we want to satisfy is to create, for each existent group, a special entry that
identifies the group itself.
This identifier that we will call "separator" must be positioned before all the flight entries belonging
to each group.
The "separator" should visualise the "section" identifier ("DEP"/"ARR"/"ENR"), the group
identifier (i.e. the name of the related airport or fix), and the number of flight entries belonging to
the group.
This means that we need to define a new table list entry template (EntryTemplate). So we are going
to identify another classification within the entries, related to a new reference that identifies if the
table list entry is or a "standard entry (strip in the example)", or a "(group) separator". This
reference will be identified with the RECORD_TYPE_REF one that can assume the values
ENTRY_CASE or SEPARATOR_CASE.
We need three (DEP/ARR/ENR) new EntryTemplates, with specified "sort_template" syntax. The
sort_template syntax itself will be extended to provide different ordering for the two just mentioned
record types. For this reason, also the "standard entry" "sort_template" syntax has to be modified.
All of these changes are shown in the following figures.
Fig._____ 3.7.3.1.6-14 "DEP_SEPARATOR_TEMPLATE" EntryTemplate Properties Editor
205678826.doc
UNCLASSIFIED
Page 80
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig._____ 3.7.3.1.6-15 "sort_template" Resource Syntax Within The

"DEP_SEPARATOR_TEMPLATE" Properties Editor
As can be observed the "sort_template" syntax for this EntryTemplate has got a third token set to
the '0' character. And this will be also for the two following EntryTemplates.
Fig._____ 3.7.3.1.6-16 "ARR_SEPARATOR_TEMPLATE" EntryTemplate Properties Editor
205678826.doc
UNCLASSIFIED
Page 81
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003

"ARR_SEPARATOR_TEMPLATE" Properties Editor
Fig._____ 3.7.3.1.6-18 "ENR_SEPARATOR_TEMPLATE" EntryTemplate Properties Editor

"ENR_SEPARATOR_TEMPLATE" Properties Editor
While normal entries "sort_templates" syntax has the third token set to the '1' character (so the sort
key is greater, and each entry belonging to the same section and group follows the separator entry).
205678826.doc
UNCLASSIFIED
Page 82
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003

Properties Editor

Properties Editor

Properties Editor
205678826.doc
UNCLASSIFIED
Page 83
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Now we have to update the table "actions" syntax, assigning the new EntryTemplates depending on
the "record type" value; the required ordering will depend automatically by the sort_template
syntax.
Note that the separator record type is not directly related to a flight, so it can be distinguished only
by the reference GROUP_CASE_REF and not for the flight reference FLY_TYPE_REF.
Talking about the flight entries, we can observe that the reference GROUP_CASE_REF cannot be
used to distinguish the section, as the group identifier is assigned after the test on
FLY_TYPE_REF.
Follows the table "actions" syntax example:
Fig._____ 3.7.3.1.6-23 Table "actions" Syntax For Adding Group Header Entries
The ATC flight manager of the application executes only a request to add a flight entry within an its
own created list. The list manager adds automatically a group separator, if groups have been
declared. It manages also the groups sub-totals, and the change-group function, if required, as we
will see in a later example.
As a result we will obtain that the list entries will be ordered as follows:
205678826.doc
UNCLASSIFIED
Page 84
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
RECORD TYPE
DEP Section:
SEPARATOR
ENTRY
(entries)
ENTRY
(groups)
SEPARATOR
ENTRY
(entries)
ENTRY
ARR Section:
SEPARATOR
ENTRY
(entries)
ENTRY
(groups)
SEPARATOR
ENTRY
(entries)
ENTRY
ENR Section:
SEPARATOR
ENTRY
(entries)
ENTRY
(groups)
SEPARATOR
ENTRY
(entries)
ENTRY
205678826.doc
SORT_TEMPLATE
NAME
SORT KEY
NORMAL_SORT
NORMAL_SORT_A
NORMAL_SORT_A
'0' + group + '0'

'0' + group + '1'
'0' + group + '1'
NORMAL_SORT
NORMAL_SORT_A
NORMAL_SORT_A
'0' + group + '0'

'0' + group + '1'
'0' + group + '1'
NORMAL_SORT
NORMAL_SORT_A
NORMAL_SORT_A
'1' + group + '0'

'1' + group + '1'
'1' + group + '1'
NORMAL_SORT
NORMAL_SORT_A
NORMAL_SORT_A
'1' + group + '0'

'1' + group + '1'
'1' + group + '1'
NORMAL_SORT
NORMAL_SORT_A
NORMAL_SORT_A
'2' + group + '0'

'2' + group + '1'
'2' + group + '1'
NORMAL_SORT
NORMAL_SORT_A
NORMAL_SORT_A
'2' + group + '0'

'2' + group + '1'
'2' + group + '1'
UNCLASSIFIED
D
28/02/2003
Page 85
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
3.7.3.1.7 Within The Example: Building A Header For Table List Entries Groups
The requirement that we want to satisfy is to have, for each entry, two alternative ordering ways.
We want that:
DEP flights entries could be ordered by "departure airport" or by "outbound fix.
ARR flights entries could be ordered by "arrival airport" or by "inbound fix"
ENR flights entries could be ordered by " inbound fix " or by "outbound fix".
We have to manage a new reference (TOGGLE_GROUP_REF, assuming the values TRUE_CASE
or FALSE_CASE) that allows knowing if the entry ordering is normal (NORMAL_SORT_A) or
alternative (NORMAL_SORT_B).
We can derive that under this requirement a flight entry could change also the original section,
going for instance from the ARR section to the ENR section.
The "sort_template" syntax involved in this requirement is only these related to "entry (flight)"
record type (no changes for "separator" record type EntryTemplates).

Properties Editor
205678826.doc
UNCLASSIFIED
Page 86
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003

Properties Editor

Properties Editor
Now we have to update the table "actions" syntax. Changes will regard the "set_group" built-in
functions call (to change group as required at the beginning of this paragraph) and the "set_sort"
one. Follows the table "actions" syntax example:
205678826.doc
UNCLASSIFIED
Page 87
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig._____ 3.7.3.1.7-27 Table "actions" Syntax To Allow Multiple Ordering
205678826.doc
UNCLASSIFIED
Page 88
E000IES0-09SUM
UNCLASSIFIED
Issue
Date:
D
28/02/2003
3.7.3.1.8 Within The Example: Flight Status Depending Layouts

The requirement that we want to satisfy is to have, for each entry, a specific layout depending on
the flight status ("pending", "active", "live", "terminated") and on the flight type
("DEP","ARR",ENR"). We want that:
FLIGHT
TYPE:
"DEP"
"DEP"
"ARR"
"ARR"
"ENR"
"ENR"
FLIGHT STATUS:
ENTRY TEMPLATE:
"pending"
"active", "live", "terminated"
"pending"
"pending"
"ESB_DEP_PEN_TEMPLATE"
"ESB_DEP_ACT_TEMPLATE"
"ESB_ARR_PEN_TEMPLATE"
"ESB_ARR_ACT_TEMPLATE"
"ESB_ENR_PEN_TEMPLATE"
"ESB_ENR_ACT_TEMPLATE"
It will be necessary to add a new template for each "flight type" ("ESB_DEP_ACT_TEMPLATE",
"ESB_ARR_ACT_TEMPLATE" and "ESB_ENR_ACT_TEMPLATE").
Normally active flights have many more information fields than pending flights. So these templates
will set to On the visibility of many of the declared entry fields, and will assign a grid relative
position to those fields that have not been declared for their position within the structure declaration
operation.
The table "actions" section will change as in the following example:
205678826.doc
UNCLASSIFIED
Page 89
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig._____ 3.7.3.1.8-28 Table "actions" Syntax For Flight Status Depending Layouts (1st)
205678826.doc
UNCLASSIFIED
Page 90
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig._____ 3.7.3.1.8-29 Table "actions" Syntax For Flight Status Depending Layouts (2nd)
205678826.doc
UNCLASSIFIED
Page 91
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
3.7.3.1.9 Within The Example: Ordering Table List Entries Within Groups By
Resources Values
The requirement that we want to satisfy is to order each entry, within its group, by the "time"
resource and the "clearance level" one.
We want that:
DEP flights entries should be ordered by decreasing "estimated time of departure" ("ETD"), and
secondarily by "clearance level" ("ALV").
ARR flights entries should be ordered by decreasing "estimated time of landing" ("ETL"), and
ENR flights entries should be ordered by decreasing "estimated time of off-block" ("ETO"), and
The "sort_template" syntax involved in this requirement is these related to "entry (flight)" record
type but also for "separator" record type, as the length of the "sort key" strings has to be the same
for all table list items.

Properties Editor
205678826.doc
UNCLASSIFIED
Page 92
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig._____ 3.7.3.1.9-31 "sort_template" Resource Syntax Within The "ESB_DEP_ACT_TEMPLATE"

Properties Editor

Properties Editor
205678826.doc
UNCLASSIFIED
Page 93
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig._____ 3.7.3.1.9-33 "sort_template" Resource Syntax Within The "ESB_ARR_ACT_TEMPLATE"

Properties Editor

Properties Editor
205678826.doc
UNCLASSIFIED
Page 94
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig._____ 3.7.3.1.9-35 "sort_template" Resource Syntax Within The "ESB_ENR_ACT_TEMPLATE"

Properties Editor
We have to notice that the "mode: ORDER_DESCENDING" allows an ordering that puts at the top
of each group those strips that have higher time parameter (and therefor an assigned time value
different from '000'0).
As a consequence, the "separator" EntryTemplates will be changed, to obtain a same length "sort
key":

DEP_SEPARATOR_TEMPLATE" Properties Editor
The same will be done for the "ARR_SEPARATOR_TEMPLATE" sort_template" resource and for the
"ENR_SEPARATOR_TEMPLATE" one.
205678826.doc
UNCLASSIFIED
Page 95
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
3.8
D
28/02/2003
TABLE STRUCTURE ARCHITECTURE
In many examples within the paragraphs of this manual you will have observed that geometrical
resources often make use of arithmetic expressions, containing symbolic variables. Within the
Tabular editor a group of variables assume specific meanings.
In this paragraph we try to explain to which geometrical table basic resources those variables are
related.
For this purpose, we make use of a generic table structure graphical representation, where those
variables are shown, with segments explaining their geometrical length.
We have also listed those variables (that are syntax-reserved keys), together with their related
expression, in the next table.
Those variables, concerning table structure geometry, are designed for table proportion
maintenance. Variable definition is made in a sequential way, with multiple correlation. This
provides table components proportion also in case of changes. For example, if you change the value
of the resource "char_height" (the default used font character grid height), the change has effect to
variables directly dependent, like "tsh", "hbh" and "ebh". Consequently, the variables that make use,
within their expression, of "tsh", "hbh" or "ebh" are modified, and so on.
Correlated sysntax-reserved variables are defined within the file "local_assign.dsp". The following
table shows most of those variables definition:
VARIABLE NAME
CALCULATED VALUE
tsh
"title_top_offset+title_bottom_offset+(char_height* title_rows)"
hbh
"(header_rows*char_height)+header_interline*(header_rows-1)"
hsh
"hbh+header_top_offset+header_bottom_offset"
ebh
"(entry_rows*char_height)+entry_interline*(entry_rows-1)"
ebw
"total_chars_in_row*char_width"
esw
"ebw+entry_left_offset+entry_right_offset"
esh
"ebh+entry_top_offset+entry_bottom_offset"
EBH
"max_rows*esh"
EBW
"max_columns*esw"
ESH
"entries_top_offset+entries_bottom_offset+EBH"
ESW
"(entries_left_offset+entries_right_offset)*max_columns+EBW"
TH
"tsh+hsh+ESH"
TW
"ESW"
tw
"entries_left_offset+entries_right_offset+default_columns*esw"
sh
"esh/slot_rec"
sw
"esw"
wlx
"0.0"
wrx
"(entries_left_offset+entries_right_offset)+default_columns*esw+scroller_width"
TITLE_XR
"wrx"
TITLE_XL
"wlr"
SO
"tsh + hsh + entries_top_offset + 2"
title_len
"strlen(title)"
X_START_TITLE
"wlx+((wrx-wlx-(title_len*char_width))/2)"
X_AFTER_TITLE
"X_START_TITLE+(title_len*char_width)"
ENTRY_GRID_OFFSET_X
"entry_left_offset+box_offset"
ENTRY_GRID_OFFSET_Y
"entry_top_offset+box_offset"
205678826.doc
UNCLASSIFIED
Page 96
E000IES0-09SUM
UNCLASSIFIED
Issue
Date:
D
28/02/2003
Graphical interpretation of variable correlation looks like the following picture:

(title_rows)
wlx = 0, 0
Title
tsh
title_top_offset
char_height
title_bottom_offset
(header_rows)
header_top_offset
hbh
Header
hsh
char_height
header_interline
box_offset
header_bottom_offset
entries_top_offset
(entry_rows)
TH
entry_interline
entry_bottom_offset
entry_left_offset
entry_right_offset
ebw
entries_left_offset
sh = esh / slot_rec
tot_chars_in_row
EBH
ESH
ebh
esh
entry_top_offset
entries_right_offset
esw = sw
scroller_width
entry_bottom_offset
EBW
default_columns (max_columns)
TW=ESW (for max_columns) TW=tw (for default_columns)
Fig.__ 3.8-22 Table Structure Variables Representation
As we can observe in the table structure representation, the syntax-reserved variables are grouped
depending on the table section they relate.
So "tsh", "title_len", ", "X_START_TITLE", "TITLE_XR", "TITLE_XL" and "X_AFTER_TITLE"
are used for objects located within the Title table section.
"hbh", "hsh" are used for objects located within the Header table section. "ebh", "ebw", "hsh",
"ENTRY_GRID_OFFSET_X" and "ENTRY_GRID_OFFSET_Y" are used for objects positioned
within the single entry of the list.
"EBH", "EBW", "ESH", "ESW" are normally used for objects positioned with reference to the table
List section.
The other variables use the single table section reserved variables to obtain the whole table
parameters as "tw", "TH" and "TW".
Many of the graphical primitives used for table presentation are related to these syntax reserved
variables so that they become resizable, depending on specific table section resources changes. This
simplifies the action to change the aspect ratio of a table, its size, or the number of characters for an
entry, the number of rows for the header, for the single entry, for the whole list, and so on.
The user might build its own variables, starting from these basic ones, if needed.
205678826.doc
UNCLASSIFIED
Page 97
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
205678826.doc
UNCLASSIFIED
D
28/02/2003
Page 98
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
3.9
D
28/02/2003
CREATING A NEW LIST
In order to create a new list using the Ies Tabular tool you can follow two different methods,
starting from a default list table, or duplicating an existent one.
When you choose the first method you may use the File->New Functionality of the Ies Tabular.
For a more exaustive explanation of this command please refer to the par. 4.1.1.2 MENU ITEM
"NEW", and for an help on adding new grids, or text/symbol fields or editing existent ones, please
refer to the par. 4.2 POP-UP MENUS. Follow the instructions at the end of this paragraph, to edit
the lists.dsp file, for a complete integration of the new table within the site system.
Using the second method might be better, if you choose an existent table, with similar
characteristics. But remember, this operation requires more attention.
Start opening an existent table that you want to copy, then save this as a new file, named for
instance new_table(using the File->Save as menu). At this point you must exit from the IES
Tabular and start a manual editing of a set of files.
At First, open the new_table.dsp file created in the ddl site system directory. You will find all
the fields and the tokens of the cloned table. Then you should replace all the strings referring at the
old table with a new string, only to personalize the new table. For instance if you clone the FLDI
table you will find personilised strings in your file : TableName :FLDI ,FLDI_TXT1,
FLDI_SYMB1 , etc. Please replace this token (FLDI in this example) with a new one (for
example NEW). The result is: TableName :NEW ,NEW_TXT1, NEW_SYMB1 , etc.
Pay attention making these changes: the only names that can be changed, without mistakes, are
presentation objects, or primitives, or attributes, or template names.Some other identifiers,
containing the token, might be application identifiers, that come from editable code header files.
For instance you might find tokens like FLDI_CHAR_HEIGHT. Please dont change this kind of
identifiers, and follow, before, the procedure described in the following sentence.
Having saved the new file, you will add some other information in another file, named
list_configuration.h, in the include system directory (after the File->New command a
message will remember you this operation). In this file you will find the information about all the
defined tables. Please find the duplicated table information (for example
FLDI_TOT_CHARS_IN_ROWS) and add information about your new table (for example
NEW_TOT_CHARS_IN_ROWS etc.).
In order to edit list_configuration use the Edit->List Configuration menu functionality (see
par.4.1.6.4 MENU "BROWSER", ITEM "LISTS CONFIGURATION")
205678826.doc
UNCLASSIFIED
Page 99
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig.__ 3.9-23 Adding defines Using List Configuration Editor
For a complete use of this new table by the IES, it is required a change of the file lists.dsp,
located in the ddl directory of the system in use. In this file you must add a new line with the
same syntax of the other entries and with the name of the new file saved new_table.
In order to edit lists.dsp use the Edit->Lists menu functionality (see par.4.1.6.3 MENU
"BROWSER", ITEM "LISTS")
See the following example pictures of lists.dsp after the change.
205678826.doc
UNCLASSIFIED
Page 100
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig.__ 3.9-24 List Editor Shell
After some change, clicking on the "File" button the menu will appear. Selecting the "Save" button
the fileSelectionBox will appear.
This window automatically allows to save the lists.dsp file, select the file and confirm clicking on
the "Ok" button.
3.9.1
COPY OR MOVE OBJECTS FROM AN EXISTENT TABLE
In order to import nodes (grids or fields) to your new table from an existing one see paragraphs
concerning about copy, move and attach operations (par. 4.2.9, 4.2.10, 4.2.11)
3.10 CREATING A NEW TRANSPARENT TABLE

In order to create a new transparent list using the Ies Tabular tool you can follow these steps.
You need working with a multiple table tabular component. So load the tabular component from
the menu File->Load button. After that you must select one of the existent transparent tables,
by clicking on the "Select" button. The selection-box will appears, containing the list of a particular
205678826.doc
UNCLASSIFIED
Page 101
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
group of tables : transparent tables. This list of tables is enumerated in the tabular.dsp file
(ddl of system in use directory). Edit this file, making use of the Text Editor window, and
add the new table (see the following example of file):
#include_table
#include_table
#include_table
#include_table
#include_table
#include_table
<csl_list.dsp>
<sil_list.dsp>
<mlb_list.dsp>
<llp_list.dsp>
<ghost_list.dsp>
<new_trans_table.dsp> ! NEW TRANSPARENT LIST ADDED
After this, you must create the new table itself, saving it within, new file, named
new_trans_table.dsp. Copy an existent table, or use the Save as command (obviously you must
load one of the existent transparent tables).
In order to personalise the fields of this new table, follow the suggestions described in the previous
paragraph.
The last step you shall execute, to complete this new transparent table integration, concerns the
level of visualization of this list (that is the priority resource). You must add a new priority
identifier, using the IES Gsl facility (menu "Edit", "Priority Levels").
\Alternatively, the transparent table priority might be fixed at a float value ranging about the values
0.60000 until 1.0 (highest level).
205678826.doc
UNCLASSIFIED
Page 102
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
USING MENUS
In the following paragraphs we are going to describe all the tool menus and their meaning. The tool
menus may be subdivided in two main groups: "menu bar menus" and object "pop-up menus".
4.1
MENU BAR MENUS
The "menu bar menus" group is always visible in the screen area.
The menu bar is the main panel section that allows managing the principal global actions provided
by the tool. Clicking the left mouse button on the items of the menu bar, the corresponding menu
list of commands is shown. So, selecting an item of the menu, the execution of the corresponding
command will start, or a cascade menu will be presented.
It looks like the following:
Fig.__ 4.1-25 IES Tabular Main Menu Bar
205678826.doc
UNCLASSIFIED
Page 103
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
4.1.1
D
28/02/2003
MENU "FILE"
To start an editing session on a table you must click on the "File" button. A list of command will be
shown. A pull-down menu will appear as shown below:
Fig.___ 4.1.1-14 IES Tabular "File" Menu Button

:
4.1.1.1 MENU ITEM "LOAD"

Clicking on the "Load" button you can choose the component table.
Fig.____ 4.1.1.1-13 IES Tabular "Load" Button
Normally a window will appear on the screen called "Component Selection" where you can choose
the working table, selecting an item in the list. Before the "Component Selection" window you can
see an Ies Warning Box that will advise you if the current table is modified, or you have done a
Move operation (for other information see the par. 4.2.10).
Fig.____ 4.1.1.1-14 IES Warning Box
205678826.doc
UNCLASSIFIED
Page 104
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Selecting the File Load menu Item, being working on the New Strip Area table, and being in
the Work On Strip Printer status, if the current sub-status is different than Electronic Structure, a Warning shall be notified to the operator, and the Load request rejected.
205678826.doc
UNCLASSIFIED
Page 105
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig.____ 4.1.1.1-15 IES Tabular Component Selection
Confirm your choose, clicking on the "Ok" or "Apply" button, or dismiss clicking on the "Cancel"
button. Then you can see the structural tree of the table and the preview window on the screen.
Fig.____ 4.1.1.1-16 Table (NSA) Layout In The Preview Area
205678826.doc
UNCLASSIFIED
Page 106
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
4.1.1.2 MENU ITEM "NEW"

You can create a new table selecting the "New" button of the menu.
Fig.____ 4.1.1.2-17 IES Tabular "New" Button
Normally a window will appear on the screen called "New Table" where you can insert the new
working table, writing in the textbox. Before the "New Table" window you can see an Ies Warning
Box that will advise you if the current table is modified, or you have done a Copy or Move
operation (for other information see the par. 4.2.10)
Fig.____ 4.1.1.2-18 IES Warning Box
Fig.____ 4.1.1.2-19 IES Tabular New Table Shell Name
After your click, a new window appears; insert a name in the text field and click the "Ok" button to
confirm or "Cancel" to dismiss. On the screen will appear a default structural tree and the table
layout will look like that of the following figure:
205678826.doc
UNCLASSIFIED
Page 107
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig.____ 4.1.1.2-20 GFR Layout
Fig.____ 4.1.1.2-21 IES Tabular "GRF" Table Tree
205678826.doc
UNCLASSIFIED
Page 108
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
4.1.1.3 MENU ITEM "SAVE"

Clicking on the "Save" button you can update the table project files, without exiting the session.
Fig.____ 4.1.1.3-22 IES Tabular "Save" Button
Before every Save-operation its necessary to check the current mode on the title of the BlackBoard
window: if you work on Structure mode you can save the project, otherwise (working on
Template mode) you will see the following error message :
Fig.____ 4.1.1.3-23 Error Dialog" For Save In Template Mode
4.1.1.3.1 AUTOMATIC BACKUP

In order to provide a maintenance activity relative to IES project its necessary, before every Saveoperation, to make a copy of the previous dataset. The security backup of the files (.dsp) is made
with the same name and extension of the original files, with an additional extension including the
information about the current year, month, day, hour, minute and second
(.<YYYYMMDDHHMMSS>); the backup file is created in a new directory named "backup.d"
under the project ddl directory.
For instance, in a system named demo, if you execute a save project action for the esb table, you
will see the following message in the Xterm Window:
NOTICE: A Copy Of The File:
/disk6/cwpgen/system/demo/source/ddl/esb.dsp
Has Been Written As The Backup File:
/disk6/cwpgen/system/demo/source/ddl/backup.d/esb.dsp.Y1999M09D28h10m32s17
/disk6/cwpgen/system/demo/source/ddl/backup.d/esb_layout.dsp.Y1999M09D28h10m32s17
/disk6/cwpgen/system/demo/source/ddl/backup.d/esb_actions.dsp.Y1999M09D28h10m32s18
205678826.doc
UNCLASSIFIED
Page 109
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003

/disk6/cwpgen/system/demo/source/ddl/backup.d/esb_templates.dsp.Y1999M09D28h10m32s18
In this example the saving operation is accomplished at 10:32:17-8, 28/09/99.

The backup action include some other file if you modify primitives or other particuar components.
The backup action takes place only if the project file is already located under the project ddl
directory (and not in case of library project files).
4.1.1.4 MENU ITEM "SAVE AS"

Clicking on the "Save As" button you can create a new table project file, without exiting the
session.
Fig.____ 4.1.1.4-24 "Save as" Button
When you select this feature the following window "fileSelectionBox" will appear:
Fig.____ 4.1.1.4-25 FileSelectionBox
205678826.doc
UNCLASSIFIED
Page 110
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Change directory by "Directories" section; select files from "Files" section to overwrite an existing
project file or digit the path and/or filename in "DSP File" section. The "Save as" command save all
the table information only in a file.
Then press the "OK" button to confirm or the "Cancel" button to dismiss the shell.
4.1.1.4.1 AUTOMATIC BACKUP

For an explanation of this operation see at the par. 4.1.1.3.1, but the Save as command save only a
file (for instance "esb.dsp").
/disk6/cwpgen/system/demo/source/ddl/backup.d/esb.dsp.Y1999M09D28h10m32s17
The backup action takes place only if you overwrite an existent project file under the project ddl
directory (and not in case you create a new project file).
4.1.1.5 MENU ITEM "EXIT"

Press the "Exit" button to close the "IES Tabular" working session.
Fig.____ 4.1.1.5-26 IES Tabular "Exit" Button
A "IES Warning Box" will appear, and a warning message will ask you if you want to confirm
("OK" button) or abort the exit command ("Cancel" button).
Fig.____ 4.1.1.5-27 Exit Mask
205678826.doc
UNCLASSIFIED
Page 111
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
4.1.2
D
28/02/2003
MENU "EDIT"
Clicking on the "Edit" button a pull-down menu appears.
Fig.__ 4.1-26 IES Tabular "Edit" Menu Button
4.1.2.1 MENU "EDIT", ITEM "PRIMITIVE"

Pressing the "Primitive" button a cascade menu appears.
4.1.2.1.1 SUB_MENU "EDIT" - "PRIMITIVE" - "LOCAL PRIMITIVE"

For the Tabular Editor Local Primitives are those having scope within the specific interface/table.
The figure shown below represents the commands list of the sub-menu "Primitive".
Clicking on the "Local Primitive" button:
Fig._____ 4.1.2.1.1-37 "Local Primitive" Button
A "Primitive Selection" box will appear, if exists some "Local Primitive" related with the
component in use:
205678826.doc
UNCLASSIFIED
Page 112
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig._____ 4.1.2.1.1-38 Primitive Selection Box
Choose the desired primitive, and click on the "Ok" button to confirm; to do the same thing, you
can use a double click on the desired item.
Automatically, the relative Properties Editor ("SYMBOL_FCF_ON") appears on the screen and
you can see and change the contained information.
Fig._____ 4.1.2.1.1-39 "SYMBOL_FCF_ON" Primitive Properties Editor
205678826.doc
UNCLASSIFIED
Page 113
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
In order to change values in the property editor you can use various ways:
It's possible to change the value for the "Attribute" textbox selecting an item into the "Attribute
Selection" panel; it will appear when you click the corresponding ">>" button. Then you can
confirm the choice with the Ok or Apply button or dismiss with the Cancel button.
Meanwhile you can see a little preview of the selected item in the Previewer area.
Fig._____ 4.1.2.1.1-40 "Attribute Selection" for Local Primitive Properties Editor
To select a different value for the "Color" textbox you can choice an item into the "Color Selection"
that will appear when you click on the corresponding ">>" button. Then you may confirm the
choice with the Ok or Apply button or dismiss with the Cancel button. Meanwhile you can
see a little preview of the item selected in the Previewer area.
To select a different value for the "Style" textbox you can choice an item into the "Style Selection"
that will appear when you click on the corresponding ">>" button. Then you may confirm the
choice with the Ok or Apply button or dismiss with the Cancel button. Meanwhile you can
see a little preview of the item selected in the Previewer area.
205678826.doc
UNCLASSIFIED
Page 114
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Following the common part of the Primitive Properties Editor (Name, Attribute, Color and Style
fields) you will find some additional rows depending on the type of the selected primitive.
In the case of RECTANGLE PRIMITIVE the property editor contains the four expressions for
the two vertexes necessary to define a rectangle:
Fig._____ 4.1.2.1.1-41 "Rectangle Primitive" Properties Editor
In order to change the values of "Lower Left X", "Lower Left Y [-]", "Upper Right X" or "Upper
Right Y[-]" you must apply the focus to the concerning textbox, and change the contents by
keyboard typing.
205678826.doc
UNCLASSIFIED
Page 115
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Also it's possible to type or load a long and complex formula using the Text Editor that will
appear clicking on the concerning "" button.
Fig._____ 4.1.2.1.1-42 "Text Editor for Local Primitive Properties Editor
Before confirming and updating the typed formula with the "Ok" or Apply button, you can save
to a file, or load from a file, a formula, using the menu File in the Text Editor; to dismiss all
press the "Cancel" button.
In the case of POLYLINE PRIMITIVE the properties editor contains the expressions for the
vertexes necessary to define the desired polyline:
Fig._____ 4.1.2.1.1-43 "Polyline Primitive" Properties Editor

205678826.doc
UNCLASSIFIED
Page 116
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
In order to change the values of a vertex (Point[x].X, Point[x].Y) you must type the values in the
corresponding text box. You may use the Text Editor too, as explained in the previous case.
Also, it's possible to add or remove a vertex of the polyline selecting an item in the concerning
"Add/Remove" popup menu, that will appear clicking on the corresponding "+/-" button:
Fig._____ 4.1.2.1.1-44 "Add/Remove Menu" for Local Primitive Properties Editor
The choice Add After is used to create a new vertex after the current one (Point [x + 1].X, Point[x
+ 1].Y).
The choice Add Before is used to create a new vertex inserted before the current one, shifting the
current one at the next position.
The choice Remove is used to remove the current vertex. Warning: you cant remove a vertex of
a single vertex polyline.
In the case of LIST OF PRIMITIVE the property editor contains the primitives necessary to
define the desired list:
Fig._____ 4.1.2.1.1-45 "List of Primitive" Properties Editor
To change the value of a primitive (Primitive[x]) you must select an item into the "Primitive
Selection" panel that will appear clicking on the corresponding ">>" button.
205678826.doc
UNCLASSIFIED
Page 117
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Confirm and update the primitive selected, with the "Ok" or Apply button, or double-clicking on
the desired item; to dismiss the selection press "Cancel" button.
Also it's possible to Add or Remove a primitive (Primitive[x]) with a selection into the concerning
"Add/Remove" popup menu will appear when you click on the corresponding "+/-" button.
The choice Add After is used to create a new primitive after the current one(Primitive [x + 1]).
The choice Add Before is used to create a new primitive inserted before the current one, shifting
the current one at the next position.
The choice Remove is used to remove the current primitive. Warning: you cant remove a
primitive of a single primitive list.
When you finish all yours changes then confirm and update the primitive with the "Ok" or "Apply"
button, or dismiss all with the "Cancel" button; if you apply the changes pay attention for eventual
errors occurred. The application checks if the values are not acceptable, changes eventually the
background colour of the wrong textbox and shows an Error Dialog message box.
Fig._____ 4.1.2.1.1-46 "Error Dialog" for Local Primitive Properties Editor
Another eventual error may occurs if in the Primitive selection you create a recursive declaration.
The application checks if the value of Primitive name is the same of the current primitive in use.
In that case it changes the background colour of the wrong textbox, and shows an Error Dialog
message box.
Fig._____ 4.1.2.1.1-47 "Error Dialog" for Local Primitive Properties Editor
In any case pay attention for indirect recursive declaration of primitives, because the application
doesnt check if a selected primitive contains itself the same primitive you are editing.
205678826.doc
UNCLASSIFIED
Page 118
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
4.1.2.1.2 SUB_MENU "EDIT" - "PRIMITIVE" - "GLOBAL PRIMITIVE"

For the Tabular Editor Global Primitives are those having scope within all tabular interfaces and
within contact facility too. They are included in the file raster_symbol.dsp.
For this command explanation please refer to the Par. 4.1.2.1.1
Fig._____ 4.1.2.1.2-48 "Global Primitive" Button
205678826.doc
UNCLASSIFIED
Page 119
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
4.1.2.1.3 SUB_MENU "EDIT" - "PRIMITIVE" - "PARAMETRIC PRIMITIVE"

For the Tabular Editor Parametric Primitives are those having scope within all that have their own
Motif container (standard tabular windows). They are included in the file
parametric_table_symbols.dsp.
Fig._____ 4.1.2.1.3-49 "Parametric Primitive" Button
4.1.2.1.4 SUB_MENU
"EDIT"
MULTI_PRIMITIVE"
"PRIMITIVE"
"PARAMETRIC
For the Tabular Editor Parametric Multi_Primitives are those having scope within all tables that
lay the radar canvas (Geographical Radar Picture, Secondary Radar Picture and so on). They are
included in the file parametric_table_multilist_symbols.dsp.
Fig._____ 4.1.2.1.4-50 "Parametric Multi_Primitive" Button
205678826.doc
UNCLASSIFIED
Page 120
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
4.1.2.1.5 SUB_MENU "EDIT" - "PRIMITIVE" - "ALL PRIMITIVES"

For the Tabular Editor All Primitives are those having scope within all the primitives are shown,
for this selection, independently by their subclass.
Fig._____ 4.1.2.1.5-51 "All Primitive" Button
205678826.doc
UNCLASSIFIED
Page 121
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
4.1.2.2 MENU "EDIT", ITEM " ATTRIBUTE "

Selecting the "Attribute" button a cascade-menu appears.
4.1.2.2.1 SUB_MENU "EDIT" - "ATTRIBUTE" - "LOCAL ATTRIBUTES"

For the Tabular Editor Local Attributes are those having scope within the specific interface/table.
The figure shown below represents the command list of the sub-menu "Attribute".
Clicking on the "Local Attribute" button:
Fig._____ 4.1.2.2.1-52 "Local Attribute" Button
An "Attribute Selection" box will appear, if some "Local Attributes" exists:
Fig._____ 4.1.2.2.1-53 Selection Item In Attribute Box
Choose the desired attribute, and click on the "Ok" button to confirm; to do the same thing, you can
use a double click on the desired item.
Automatically, the relative Properties Editor ("BG_EMERGENCY ") appears on the screen and you
can see and change the contained information.
205678826.doc
UNCLASSIFIED
Page 122
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig._____ 4.1.2.2.1-54 Attribute (BG_EMERGENCY) Properties Editor
In order to change the value of "Color Name" you must select an item into the "Color Selection"
panel that will appear clicking on the corresponding ">>" button. You can see a little preview of the
selected item in the bottom area of the window.
Also to change the value of "Style Name" you must select an item into the "Style Selection" panel
that will appear clicking on the corresponding ">>" button. You can see a little preview of the
selected item in the bottom area of the window.
Confirm and update changes with the "Ok" or Apply button, or dismiss all with the "Cancel"
button.
4.1.2.2.2 SUB_MENU "EDIT" - "ATTRIBUTE" - "GLOBAL ATTRIBUTE"

For the Tabular Editor Global Attributes are those having scope within all tabular interfaces.
They are included in the file global_table_attribute.dsp.
Fig._____ 4.1.2.2.2-55 "Global Attribute" Button
205678826.doc
UNCLASSIFIED
Page 123
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
4.1.2.2.3 SUB_MENU "EDIT" - "ATTRIBUTE" - "PARAMETRIC ATTRIBUTE"

For the Tabular Editor Parametric Attributes are those having scope within all tabular interfaces
that have their own Motif container (standard tabular windows). They are included in the file
parametric_table_attributes.dsp.
Fig._____ 4.1.2.2.3-56 "Parametric Attribute" Button
205678826.doc
UNCLASSIFIED
Page 124
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
4.1.2.2.4 SUB_MENU "EDIT" - "ATTRIBUTE" - "ALL ATTRIBUTES"

For the Tabular Editor All Attributes are all the defined attributes, independently by their
subclass.
Fig._____ 4.1.2.2.4-57 "All Attribute" Button
4.1.2.3 MENU "EDIT", ITEM "TEMPLATE"

Selecting the "Template" button the list of templates will appear on the screen.
The selection-box "Template Selection" will appear on the screen.
Fig.____ 4.1.2.3-28 Selection Item In Template Box
Choose the desired attribute, and click on the "Ok" button to confirm; to do the same thing, you can
use a double click on the desired item.
Automatically, the relative Properties Editor ("ESB_ARR_ACT_TEMPLATE") appears on the
screen and you can see and change the contained information.
205678826.doc
UNCLASSIFIED
Page 125
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig.____ 4.1.2.3-29 Template (ESB_ARR_ACT_TEMPLATE) Properties Editor
Confirm and update the template with "Ok" or "Apply" button, or dismiss with "Cancel" button.
4.1.2.4 MENU "EDIT", ITEM "INCLUDE_FILES"

Selecting the "Include_files" button the Include Section Editor window will appear on the screen.
Fig.____ 4.1.2.4-30 Include Section Editor Shell
Edit or add the desired include, and click on the "Ok" or Apply button to confirm, that allows to
check the syntax before to save.
After the changes and the check, clicking on the "File" button the menu will appear. Selecting the
"Save" button the fileSelectionBox will appear.
This window automatically allows to save the lists.dsp file, select the file and confirm by clicking
on the "Ok" button.
205678826.doc
UNCLASSIFIED
Page 126
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig.____ 4.1.2.4-31 "Save" Button in the Editor Shell
In the File menu there is even the Load option in order to load another file in place of
lists.dsp.
If you want to search a particular string in the file, click on the "Edit" button and then on the
"Search" button; a dialog shell will appear on the screen.
Insert a string to search in the "String Input" field, and press the "Forward" or "Backward" button
depending on the search direction desired. For a better explanation of the menu functionality see an
example in the par.4.1.6.1 MENU "BROWSER", ITEM "EDITOR", that use the same menus.
4.1.2.5 MENU "EDIT", ITEM "GENERAL_VARIABLES"

Selecting the "General_variables" button the General Variables Editor window will appear on the
screen.
Fig.____ 4.1.2.5-32 General Variables Editor Shell
Edit or add the desired variable, and click on the Apply button to confirm, that allows checking
the syntax and confirm the changes. The Close button withdraws the editing. The Ok button
executes an Apply and a Close command, closing the editor.
Clicking on the "File" button a menu will appear: selecting the "Save" button a fileSelectionBox
will pop-up.
This file selection window allows saving the general_variables.dsp file with a different file name
or in another directory. Select the file and confirm, clicking on the "Ok" button.
205678826.doc
UNCLASSIFIED
Page 127
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
In the File menu there is even the Load option, in order to load syntax from a file external to
the project, so including a new syntax to the project itself.
"Search" button: a dialog shell will appear on the screen.
depending on the desired search direction. For a better explanation of the menu functionality see an
example in the par.4.1.6.1 MENU "BROWSER", ITEM "EDITOR", that make use of the same
menus.
205678826.doc
UNCLASSIFIED
Page 128
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
4.1.3
D
28/02/2003
MENU OPTIONS
Clicking on the "Options" button a menu will appear.
Fig.__ 4.1-27 IES Tabular "Options" Menu Button
4.1.3.1 MENU "OPTIONS" - ITEM "VIEW NAME FIELDS"

Clicking on the "View Name Fields" toggle button, the fields of the table tree actually shown will
be represented only with name, or with name and class.
Fig.____ 4.1.3.1-34 "View Name Fields" Button
Below is shown the button' s layout when pressed.
Fig.____ 4.1.3.1-35 IES Tabular Changed Button Layout
For example, below is shown the tree representation with only the fields' name. Using this
functionality you can have a wide view of the current tree representation, so you con easily found a
node.
205678826.doc
UNCLASSIFIED
Page 129
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig.____ 4.1.3.1-36 Tree Layout With Fields Name Only
205678826.doc
UNCLASSIFIED
Page 130
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
4.1.4
D
28/02/2003
MENU "CREATE"
Clicking on the "Create" button a pull-down menu will appear.
Fig.__ 4.1-28 IES Tabular "Create" Menu Button
4.1.4.1 MENU "CREATE", ITEM "NEW PRIMITIVE"

Creating a primitive, like polyline or rectangle, we cant see any graphical change, but the
primitives are used by symbol fields, that refers a primitive and shows it in a defined position.
Selecting the "New Primitive" cascade button a relative cascade menu appear.
Fig.____ 4.1.4.1-37 "New Primitive" Cascade Button
4.1.4.1.1 SUB MENU "CREATE" - "NEW PRIMITIVE" - "RECTANGLE"

The figure shown below represents the command list of the sub-menu "New Primitive".
Clicking on the "Rectangle" button:
Fig._____ 4.1.4.1.1-58 "Rectangle" Button
A new shell will appear on the screen, that you must use to insert the name of the new primitive.
Fig._____ 4.1.4.1.1-59 New Primitive Name Shell
205678826.doc
UNCLASSIFIED
Page 131
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Then, the Properties Editor for "RECT_PRIM_1" will appear on the screen and you can see and
change the contained information.
Fig._____ 4.1.4.1.1-60 Properties Editor Of The New Primitive "RECT_PRIM_1"
You can confirm clicking on the "Ok" or "Apply" button, or dismiss with the "Cancel" button.
4.1.4.1.2 SUB MENU "CREATE" - "NEW PRIMITIVE" - "POLYLINE"

Fig._____ 4.1.4.1.2-61 "Polyline" Button
4.1.4.1.3 SUB MENU "CREATE" - "NEW PRIMITIVE" - "LIST OF PRIMITIVE"

Fig._____ 4.1.4.1.3-62 "List of Primitive" Button
205678826.doc
UNCLASSIFIED
Page 132
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
4.1.4.2 MENU "CREATE", ITEM "NEW ATTRIBUTE"

Selecting the "New Attribute" cascade-button a cascade menu will appear.
Fig.____ 4.1.4.2-38 "New Attribute" Cascade Button
4.1.4.2.1 SUB MENU "NEW ATTRIBUTE", ITEM "TEXT ATTRIBUTE"

The figure shown below represents the command list of the sub-menu "New Attribute".
Clicking on the "Text Attribute" button:
Fig._____ 4.1.4.2.1-63 "Text Attribute" Button

A new shell will appear on the screen, that you must use to insert the name of the new attribute.
Fig._____ 4.1.4.2.1-64 New Text Attribute Name Shell
The Properties Editor for "NEW_TEXT_ATTR_1" will appear on the screen and you can see and
change the contained information
205678826.doc
UNCLASSIFIED
Page 133
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig._____ 4.1.4.2.1-65 Properties Editor Of New Text Attribute (NEW_TEXT_ATTR_1)
4.1.4.2.2 SUB MENU "NEW ATTRIBUTE", ITEM "SYMBOL ATTRIBUTE"

Fig._____ 4.1.4.2.2-66 "Symbol Attribute" Button
205678826.doc
UNCLASSIFIED
Page 134
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
4.1.4.3 MENU "CREATE", ITEM "NEW TEMPLATE"

Click on the "New Template" cascade button: a cascade menu will appear.
Fig.____ 4.1.4.3-39 "New Template" Cascade Button
4.1.4.3.1 SUB MENU "CREATE" - "NEW TEMPLATE" - "TABLE TEMPLATE"

The figure shown below represents the command list of the sub-menu "NewTemplate".
Click on "TableTemplate" button.
Fig._____ 4.1.4.3.1-67 "TableTemplate" Button
A new shell will appear on the screen, that you must use to insert the name of the new template.
Fig._____ 4.1.4.3.1-68 New TableTemplate Name Shell
The Properties Editor "NEW_T_TEMPLATE_1" will appear on the screen and you can see and
change the contained information.
205678826.doc
UNCLASSIFIED
Page 135
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig._____ 4.1.4.3.1-69 Properties Editor of New TableTemplate "NEW_T_TEMPLATE_1"
You can confirm clicking on the "Ok" or "Apply" button. Remember that if you don't modify any
field of the properties editor, you will not obtain its creation. Making no change to the default
values just after creation is intended as an abort of the template creation. You can also dismiss
pressing the "Cancel" button.
Pay attention: you must execute the following actions, having created a new template (otherwise an
inconsistency declaration error shall abort any following reload).
1. - At first, define the name of the new template in the file "list_configuration.h" (system "include"
directory) following all other template declarations (using the Browse->Lists Configuration
facility, see par.4.1.6.4 MENU "BROWSER", ITEM "LISTS CONFIGURATION" ).
For instance:
#define ESB_MAXIMIZE_TEMPLATE 8
#define NEW_T_TEMPLATE_1
9
2. - Then, using the "Templates" radio-button, select the just created template, and modify some
fields visibility (named "default_status": set, at least, one text or symbol field to "On" or "Off", as
needed). You might also change a text or symbol field position. What is very important to keep in
mind, is that templates exist to allow contemporary changes to many fields visibility or position. So
it is semantically wrong to create templates without relating them to a set of field resources
change.
205678826.doc
UNCLASSIFIED
Page 136
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
4.1.4.3.2 SUB MENU "CREATE" - "NEW TEMPLATE" - "ENTRY TEMPLATE"

Fig._____ 4.1.4.3.2-70 "EntryTemplate" Button
4.1.4.3.3 SUB MENU "CREATE" - "NEW TEMPLATE" - "ENTRY STATE"

Fig._____ 4.1.4.3.3-71 "EntryState" Button
205678826.doc
UNCLASSIFIED
Page 137
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
4.1.5
D
28/02/2003
MENU "SEL_TABLE"
Clicking on the "Sel_Table" button a menu will appear.
Fig.__ 4.1-29 IES Tabular "Sel_Table" Menu Button
4.1.5.1 MENU "SEL_TABLE", ITEM "SELECT"

If working with a multiple table tabular component, clicking on the "Select" button, a selection-box
will appear on the screen.
The selection-box contains the list of a particular group of tables.
Fig.____ 4.1.5.1-40 Selection Item In Single Table Box
Choose the interested table and click the "Ok" button to confirm, or use a double click on the
selected item.
The selected table "mlb_list" will be presented on the screen.
205678826.doc
UNCLASSIFIED
Page 138
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
4.1.6
D
28/02/2003
MENU "BROWSER"
Clicking on the "Browser" button a menu will appear.
Fig.__ 4.1-30 IES Tabular "Browser" Button
4.1.6.1 MENU "BROWSER", ITEM "EDITOR"

Clicking on the "Editor" button a text editor will appear.
The IES TextEditor is shown below:
Fig.____ 4.1.6.1-41 Text Editor Shell Empty
Clicking on the "File" button the menu will appear. Selecting the "Load" button the
fileSelectionBox will appear.
Fig.____ 4.1.6.1-42 "Load" Button in the Text Editor Shell
205678826.doc
UNCLASSIFIED
Page 139
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig.____ 4.1.6.1-43 Selecting a File on the File Selection Box
Select the file and confirm clicking on the "Ok" button.

depending on the search direction desired.
Fig.____ 4.1.6.1-44 Search Shell
For instance, if you search the word "fldi", in order to see the current "fldi" table syntactical
definition, you will see the following text in the "Text Editor" window:
205678826.doc
UNCLASSIFIED
Page 140
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig.____ 4.1.6.1-45 "Text Editor" Window With "fldi" Table Syntactical Definition
In the Edit menu there is even the Clear option in order to have an empty editor.
Clicking on the "File->Save" button a dialog window (save dialog) will appear; you can update the
same file, clicking on "Ok" button, or change the path and/or filename writing it in the "Save File"
field.
The "save dialog" shell looks like the following:
205678826.doc
UNCLASSIFIED
Page 141
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig.____ 4.1.6.1-46 Save Shell
4.1.6.1.1 Using The Text Editor Facility Starting From A Properties Editor
Calling the text editor from a properties editor using the correlated "" (start Text Editor) button,
you can edit or add a text in the desired textbox. To make a correct use of this facility you have to
edit the text, press the "Apply" button of the Text Editor window, and then press the "Apply"
button of the Properties Editor, in order to verify the modified text syntax.
Using the TextEditor from the main menu there isnt enabled the OK and Apply buttons.
Please, changing the Text Editor syntax, press at first the Apply button, followed by the
Properties Editor Apply button press. This in order to check the changes. If you press directly,
the Text Editor Ok button, without having checked the syntax, re-opening the Text Editor
you should see again the original data-base syntax.
4.1.6.2 MENU "BROWSER", ITEM "LOG WINDOW"

Clicking on the "Log Window" button a text editor will appear. Containing a trace of the run xterm window.
The following picture shows an example.
205678826.doc
UNCLASSIFIED
Page 142
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig.____ 4.1.6.2-47 Log Window Text Editor
205678826.doc
UNCLASSIFIED
Page 143
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
4.1.6.3 MENU "BROWSER", ITEM "LISTS"

Clicking on the "Lists" button a text editor will appear, containing the lists.dsp file loaded.
The IES List Editor is shown below :
Fig.____ 4.1.6.3-48 List Editor Shell
on the "Ok" button.
205678826.doc
UNCLASSIFIED
Page 144
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig.____ 4.1.6.3-50 File Selection Box For "lists.dsp" Shell
lists.dsp.
4.1.6.4 MENU "BROWSER", ITEM "LISTS CONFIGURATION"

Clicking on the "Lists Configuration" button a text editor will appear.
The IES List Configuration Editor is shown below:
205678826.doc
UNCLASSIFIED
Page 145
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig.____ 4.1.6.4-51 List Configuration Editor Shell
on the "Ok" button.
lists.dsp.
205678826.doc
UNCLASSIFIED
Page 146
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
205678826.doc
UNCLASSIFIED
Page 147
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
4.1.7
D
28/02/2003
MENU "REMOVE"
Clicking on the "Remove" button, a single command appears.
Fig.__ 4.1-31 "Remove" Button
4.1.7.1 MENU "REMOVE", ITEM "TEMPLATE"

Clicking on the "Template" button, a selection box will appear on the screen (RemoveTemplate
Selection).
The items shown in the list are the same shown in the selection box "Template Selection" (see the
Par. 4.3.2 TEMPLATES RADIO BUTTON)
You can remove the template selecting an item in the list and confirm clicking with the "Ok"
button, or with double mouse click, a IES Warning Box will appear, then you can confirm the
operation with the OK button or dismiss with the Cancel button.
For instance, removing the MAXIMIZE_TEMPLATE you will see the following windows:
Fig.____ 4.1.7.1-53 Selection Item In Remove Template Box
205678826.doc
UNCLASSIFIED
Page 148
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig.____ 4.1.7.1-54 IES Warning Box For Remove Template
Warning: removing a template is one of the most delicate actions. The user should operate it very
carefully, as the whole template declaration would be lost. A table template is similar to contact
facility classes template. Comparing with it, the "REMOVE" "TEMPLATE" action, is similar to
removing the "CONTROLLED" track class.
4.1.8
MENU "PAPER STRIP"
Clicking on the "Paper Strip" button a pull-down menu will appear.
Fig.___ 4.1.8-15 "Paper Strip" Menu
For a better explanation of the Paper Strip Management see the following chapter 5 PAPER STRIP
CUSTOMIZATION.
205678826.doc
UNCLASSIFIED
Page 149
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
4.2
D
28/02/2003
POP-UP MENUS
The Tabular "pop-up menus" are activated clicking on specific objects of the editor with the right
mouse button. This type of menu is accessible through object nodes contained in the tree
representation, or trough objects represented in the blackboard area (for the identification of objects
please refer to the par. 3.2.1).
This menu appears as a list of commands, enabled depending on the object you clicked on. So, in
order to execute a command, follow these operations: select an item on the screen, with the right
mouse button, keep the button pressed and release it when you have highlighted the interesting
option. The execution of the corresponding command will start, or a cascade menu will be
activated.
If you work in different situations, the pop-up menu commands might be differently enabled too.
The Tabular pop-up menu looks like the following:
Fig.__ 4.2-32 IES Tabular Pop-up Menu For "Fldi" Table
4.2.1
POP-UP MENU, ITEM "PROPERTIES EDITOR"
Clicking on the "Properties Editor" Tabular pop-up menu button you can see a resource
representation of the item selected. Meanwhile you will see highlighted the correspondent item in
the blackboard area.
For instance you may apply the "Properties Editor" command to the "DEFAULT_GRID (Grid)"
item in the "fldi" interface. After the right button release, you will see the properties of the
"DEFAULT_GRID (Grid)", as in the following image:
205678826.doc
UNCLASSIFIED
Page 150
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig.___ 4.2.1-16 IES Tabular "DEFAULT_GRID (Grid)" Properties Editor
4.2.2
POP-UP MENU, ITEM "ADD LIST"
The Add List command of the pop-up menu allows adding the table list node, if it isn't already
existent. The table list node can have children of type "Entry Grid" only. They are manager objects
that allow the positioning of text and symbol fields. You can add a list exclusively to a table node.
In all the other cases you will find this command unavailable.
Clicking on the "Add List" button, if the list node already exists an "Error Dialog" will appear, as
shown in the following picture; otherwise you will see the new "LIST (List)" node appearing as a
child of the table node.
Fig.___ 4.2.2-17 IES Tabular "Error Dialog" For Existent List Node
205678826.doc
UNCLASSIFIED
Page 151
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
4.2.3
D
28/02/2003
POP-UP MENU, ITEM "ADD GRID"
The Add Grid command of the pop-up menu is used to add a new manager that provides the
positioning of elementary table objects as "TextField" and "SymbolField". For this reason you can
add a grid exclusively to the table item. In all the other cases you will find this command
unavailable.
Clicking on the "Add Grid" button, a dialog shell will appear, asking a name for the new grid. You
can define the name for the grid and confirm with the "OK" button, or dismiss with the "Cancel"
button. When you confirm the creation, you will see the new node as a child of the selected item,
and a new properties editor for the grid will appear, set with default values. In order to see the grid
structure, selecting a grid node with the left mouse button you will see a graphical representation of
the grid in the blackboard area, and the node will be highlighted.
For a complete instance of grids creation, follow these steps: creating a new table named
"TEST_TABLE" (for instruction about the "New" item of "File" menu please refer on Par. 4.1.1.2),
you will see the new table window and the correspondent "TEST_TABLE (Table)" node at the top
level.
Selecting the "TEST_TABLE (Table)" node, you can use the Add Grid command to add a "Grid"
named "TEST_GRID", while the correspondent Properties Editor will appear. You can change
some of the properties of the grid, for a logical grid creation; then you can see the following
situation:
Fig.___ 4.2.3-18 IES Tabular New Grid TEST_GRID And The Correspondent Properties Editor
205678826.doc
UNCLASSIFIED
Page 152
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
For a more exhaustive explanation about the grid properties editor, please refer to the Par. 3.4
4.2.4
POP-UP MENU, ITEM "ADD TEXT"
This command is used to create a new text child field under the selected node. It can be applied
exclusively at a grid item, used for field positioning. Using this command with an "EntryGrid"
node, you can create an "EntryTextField" node.
Clicking on the "Add Text" button, a new dialog will appear, asking a name for the new field. The
application expects, in the text box appeared, a typed name to assign it at the new text field
requested. To confirm the name for the new field, press the "OK" button, or "Cancel" to dismiss.
At the confirmation you will see the new item, with the assigned name, on the lower branch of the
possible branches of the source grid node. Meanwhile the properties editor of the new text field will
appear, set with default resource values. Then you can manage the resources and confirm with the
"OK" or "APPLY" buttons, or dismiss with the "CLOSE" button.
Warning: If you assign an already existent name at the new field, the application will show you an
"Error Dialog" window.
For instance, follow the steps in the previous paragraph (Par. 4.2.3) to create a new table with a new
grid, then click on the "TEST_GRID (Grid)" node with the right mouse button and choose the "Add
Text" command. Define its name as "TEST_TEXT", in the dialog window, and press the "OK"
button. The correspondent properties editor will appear. You can type the "Example TEXT" in the
"default_string" field, select an attribute for the "attribute_name" field (for example
"A_TITLE_TEXT"), and then click on the "APPLY" button to see the following situation:
205678826.doc
UNCLASSIFIED
Page 153
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig.___ 4.2.4-19 IES Tabular New Field Text TEST_TEXT With Correspondent Properties Editor
For a more exhaustive explanation about the text field properties editor, please refer to the Par.
3.4.1.
In any case, for a further example, after the creation, you are able to change again some resources of
the text field. For instance if you change the "position_x", "position_y" and "attribute_name"
resources to a new row/column position and to a new attribute "A_TEXT". Clicking on the
"APPLY" button, you can see the new following situation:
205678826.doc
UNCLASSIFIED
Page 154
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig.___ 4.2.4-20 Field Text TEST_TEXT With Correspondent Properties Editor In A New Position
To verify the row-column position, referred to the parent grid, click on it in the tree representation.
4.2.5
POP-UP MENU, ITEM "ADD SYMBOL"
This command is used to create a new symbol child field under the selected node. It can be applied
exclusively at a grid item, used for field positioning. Using this command with an "EntryGrid", you
can create an "EntrySymbolField" node.
Clicking on the "Add Symbol" button, a new dialog will appear, asking a name for the new field.
The application expects, in the text box appeared, a typed name to assign it at the new symbol field
requested. To confirm the name for the new field, press the "OK" button, or "Cancel" to dismiss.
At the confirmation you will see the new item, with the assigned name, on the lower branch of the
possible branches of the source grid node. Meanwhile the properties editor of the new symbol field
will appear, set with default resource values. Then you can change the properties and confirm with
the "OK" or "APPLY" buttons or dismiss with the "CLOSE" button.
For a more exhaustive explanation about the symbol field properties editor, please refer to the Par.
3.4.1.
Warning: If you assign an already existent name at the new field, the application will show you an
"Error Dialog" window.
205678826.doc
UNCLASSIFIED
Page 155
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
4.2.6
D
28/02/2003
POP-UP MENU, ITEM "ADD ENTRYGRID"
The Add EntryGrid command of the pop-up menu is used to add a new manager that provides the
positioning of elementary list entry fields, as "EntryTextField" and "EntrySymbolField". For this
reason you can add a grid exclusively to the list item. In all the other cases you will find this
command unavailable.
Clicking on the "Add EntryGrid" button, a dialog shell will appear, asking a name for the new grid.
You can define the name for the EntryGrid and confirm with the "OK" button, or dismiss with the
"Cancel" button. When you confirm the creation, you will see the new node as a child of the
selected item (the "list" node), and a new properties editor for the EntryGrid will appear, set with
default values. In order to see the grid structure, selecting a grid node with the left mouse button
you will see a graphical representation of the grid in the blackboard area, and the node will be
highlighted.
For a more exhaustive explanation about the entry grid properties editor, please refer to the Par. 3.4
4.2.7
POP-UP MENU, ITEM "DUPLICATE"
Clicking on the "Duplicate" button you can make a clone of the selected item. You can apply this
command, obviously, only to text or symbol fields.
When you use this command, the application ask you a new name to assign at the new the item and
shows the following insert shell.
Fig.___ 4.2.7-21 "IES Tabular new insert" Shell
The new duplicated field is naturally derived from the origin one, then with the same resources.
For instance if you duplicate the "TEST_TEXT (Text Field)" under the "TEST_GRID (Grid)", (see
example in the Par. 4.2.4), you can duplicate it and create the new text field node named
"TEST_TABLE_DUPLICATE_FIELD_000 (Text Field)", on the lower branch of the possible
branches of the source grid node. After the duplication you will see the tree representation area as in
the following image:
205678826.doc
UNCLASSIFIED
Page 156
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig.___ 4.2.7-22 New Duplicated Field Text TEST_TABLE_DUPLICATE_FIELD_000
4.2.8
POP-UP MENU, ITEM "REMOVE"
This command is used to delete the selected node, with all the sub-nodes of the current item.
For instance, if you use the Remove command on the TEST_GRID (Grid) manager, used in
previous example (see the Par. 4.2.3), then you will remove also its child,
"TEST_TABLE_DUPLICATE_FIELD_000 (Text Field)".
4.2.9
POP-UP MENU, ITEM "COPY "
This command is used to store information about the selected node, with all the concerning tree
sub-nodes, in order to apply a future paste (Attach) operation (see the Par. 4.2.11).
If you use the Copy command on a node, you wont see any particular graphical behaviour.
Then you will be able to execute an Attach command, obtaining a copy, automatically renamed,
of the node (and all its children). This Attach operation might be After, Before or Under
another node. The Attach operation follows a destinatary node consistency check.
After the Copy operation, and before the Attach, you can also load another table component
or create a new one. All the information about the copied node are stored by the tool until an Exit
or a valid Attach command; and, obviously, until another Copy or Move command. It is
allowed to copy nodes, and all their children, from a table component to another, keeping up all the
concerning local information of the source table (i.e. local primitives and attributes).
4.2.10 POP-UP MENU, ITEM "MOVE "

This command, similar to Copy command, allows to store information about the selected
node, with all the concerning tree sub-nodes, in order to apply a future paste (Attach) operation
and a subsequently remove operation of the source sub-tree (see the Par. 4.2.11).
If you select the Move command on a node, you wont see any particular graphical behaviour.
Then you will be able to Attach the node (and all its child). This Attach operation might be
After, Before or Under another node. The Attach operation follows a destinatary node
consistency check.
205678826.doc
UNCLASSIFIED
Page 157
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
After the Move operation, and before the Attach, you can also load another table component
or create a new one. All the information about the copied node are stored by the tool until an Exit
or a valid Attach command; and, obviously, until another Copy or Move command. It is
allowed copying nodes, and all their children, from a table component to another, keeping up all the
concerning local information of the source table (i.e. local primitives and attributes).
Pay Attention: when loading another component after a Move operation the application will
advise you, with the following IES Warning Box.
Fig.___ 4.2.10-23 IES Warning Box
Pressing the Continue button, and loading or creating a different component, the application shall
automatically remove the selected for move node from the origin table and automatically save the
correspondent table project file. In order to recover a previous version of the table component,
please refer to the paragraph concerning backup operations (par. 4.1.1.3.1). Pressing the Reset
button on the Warning Box, the Move action (and consequent Attach operation) will
be aborted. The Attach operation will result already executable. The same situation will
happen pressing the Continue button on the Warning Box, but selecting the same table on the
Selection Box that will appear for the Load action.
4.2.11 POP-UP MENU, ITEMS "ATTACH BEFORE", "ATTACH AFTER",

"ATTACH UNDER"
Before using these commands you must have already executed a Copy or a Move
operation, even from another tabular component (see previous par. 4.2.9 ,4.2.10). Otherwise the
application will notify you an error with the following Error Dialog.
Fig.___ 4.2.11-24 Nothing To Reposition Error Dialog
205678826.doc
UNCLASSIFIED
Page 158
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
These commands are used to choose a new tree position for a previously moved node, or for a
clone of a previous copied node, always with all its children.
The behaviour of the Attach commands depends on the previous command.
In case of a previous Copy operation, the source node is unchanged, but a new one, with the
same characteristics, is created on the new chosen tree position. The application assigns a new
name to each item of the duplicated sub-tree. The new name is generated automatically by the
application, using the source node name and a global incremental number. When the Attach
operation takes place between different tabular components, referred resources are migrated too
(primitives and attributes)
In case of a previous Move operation, the source node is removed from the original tree
position and re-created on the new selected one.
Using the Attach After and Attach Before commands on a node, will cause the reposition of the
source node, or of the renamed clone, as a brother of the selected node, obviously after or before the
destination node respectively. Using the Attach Under command the application attaches the
renamed clone, or the moved node, as the last child of the selected node.
There's still a chance to make a wrong reposition, but the application would notify you the mistake
with an Error Dialog like the following. For instance you cant reposition a node under another
node of the same category (for example a Grid node under another Grid node), or a TextField
as a brother of an EntryTextField node.
Fig.___ 4.2.11-25 Wrong Reposition Error Dialog
205678826.doc
UNCLASSIFIED
Page 159
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
4.3
D
28/02/2003
USING THE RADIO BUTTONS
At the top of the tree representation area you can find two radio buttons, working on "radio always
one" mode. They allow to define the working method, that is building the structure of the table, or
modifying the table templates.
Fig.__ 4.3-33 IES Tabular Radio Buttons
4.3.1
STRUCTURE RADIO BUTTON
Clicking the Structure button you can change the table structure, (it is the default start mode).
Then you are able to add, duplicate or remove, grids, fields or list, and change the properties of the
each objects of the current table.
All the commands you have seen in the pop-up menu usage description are available in the
Structure" mode.
4.3.2
TEMPLATES RADIO BUTTON
Using the Templates button you can choose a different template, for the current table, to work on.
So you are able to see only some functionality of the single objects in the current table.
Clicking on the Templates radio button, the "Template Selection" window will appear, if some
template exist for the current table. Then you can choose one of the existent template
representations, as the current working one.
205678826.doc
UNCLASSIFIED
Page 160
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig.___ 4.3.2-26 IES Tabular "Template Selection" Window
For a more exhaustive explanation about the template usage, please refer to the Par. 3.7
4.3.3
CHECK GEOMETRY TOGGLE BUTTON
Clicking the Check Graphic Context button you pop-up/pop-down a Log Window, (not visible at
start-up). Then you are able to see if the position and dimension properties of each object of the
current table are coherent with the belonging section of table.
All notifications regarding the geometrical coherence are refreshed applying any modification on
table components or resources.
Fig.___ 4.3.3-27 Log Window For Check Geometry In A Correct Situation

205678826.doc
UNCLASSIFIED
Page 161
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
In the following two pictures you can see an example of a wrong repositioning of a header field that
overlaps the entries area (the virtual lens, in Fig.___ 4.3.3 -28 A Section Of The FLDI Table
With Components Overlap On The BlackBoard, shows the error position).
Fig.___ 4.3.3-28 A Section Of The FLDI Table With Components Overlap On The BlackBoard
Fig.___ 4.3.3-29 Log Window For Check Geometry In A Wrong Situation
205678826.doc
UNCLASSIFIED
Page 162
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
PAPER STRIP CUSTOMIZATION
The Paper Strip Management allows an additional usage of the I.E.S. Tabular tool. Entering this
modality its possible to define new paper strip templates, even containing pseudo-graphic
sections. These templates will be sent to the FDM CSCI, in order to initialise its internal
configuration at start-up. FDM CSCI will interface the IES CSCI when included in the Off-line
Configuration Position. FDM CSCI controls the Strip Printer Unit.
The Tabular Editor must be used on two distinct states:
Electronic Tables Customization state
Paper Strip Customization state
Most of the customisation capabilities allowed on Electronic Tables Customisation state shall be
disabled when working on Paper Strip Customisation state.
On the other hand, some specific Paper Strip Customisation state resources and facilities shall be
disabled when the Tabular Editor will be in Electronic Tables Customisation state.
The way to switch the editor functionalities/states is using the Paper Strip menu.
5.1
SWITCHING ON "PAPER STRIP" CUSTOMIZATION STATE
Clicking the "Paper Strip" button a pull-down menu will appear.
Fig.__ 5.1-34 Disabled "Paper Strip" Menu
It contains the following menu items: Work On Paper Strip, Edit Paper Strip Grid, New
Paper Strip Template ..., Edit Paper Strip Template..., Remove Paper Strip Template ...,
Clone Paper Strip Template..., Export Electronic To Paper Strip Template..., Create Strip
Pseudo Graphic Layout , Edit Strip Pseudo Graphic Layout ..., Edit Flight States - Templates
Matrix, Print Paper Strip Template ..., Print All Paper Strip Templates, Generate Final
Configuration.
The first menu item, Work On Paper Strip, is a toggle button. The first time you are using this
menu it shall result not set. Trying to set it, if the loaded table is the New Strip Area (NSA), all
the other menu items of the Paper Strip menu shall be set sensitive. Setting the menu item Work
On Paper Strip, shall cause the IES Tabular Editor changing its status, passing from the standard
205678826.doc
UNCLASSIFIED
Page 163
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Electronic Tables Customization to the Paper Strip Customisation state. Even the NSA
representation changes on the BlackBoard (Interactive Window with graphics).
Fig.__ 5.1-35 Enabled "Paper Strip" Menu After The Switch
If you arent using the NSA table an Error Dialog will inform about the wrong operation, because
only this table allows working for the PPST customisation.
After the tool state switch you can see immediately the different representation and reposition of the
table fields. Normally the NSA is divided in a table title and an entry list part. After the switch only
the entry list part is represented.
All the electronic positions of the entry fields, referred to electronic father grids, are transposed
with respect to the standard grid dimension of a paper strip (80 x 11 cells).
In the following pictures you can see a translation the NSA :
Fig.__ 5.1-36 The NSA Table Representation In Electronic Tables Customization State
Fig.__ 5.1-37 The NSA Table Representation In Paper Strip Customization State
205678826.doc
UNCLASSIFIED
Page 164
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
5.1.1
D
28/02/2003
Entry Fields Resources In Paper Strip Customization State
When switching to Work On Paper Strip mode, the Electronic Strip Entry Configuration shall be
represented on the Black Board Preview Window, with all New Strip Area nodes related to Paper
Strip Configuration visible. The visible nodes shall be the same resulting sensitive on the Structural
Tree representation. All the visible Entry Fields shall be positioned on the unique Paper Strip Grid
(see paragraph 5.1.2 MENU "Paper Strip", ITEM "Edit Paper Strip Grid).
Only the Entry of the New Strip Area table shall be visualised on the Black Board Preview
Window: this Entry shall be positioned on the top left pixel of the window. A right mouse button
click (WB) on a visible Entry Field in the Black Board, or on the Structural Tree node, shall pop-up
a menu. This menu shall have enabled only the Properties Editor menu item. The Black Board
shall represent a Paper Strip Layout, based on a Strip Grid made of 11 rows by 80 columns. Entry
Fields shall be represented making use of a Vectorial Font.
In the following picture you can see the available resources :
Fig.___ 5.1.1-30 The ESB_CS Entry-Field Properties Editor In Paper Strip Customization State
205678826.doc
UNCLASSIFIED
Page 165
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Syntax
DERIVED FROM ELECTRONIC RESOURCES:
name:
<string>
field name: this name must be unique
within the whole tabular component
defined at creation time
(Not Editable)
type:
{ EntryTextField }
defined at creation time.
(Not Editable)
default_string: <string>
Its the initial string value used for default
visualization, on the preview representation
window (BB) of an EntryTextField. Its
also used as string for fixed ascii text fields
without reference to be drawn on a
paper strip (see 5.1.1.1
Entry Fields Used As Static Text)
default_status: {enumerated reasource : On | Off}
It defines the field visibility. Should be
set Off in the Structure declaration
phase. At the contrary the same object
default_status should be set On
in the Templates declaration phase, if
the field is to be reresented
in the template (see 5.2.2
Modifing An Existing PaperStripTemplate)
reference:
<reference_identifier>
Reference to a resource of a conceptual
object managed by a specified
ATC handler within the internal database
PAPER STRIP RESOURCES SECTION:
ppst_auto_position: { C#<non negative integer> ; R#<non negative integer> }

horizontal and vertical translated position
value obtained using the parent electronic
grid manager resources and evaluating an
expression using the default paper-strip
grid parameters (11x80)
(Not Editable)
ppst_position_x: { C#<non negative integer> |
pixel horizontal positioning value obtained
using the paper strip grid manager
resources or evaluating a numeric
205678826.doc
UNCLASSIFIED
Page 166
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
expression using other pre-assigned

parameters
ppst_position_y: { R#<non negative integer> |
pixel vertical positioning value obtained
using the paper strip grid manager
resources or evaluating a numeric
expression using other pre-assigned
parameters.
The expression is negatively signed to
obtain pixel values X-Server compatible
coordinates
ppst_truncation: <numeric positive integer>
it's the number used to truncate
an EntryTextField string when its
electronic length is greater then the
declared "ppst_truncation" value
ppst_font:
{enumerated reasource : 1x1sp | 1x2sp | 1x3sp | 2x2sp | 2x3sp | 2x4sp |
3x3sp | 3x4sp | 4x4sp }
identifier of a pre-defined set of possible
dimensions: they are evaluated and
represented using the paper strip grid
manager resources, char_width and
char_height values.
But they are fixed font resources used by
The strip printer firmware. See the
examples on next figures.
ppst_reverse: {enumerated reasource : On | Off}
It defines the field reverse, or not,
representation, it establish the print reverse
method of the strip printer firmware (see
the examples on next figures)
The reference resource is the link to the internal database, managed by a specific ATC handler.
Its used also as a link to the FDM CSCI in order to define the field of the ATC conceptual object to
be printed.
The resource ppst_automatic_position is automatically computed on the first Electronic/Paper
switch. It shall be the result of an automatic translation of the Entry Field Electronic position to the
Paper Strip position, considering Paper Strip dimension. This resource shall be unchangeable by
operator.
The operator shall be enabled changing the expressions contained in the text fields of the resources
ppst_position_x and ppst_position_y. If these last two resources will be set or changed by
operator, their resulting values shall overcome the automatic position. This shall happen also if
these two resources will be set working on a Paper Strip Template. In this last case, Paper Strip
Template position values shall overcome also eventually set Paper Strip Structure position values,
or Paper Strip Structure automatically translated positions (see par. 5.2 PAPER STRIP
TEMPLATES).
Use the ppst_automatic_position resource as reference to return to the electronic position
translation.
205678826.doc
UNCLASSIFIED
Page 167
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
The resource ppst_font shall appear as a choice allowing to select a value of 9, that are 1x1sp,
1x2sp, 1x3sp, 2x2sp, 2x3sp, 2x4sp, 3x3sp, 3x4sp, 4x4sp.
Fig.___ 5.1.1-31 The Entry-Field ppst_font Resource Choice
This resource is used to choose one of the pre-defined font attributes of the field, to be used in the
Black Board and by the strip printer. The font dimensions are multiple of the single cell dimension
(1x1sp font size) of the paper strip grid.
The resource ppst_reverse shall appear as a boolean choice; when set true, the Entry Field shall
be printed and represented in reverse.
The resource ppst_truncation, when undefined, or set to 0, shall mean that no field string
truncation is requested to the FDM CSCI. Otherwise, a value greater than 0 shall indicate the
character position where FDM CSCI shall execute the related field string clipping. When one of
these resources is set in the Properties Editor of an Entry Field of the table Structure, the same
resource value shall be present also in the Properties Editor of the same Entry Field of every Paper
Strip Template.
The following pictures explain better the modifications effects of the resources :
Fig.___ 5.1.1-32 A Section Of The BlackBoard with ESB_CS Field With Default Resources Values
205678826.doc
UNCLASSIFIED
Page 168
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig.___ 5.1.1-33 A Section Of The BlackBoard with ESB_CS Field With 2x3sp Value For the
ppst_font resource
Changing the resources as in the following picture, you shall obtain the graphic result visible on the
next picture (Fig.___ 5.1.1 -35 A Section Of The BlackBoard with ESB_CS Field With 3x4sp
Value For ppst_font, 3 For ppst_truncation and On For ppst_reverse).
Fig.___ 5.1.1-34 A Section Of The ESB_CS Field Properties Editor With Modified ResourcesValues
Fig.___ 5.1.1-35 A Section Of The BlackBoard with ESB_CS Field With 3x4sp Value For
ppst_font, 3 For ppst_truncation and On For ppst_reverse
These pictures are referred to the starting paper strip grid dimensions, set to default values. Use the
Edit Paper Strip Grid menu in order to have a better visualization (see 5.1.2MENU "Paper
Strip", ITEM "Edit Paper Strip Grid). The grid changes dont have effect on the final FDM
Configuration file.
5.1.1.1 Entry Fields Used As Static Text

Using the visible Entry Fields nodes, resulting sensitive on the Structural Tree representation, you
can use a set of fields in order to represent static text strings on the paper strip.
Fields resources are obviously the same described on the previous paragraphs, but the
default_string resource is used as a static text. In fact the field has no link to the internal database
(the reference resource is typically empty).
The STATIC_TEXT_[XX] token often identifies this kind of fields.
205678826.doc
UNCLASSIFIED
Page 169
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
5.1.2
D
28/02/2003
MENU "Paper Strip", ITEM "Edit Paper Strip Grid
Clicking on the Edit Paper Strip Grid item you can see the paper strip grid properties editor. You
can also edit the selected grid parameters, as shown in the following figure:
Fig.___ 5.1.2-36 strip_printer_grid Properties Editor
Syntax
name:
STRIP_PRINTER_GRID
grid name: this name is unique.
(Not Editable)
type:
offset_x:
offset_y:
char_width:
char_height:
205678826.doc
ENTRY_GRID
it is a static resource
{ numeric identifier | numeric integer expression }
number of horizontal pixels from the
topleft Black Board corner to the
grid origin.
{ numeric identifier | numeric integer expression }
number of vertical pixels from the top-left
Black Board corner to the grid origin.
horizontal single char spacing: its used for
field column positioning, when are used
expressions as C#<non negative integer>
UNCLASSIFIED
Page 170
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
vertical single char spacing: its used for

field row positioning, when are used
expressions as R#<non negative integer>;
the row spacing value depends also on the
interline grid resource
interline:
0
this grid resource is fixed to zero because it
isnt configurable on the strip printer.
(Not Editable)
The positioning of all fields depends on this Grid manager (STRIP_PRINTER_GRID) only if are
used positional expressions as " R#<non negative integer>" and/or "C#<non negative integer>".
The font used for the fields is a vector scalable font in order to be adaptable to grid dimensions
and/or to its font parameters (1x2, 2x2etc).
The modifications on the STRIP_PRINTER_GRID resources are used only in order to obtain a
better visualization on the preview representation window (Black Board) because dont take effect
on the FDM final configuration file. See the following pictures before and after the parameters
change from default values (char_width : 10, char_height : 10) to new values (char_width : 15,
char_height : 15):
Fig.___ 5.1.2-37 The NSA Table With Default STRIP_PRINTER_GRID Properties (char_width,
char_height)
Fig.___ 5.1.2-38 The NSA Table With Enlarged STRIP_PRINTER_GRID Properties (char_width,
char_height)
205678826.doc
UNCLASSIFIED
Page 171
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
5.2
D
28/02/2003
PAPER STRIP TEMPLATES
Using the IES Tabular Editor, normally you see and modify all the fields and resources available, in
the NSA base configuration, starting from a default situation. In order to define different subset of
fields (changing visibility and position) you must use the template class.
The PaperStripTemplate section shall be quite identical to electronic Entry Template sections.
Entry Fields visibility shall be switch-able On and Off, and their positions changeable with respect
to their Structure resources ppst_position_x and ppst_position_y. The difference shall be in the
token ppst_position that shall substitute the electronic format position, and the fact that no
other existing electronic sub-sections shall be provided : there shall be only an additional resource,
that is the name of a Pseudo Graphic Primitive, to be applied to the Paper Strip Template.
Changing the status of the IES Tabular Editor from the standard Electronic Tables Customization
to the Paper Strip Customisation state, you can utilize only the Paper Strip Templates that are a
different type of template with respect of electronic types (EntryTemplate, TableTemplate,
EntryState).
5.2.1
PaperStripTemplate Resources
The entity "template" has its own resources, which can be accessed by means of the
Paper Strip -> "Edit Paper Strip Template " from the main menu. To have an example, we can
have a look to the "PPST_TEMPLATE01" properties editor:
Fig.___ 5.2.1-39 Properties Editor For "PPST_TEMPLATE01"

Syntax
Template Name:
String resource.
The Template name is unique and not
editable after creation
Template Type: {PaperStripTemplate}
enumerated resource, fixed for this
template type
205678826.doc
UNCLASSIFIED
Page 172
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Pseudo Graphic Prim.: <PseudoGraphicPrimitive identifier>

Its the name of a Pseudo Graphic
Primitive.
Its a special type of graphic primitive.
The usage of this resource allows to
combine the template to a specific
primitive and provides the automatic
visualization of this graphical primitive
when you select the template.
(For a better explanation of
Pseudo Graphic Primitives see the
5.3 PSEUDO GRAPHIC)
5.2.2
Modifing An Existing PaperStripTemplate
At the top of the tree representation area you can find two radio buttons, working on "radio always
one" mode. They allow defining the working method, that is building the Structure of the table (in
this case the strip only), or modifying the PaperStripTemplate templates.
Fig.___ 5.2.2-40 IES Tabular Radio Buttons
Clicking the Structure button you can change the table structure, it is the default start mode.
All the commands you have seen in the pop-up menu usage description are available in the
Structure" mode.
Using the Templates button you can choose a different template, for the current table, to work on.
So youll be able to use only some functionalities of the single objects of the current table.
Clicking on the Templates radio button, the "Template Selection" window will appear, if some
template exists for the current table. Then you can choose one of the existing templates
representations, as the current working one.
205678826.doc
UNCLASSIFIED
Page 173
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig.___ 5.2.2-41 Selection Item In Template Selection Box
Passing from Structure to Template mode, youll see the following changes:
The Blackboard changes its title from NSA PPST Structure to NSA PPST
<template_name> PPST Template and shows fields eventually in different positions.
The tree representation highlights all the fields changed with respect of the standard
Structure mode.
The fields pop-up menu is reduced to the Properties Editor menu item only.
You will not be able to edit an existing template during a Template editing session (5.2.3.2
MENU "Paper Strip", ITEM "Edit Paper Strip Template ")
Fig.___ 5.2.2-42 Trying To Edit A Template During A Template Editing Session
Editing the resources of an Entry Field, by means of a properties editor panel, youll see a
reduced set of properties; youll be able to change only default_status and
ppst_position_x and y.
205678826.doc
UNCLASSIFIED
Page 174
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
These entry field resources allow defining the template layout. In fact you can select a single paper
strip template and change the visibility and position of the relevant entry fields in order to obtain a
new strip representation.
The following picture shows the entry field resources available in Template mode:
Fig.___ 5.2.2-43 Properties Editor Of An Entry Field in Template mode
After modifications to ppst_position_x or ppst_position_y, you can always restore the original
positions looking to the ppst_auto_position resource.
In order to close a Template editing session you must return to Structure mode using the
correspondent radio-button; if you want to save all changes you must return in Electronic
definition mode.If you created any template with no fields changed, youll see the following
warning.
205678826.doc
UNCLASSIFIED
Page 175
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig.___ 5.2.2-44 Warning For Template Without Fields Set
In order to create a paper strip template, clone or export it from electronic a template see the
following paragraphs about the relative menus.
205678826.doc
UNCLASSIFIED
Page 176
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
5.2.3
D
28/02/2003
Paper Strip Template Menus
5.2.3.1 MENU "Paper Strip", ITEM "New Paper Strip Template "
Clicking on the "New Paper Strip Template " button, a prompt dialog will appear on the screen,
asking for a name (Enter New Name).
Fig.____ 5.2.3.1-55 Enter New Name Box
Clicking on the "Ok" button, the properties editor of the new template will appear (For a better
explanation see 5.2.3.2 MENU "Paper Strip", ITEM "Edit Paper Strip Template ").
The Cancel button withdraws the command.
5.2.3.2 MENU "Paper Strip", ITEM "Edit Paper Strip Template "
Clicking on the "Edit Paper Strip Template " button, a selection box will appear on the screen
(Template Selection).
Fig.____ 5.2.3.2-56 Selecting An Item In The Selection Box Template

205678826.doc
UNCLASSIFIED
Page 177
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Clicking on the "Ok" button, the properties editor of the template will appear (For a better
explanation of resources see 5.2.1 PaperStripTemplate Resources). The Cancel button withdraws
the command.
5.2.3.3 MENU "Paper Strip", ITEM "Remove Paper Strip Template "
Clicking on the "Remove Paper Strip Template " button, a selection box will appear on the screen
(RemoveTemplate Selection).
You can remove a template selecting its name in the list, and confirm clicking with the "Ok"
button, or with double mouse click. A IES Warning Box shall appear: then you can confirm the
operation with the OK button or dismiss with the Cancel button.
For instance, removing the PPST_TEMPLATE01 you shall see the following windows:
Fig.____ 5.2.3.3-57 Selecting An Item In The Remove Template Selection Box
205678826.doc
UNCLASSIFIED
Page 178
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig.____ 5.2.3.3-58 IES Warning Box For Remove Template
Warning: removing a template is a delicate action. The user should operate it very carefully, as the
whole template declaration would be lost. Only the related PseudoGraphicPrimitive could be reinstanced.
5.2.3.4 MENU "Paper Strip", ITEM "Clone Paper Strip Template "
Clicking on the "Clone Paper Strip Template " button, a selection box will appear on the screen
(Template To Clone Selection) containing the list of PPST templates. If nothing happens you have
no PPST templates defined.
Fig.____ 5.2.3.4-59 Selecting An Item In The Template To Clone Selection Box
205678826.doc
UNCLASSIFIED
Page 179
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Selecting an item and clicking on the "Ok" button, a prompt dialog shall appear on the screen
asking for a new name (Clone Name for PPST_TEMPLATE01)
Fig.____ 5.2.3.4-60 Clone Name for PPST_TEMPLATE Box
Clicking the "Ok" button, the properties editor of the new template will appear (For a better
explanation of the resources see 5.2.1 PaperStripTemplate Resources).
5.2.3.5 "Paper Strip", ITEM "Export Electronic To Paper Strip Template "
Being on the Electronic Tables Customization mode, the Tabular editor allows using different
types of templates (EntryTemplate, TableTemplate, EntryState). The EntryTemplate is similar to
PaperStripTemplate.
Clicking the "Export Electronic To Paper Strip Template " button you can export an
EntryTemplate to a PaperStripTemplate. A selection box will appear on the screen (Template To
Export Selection).
Fig.____ 5.2.3.5-61 Selecting An Item In The Template To Export Selection Box
205678826.doc
UNCLASSIFIED
Page 180
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Clicking on the "Ok" or Apply button, the properties editor of the new template will appear (For a
better explanation of resources see 5.2.1 PaperStripTemplate Resources).
5.2.3.6 MENU "Paper Strip", ITEM "Edit Flight States Template Matrix"
A Flight States - Templates Matrix Properties Editor shall be accessible through this menu item
of the Paper Strip menu. The text fields, and buttons through which accessing a Selection Box,
shall allow inserting (or clearing) the name of an existing Paper Strip Template. The user shall be
forced to assign only existing Paper Strip Templates names, in correspondence to the combination
of the three flight state parameters, that are Flight Family = {ACC, APP, TWR}, Flight Position =
{DEP, ENR, ARR}, and Flight Control = {PENDING, ACTIVE}.
The Flight States - Templates Matrix Properties Editor shall be used only for a final configuration
of the FDM CSCI, in order to identify which paper strip templates shall be used for each flight
state. (see 5.4.3 MENU "Paper Strip", ITEM "Generate Final Configuration").
Fig.____ 5.2.3.6-62 Flight States Templates Matrix Properties Editor Layout
The Properties Editor contains nineteen elements; the first eighteen combinations are distributed on
two columns (PENDING, ACTIVE). The last element (EMPTY_STRIP) is used for the online
command requesting the FDM unit the print of an empty strip.
205678826.doc
UNCLASSIFIED
Page 181
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Using the corrispondent >> push button, related to the desired matrix text box, a Template
Selection box shall appear.
Fig.____ 5.2.3.6-63 Templates Selection Box From The Flight States Templates Matrix Properties
Editor
Selecting a Template and clicking on the "Ok" or Apply button, the selected template shall be
stored on the corresponding matrix position.
In order to clear an already selected PaperStripTemplate, delete it from the textbox.
The following picture shows a partial filled Flight States Templates Matrix Properties Editor:
205678826.doc
UNCLASSIFIED
Page 182
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig.____ 5.2.3.6-64 Flight States Templates Matrix Properties Editor With Some Templates Selected
205678826.doc
UNCLASSIFIED
Page 183
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
5.3
D
28/02/2003
PSEUDO GRAPHIC PRIMITIVES
Electronic templates and Structure allow defining and repositioning EntrySymbolFields that
generally make use of graphic primitives. A Pseudo Graphic Primitive is a graphic primitive used
by the strip printer in order to define paper strip separators and contour.
A Pseudo Graphic Primitive shall be edited using the BlackBoard and a Control Panel. The Control
Panel will furnish all tools needed. It works like a Properties Editor. The BlackBoard shall represent
a Paper Strip Layout based on a Strip Grid made of 11 rows by 80 columns. The Strip Grid divides
the Entry in 880 tiles.
In order to know the creation and editing method of a Pseudo Graphic Primitive read the following
two paragraphs.
5.3.1.1 MENU "Paper Strip", ITEM "Create Paper Strip Pseudo Graphic Layout"
Clicking the "Create Paper Strip Pseudo Graphic Layout" button, a dialog panel will appear on the
screen (IES New Pseudo Graphic).
Fig.____ 5.3.1.1-65 Insert Pseudo Name Box
Entering a new name and clicking the Ok button youll confirm the creation. The Cancel pushbutton withdraws the command.
The confirmation shall activate a Pseudo Graphic Editing session,and a properties editor of the
primitive shall appear.
Fig.____ 5.3.1.1-66 PSEUDO_01 Pseudo Graphic Properties Editor
205678826.doc
UNCLASSIFIED
Page 184
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
During a Pseudo Graphic Editing session, the IB mouse button shall be used as an iconic pen.
Through the Properties Editor/Control Panel, the user will be able to select a Pseudo Graphic
character out of 11 used to fill tiles, or a blank character to clear them. The resource used for this
purpose is the metacharacter choice button.
Fig.____ 5.3.1.1-67 The metacharacter Used For Pseudo Graphic Primitive Editing
Using the iconic pen, the user shall be able to fill all the desired tiles. Behind the Strip Grid and its
tiles, an 11 by 80 cells matrix shall record the type of character assigned. Use the blank selection in
order to erase previously placed metacharacters.
See the following pictures for a visual example :
Fig.____ 5.3.1.1-68 A Section Of The BlackBoard During Pseudo Graphic Primitive Editing Phase
205678826.doc
UNCLASSIFIED
Page 185
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig.____ 5.3.1.1-69 A Selected Metacharacter During The Pseudo Graphic Primitive Editing Phase
Selecting a metacharacter in the Control Panel, as in the previous picture, and clicking with the
central mouse button on a grid cell, as in the following pictures, you will place the selected
metacharacter in the selected grid cell.
Fig.____ 5.3.1.1-70 A Section Of The BlackBoard During Metacharacter Drawing
Fig.____ 5.3.1.1-71 A Section Of The BlackBoard After Metacharacter Drawing
At the end of the Pseudo Graphic Editing session, using the Apply button, the matrix behind shall
be stored to a minimized Pseudo Graphic Primitive and translated for FDM future exporting action.
In order to see the FDM translated text, knowing the strip printer firmware syntax, you can use the
button at the meta text resource row. An editor window shall appear: its contents are not
editable.
205678826.doc
UNCLASSIFIED
Page 186
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig.____ 5.3.1.1-72 The MetaText Editor Of The meta text Pseudo Resource
The strip printer firmware syntax is explained in document [5] IER 411 Manuale di
Programmazione Stampa e Controllo dei Caratteri Carlo Gavazzi Systems SpA Copyright
1992.
Using the Ok or Close button of the Control Panel you shall close the editing session. The
Pseudo Graphic Primitive can now be referenced in any template, in order to combine the
representation of text fields with graphics.
5.3.1.1.1 Linking Pseudo Graphic Primitives to Templates

The Paper Strip Template Properties Editor allows assigning a configured pseudo graphic primitive
to a template.
Fig._____ 5.3.1.1.1-72 The Paper Strip Template Properties Editor With A Referenced Pseudo Graphic
205678826.doc
UNCLASSIFIED
Page 187
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Use the >> pushbutton of the template properties editor in order to select a configured graphic
primitive for the template. A selection box, with the list of defined pseudo graphic primitives, shall
appear, if any of them exists.
Fig._____ 5.3.1.1.1-73 The Pseudo Graphic Primitive Selection Box
Clicking the Ok or Apply button of the selection box, to confirm the choice. The Ok or
Apply button of the properties editor shall link the primitive to the template. The Close button
shall withdraw the operation.
205678826.doc
UNCLASSIFIED
Page 188
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
5.3.1.2 MENU "Paper Strip", ITEM "Edit Paper Strip Pseudo Graphic Layout"
Clicking the "Edit Paper Strip Pseudo Graphic Layout" menu item, a selection box shall appear on
the screen (PseudoPrimitive Selection), if any graphical primitive has been already defined.
Fig.____ 5.3.1.2-73 The Pseudo Primitive Selection Box
Selecting an item and confirming with the Ok or Apply button youll start a new Pseudo
Graphic Editing session, and a Control Panel shall appear.
The Cancel button shall withdraw the operation.
If you are already using a template, referencing a pseudo graphic primitive, during the editing
session, the referenced primitive shall be temporally substituted.
The editing session follows the creation rules. Read the previous two paragraphs in order to know
the manual procedures (5.3.1.1 MENU "Paper Strip", ITEM "Create Paper Strip Pseudo Graphic
Layout", 5.3.1.1.1 Linking Pseudo Graphic Primitives to Template).
205678826.doc
UNCLASSIFIED
Page 189
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
5.4
D
28/02/2003
EXPORT TO FDM CSCI COMMANDS
FDM CSCI shall load the initialisation data-set generated by the IES Tabular editor. This means
that those data that will be directly sent to the strip printer shall comply with actual formats (paper
strip static graphic frame).
Compliance is guaranteed with regards to the strip printer distributed by Carlo Gavazzi Systems
Spa, model IER 512, working in emulation of the previous models IES 411 and/or IES 423.
The previous models emulation consists in using pseudo-graphic characters for paper strip
separators. More details regarding the pseudo-graphic format are described by the paragraph 5.3.1.1
MENU "Paper Strip", ITEM "Create Paper Strip Pseudo Graphic Layout".
The IES Tabular, only when the NSA table has been loaded, shall be able to generate, on menu
request, an output file (write only for IES), called fdmpers.bin. It shall be exclusively an ASCII
file. It shall contain a C-like comment at the beginning of each row of text.
This file is the only interface between the IES CSCI and the FDM CSCI.
At the end of an IES Tabular editing session, when the paper strip layouts result satisfying, the IES
Tabular shall be able to generate a final version of the file fdmpers.bin.
(for more information, read the following paragraph 5.4.3 MENU "Paper Strip", ITEM "Generate
Final Configuration").
This file will be available for distribution on all nodes providing the FDM CSCI.
To re-configure the FDM CSCI with the new paper strip customization, that CSCI should be restarted.
The operator will execute the distribution of the file fdmpers.bin, making use of standard Unix
utilities (i.e. ftp, rcp).
205678826.doc
UNCLASSIFIED
Page 190
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
5.4.1
D
28/02/2003
MENU "Paper Strip", ITEM "Print Paper Strip Template "
The Print Paper Strip Template ... menu item shall allow selecting one of the existing paper strip
templates in order to obtain a printing test on the paper strip printer, through the FDM CSCI.
Clicking on the " Print Paper Strip Template " menu item a selection box shall appear on the
screen (Template Selection), if any PaperStripTemplate exists.
Fig.___ 5.4.1-45 Template Selection Box
Clicking on the "Ok" or Apply button, having selected a template, the tool processes the
templates layout data, and generates the fdmpers.bin file, for a single template test.
A Warning Box shall appear on screen advising about the fdmpers.bin file creation path.
205678826.doc
UNCLASSIFIED
Page 191
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Fig.___ 5.4.1-46 IES Warning Box For fdmpers.bin File Creation
5.4.2
MENU "Paper Strip", ITEM "Print All Paper Strip Templates"
The Print All Paper Strip Templates menu item shall activate the generation of the fdmpers.bin
in order to obtain a printing test on the paper strip printer, through the FDM CSCI, for all defined
templates.
A Warning Box shall appear on the screen advising about the fdmpers.bin file creation path.
5.4.3
MENU "Paper Strip", ITEM "Generate Final Configuration"
The Generate Final Configuration menu item shall activate the generation of the fdmpers.bin
for final distribution.
A Warning Box shall appear an the screen advising about the fdmpers.bin file creation path.
205678826.doc
UNCLASSIFIED
Page 192
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
205678826.doc
UNCLASSIFIED
Page 193
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
5.5
D
28/02/2003
SOFTWARE PREPARATION
The I.E.S. environment used for the Paper Strip customization shall be created following the IES
Administrator Manual instructions (kit preparation), and referring to an HCI site system directory.
That system configuration environment shall have the nsa table files typically already
customised. (for instance including the vector font file: global_ppst_symbols.dsp).
In order to get information about the kit preparation and installation, the start-up procedure for the
Interface Editor System - Paper Strip configuration, and the preliminary checks, see the
Administrator Software User Manual [E000IES0-06SUM].
205678826.doc
UNCLASSIFIED
Page 194
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
APPENDIX
6.1
APPENDIX A
6.1.1
Calling Functions On Events Examples
In the esb table (esb.dsp):

text : ESB_CS
(
event: ABCK
( function: FORCED_HOOK()
function: POPPINGUP( CLEARANCE_id 'ClearanceMenu')
)
)
In this example you can see the event syntax for the ESB_CS text field. The syntax manages the
ABCK event (clicking with the left mouse button) and activate two different functions :
The FORCED_HOOK() function forces the hooking of the flight item and the POPPINGUP()
function select the Clearence menu by the second parameter (ClearenceMenu) and shows it.
-------------------------------------------------In the esb table (esb.dsp):
text: ESB_XFL 45
(
event: ABCK
event: IBCK
function: EXEC_DOUBLE_TURN (XFL_ID 'choice_XFL')
)
function: EXEC_DOUBLE_TURN (FEL_ID 'choice_FEL')
)
)
In this example you can see the event syntax for the ESB_XFL text field. The syntax manages the
ABCK and the IBCK events (clicking with the left and the central mouse buttons) and activate two
different functions for both events:
The FORCED_HOOK() function forces the hooking of the flight item and the
EXEC_DOUBLE_TURN() function select the XFL and the PEL choices opening a choice menu,
containing information defined by Command Identifiers (XFL_ID, PEL_ID). The second
parameters is the title given to the choice.
-------------------------------------------------In the color table (color.dsp):
symbol: GET_SAVE (
event: ABCK (
function: EXECUTING
(GET_S_FILENAME_PREVIEW)
)
)
205678826.doc
UNCLASSIFIED
Page 195
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
In this example you can see the event syntax for the GET_SAVE symbol field. The syntax
manages the ABCK event (clicking with the left mouse button) and activate a function :
The EXECUTING() function Opens a preview motif interface identified by the parameter
(GET_S_FILENAME_PREVIEW).
205678826.doc
UNCLASSIFIED
Page 196
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
6.2
D
28/02/2003
APPENDIX B
In order to understand the meaning of eventual Error/Warning Messages during the parsing phase,
the following table shows all the possible combination of classes and subclasses.
Typical Error/Warning Messages regard re-declaration of an identifier as belonging to different
object categories. The message will show the hexadecimal value identifying class and may be
subclass too.
6.2.1
Current CLASSES/SUBCLASSES
SCRATCH_CLASS_ID
SCRATCH_CLASS_ID | SCRATCH_SUBCLASS_ID
COLOR_CLASS_ID
COLOR_CLASS_ID | BACKGROUND_COLOR_CLASS_ID
COLOR_CLASS_ID | INVISIBLE_COLOR_CLASS_ID
COLOR_CLASS_ID | NORMAL_COLOR_CLASS_ID
COLOR_CLASS_ID | TRANSPARENT_COLOR_CLASS_ID
COLOR_CLASS_ID | BLINKING_COLOR_CLASS_ID
COLOR_CLASS_ID | STANDARD_COLOR_CLASS_ID
COLOR_CLASS_ID | INDIRECT_COLOR_CLASS_ID
COLOR_CLASS_ID | SEARCH_COLOR_CLASS_ID
FONT_CLASS_ID
STYLE_CLASS_ID
REFERENCE_CLASS_ID
REFERENCE_CLASS_ID | FLIGHT_REFERENCE_CLASS
REFERENCE_CLASS_ID | ALARM_REFERENCE_CLASS
REFERENCE_CLASS_ID | SUP_REFERENCE_CLASS
REFERENCE_CLASS_ID | TRACK_REFERENCE_CLASS
REFERENCE_CLASS_ID | PLOT_REFERENCE_CLASS
REFERENCE_CLASS_ID | GRP_REFERENCE_CLASS
REFERENCE_CLASS_ID | PILOT_REFERENCE_CLASS
COMPONENT_TABLES_CLASS_ID
POINTER_CLASS_ID
BUTTON_CLASS_ID
PRIORITY_CLASS_ID
COMPONENTS_CLASS_ID
INCLUDE_FILES_CLASS_ID
DEVICE_CLASS_ID
CONTAINER_CLASS_ID
BACKGROUND_CLASS_ID
MOTIF_EVENT_CLASS_ID
EVENT_CLASS_ID
ACTION_CLASS_ID
INQUIRE_CLASS_ID
CASE_CLASS_ID
ATTRIBUTE_CLASS_ID
ATTRIBUTE_CLASS_ID | LOCAL_ATTRIBUTE_CLASS
ATTRIBUTE_CLASS_ID | GLOBAL_ATTRIBUTE_CLASS
ATTRIBUTE_CLASS_ID | PARAMETRIC_ATTRIBUTE_CLASS
PRIMITIVE_CLASS_ID
PRIMITIVE_CLASS_ID | LOCAL_SYMBOL_CLASS
PRIMITIVE_CLASS_ID | GLOBAL_SYMBOL_CLASS
205678826.doc
UNCLASSIFIED
0xffff0000
0xffffffff
0x00010000
0x00010001
0x00010002
0x00010003
0x00010004
0x00010005
0x00010006
0x0001000a
0x0001000b
0x00020000
0x00030000
0x00040000
0x00040001
0x00040002
0x00040003
0x00040004
0x00040005
0x00040006
0x00040007
0x00050000
0x00060000
0x00070000
0x00080000
0x00090000
0x000a0000
0x000b0000
0x000c0000
0x000d0000
0x000e0000
0x000f0000
0x00100000
0x00110000
0x00120000
0x00130000
0x00130001
0x00130002
0x00130003
0x00140000
0x00140001
0x00140002
Page 197
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
PRIMITIVE_CLASS_ID | PARAMETRIC_SYMBOL_CLASS
PRIMITIVE_CLASS_ID | PARAMETRIC_MULTI_LIST_SYMBOL_CLASS
MAX_CLASS_ID
SORT_TEMPLATE_CLASS_ID
SORT_REF_NAME_CLASS_ID
SORT_REF_LENGTH_CLASS_ID
REF_MODIFIER_CLASS_ID
TEMPLATE_CLASS_ID
GENERAL_CLASS_ID
EVENT_REF_CLASS_ID
GROUP_CLASS_ID
FIELD_CLASS_ID
FIELD_CLASS_ID | TEXT_FIELD_CLASS
FIELD_CLASS_ID | SYMBOL_FIELD_CLASS
FIELD_CLASS_ID | VECTOR_FIELD_CLASS
FIELD_CLASS_ID | PRIMITIVE_FIELD_CLASS
FIELD_CLASS_ID | MANAGER_FIELD_CLASS
STRING_CLASS_ID
ENUM_CLASS_ID
EXPRESSION_CLASS_ID
205678826.doc
UNCLASSIFIED
D
28/02/2003
0x00140003
0x00140004
0x00150000
0x00160000
0x00170000
0x00180000
0x00190000
0x001a0000
0x001b0000
0x001c0000
0x001d0000
0x001e0000
0x001e0001
0x001e0002
0x001e0003
0x001e0004
0x001e0005
0x001f0000
0x00200000
0x00210000
Page 198
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
6.3
D
28/02/2003
APPENDIX C
6.3.1
ATC Glossary
AB
ABI
ACC
ACD
ACK
ACL
ACR
ADI
ADP
ADPS
ADW
AFTN
AIS
AKW
ALT
ALV
ANS
AOC
APM
APP
APW
ARR
ASC
ASQ
ASS
ATA
ATC
ATD
ATI
ATM
ATO
ATS
Action Button
Auxiliary Boundary Information
Area Control Centre
Advanced Common Database
Acknowledge
Arrival CLearance
Arrival Clearance with Re-routing
Advanced DIsplay
Auxiliary Data Processing
Auxiliary Data Processing System
AirDrome Workability
Aeronautical Fixed Traffic Network
Aeronautical Information Service
AcKnowledge Warning
Altitude Alarm
Authorization LeVel
Accept New Strip
Assumption Of Control
APproach Mode
APProach control
Airdrome Present Weather
ARRival
ASsistant Controller
Arrival SeQuencing
ASSistant function
Actual Time of Arrival
Air Traffic Control
Actual Time of Departure
Actual Time of Inbound
Air Traffic Management
Actual Time Over
Air Traffic Service
BRW
BYP
BYR
BRoWse
BYPass selection
BYpass Reached
CDS
CDS1000
CDS2000
CEN
CHK
CLB
CNL
CMS
COPS
CPA
CRR
CSA
205678826.doc
Common Display System

CDS 1280 x 1024 pixels
CDS 2048 x 2048 pixels
(default) CENtre
CHecK
Conflict LaBel
CaNceL
Control and Monitoring System
Common Operational Performance Specification
CWP Assignment
Clear Raw Radar
Control Strip Area
UNCLASSIFIED
Page 199
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
CSCI
CSL
CSV
CTR
CU1
CU2
CWP
Computer Software Configuration Item

CoaSt List
Change Step Values
Airport Control Area
Cursor 1
Cursor 2
Controller Working Position
DA
DAIW
DARD
DBC
DCL
DCR
DCO
DCY
DEC
DEP
DFA
DFI
DFN
DIS
DLA
DMD
DOT
DPT
DRS
DSC
DSD
DSV
DSA
DTX
Deviation Alert
Danger Area Infringement Warning
Direct Access Radar Data
Display Block Code
Departure CLearance
Departure Clearance with Re-routing
undo Draw action
DeCaY selection
track DECorrelation
DEParture list
Data Flight Amend
Data Flight Insert
Direction FiNder display
DISabled
DeLAy departure
Dangerous area Map Display
Draw symbol
Display Predicted Trajectory
DARD Selection
DiSseminator Change
DiSseminator Disabling
Display Speed Vector
Display Strip Area
Draw TeXt
EBC
EHL
ELS
EMG
EML
EPS
ESB
EST
ETA
Enter Block Code

Enter Height Layer
Enable Local Settings
EMerGency
End Local Map
Empty Print Strip
Electronic Strip Bay window
ESTimate
Estimated Time of Arrival / Estimated Exit Time from the feeding fix (in ACL
order)
Estimated Time of Departure
Estimated Time of Inbound
Estimated Time of Landing
Estimated Time Over
EXecutive Controller
EXEcutive function
ETD
ETI
ETL
ETO
EXC
EXE
FCK
FCN
FDM
FDP
205678826.doc
Formality ChecK
Flight data CaNcellation
Flight Data Management
Flight Data Processing
UNCLASSIFIED
Page 200
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
FDPAL
FIR
FL
FLD
FLDA
FLDI
FLS
FLTA
FPD
FPL
FPLM
FPM
FPR
FRC
Flight Strip Ordering

Flight Strip Selection
File Transfer
File TeRmination
FirmWare
GRP
GRS
General Radar Picture

Global Radar data Selection
HCI
HDG
HIJ
HLD
HLO
HOC
HOE
HOK
HOL
HW
Human-Computer Interface
HeaDinG
HIJack
HoLDing list
Height Layer On/Off
HOlding Cancellation
HOlding Exit
HoOK
HOLding insert
HardWare
L&G
LAA
LAB
LAN
205678826.doc
FDP Alarm List

Flight Information Region
Flight Level
FLDA Displaying
FLight DAta page list
FLight DIrectory list
Flight Line Selection
FLight Transiction Altitude
Flight Plan Display
Flight PLan entry
Flight PLan Message list
FPLM displaying
Flight Plan Re-entry
airdrome FoReCast
FSO
FSS
FT
FTR
FW
I/O
IB
ICA
ICAO
ICC
ICM
IFA
IFP
IFR
IMA
IMG
INBFIX
INI
IRS
D
28/02/2003
Input/Output
Information Button
InterConsole mark Acknowledge
International Civil Aviation Organization
InterConsole mark Cancel
InterConsole Mark
Identification Flight Amendment
Identification Flight Plan
Instrumental Flight Rule
Interconsole Message Acknowledge
Interconsole MessaGe
INBound (entry) FIX
INItialize
Interface Requirements Specification
Load and Go
Low Altitude Alarm
LABel selection
Local Area Network
UNCLASSIFIED
Page 201
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
LCM
LDA
LDL
LDN
LEV
LFA
LFI
LFU
LID
LMC
LMD
LMG
LML
LMS
LND
LOC
LOM
LRW
LSC
LSR
LST
LSV
LVA
Logical CWP Monitoring

Local Data Area
set LeaDer Length
LaDiNg list
LEVel
Logical ATS Function Assignment
Limited Flight Insert
Limited Flight Update
Limited Identified flight Data
Logical Console Monitoring
Local Map Displaying
Local Map Generation
Local Map Loading
Local Map Storing
LANding report
LOCal message
LOcal Map orders
Landing RunWay
Label Strip Creating
Label Strip Removing
enable/disable List STatus
LaSt leVel
planned/cleared LeVel Assignment
MAM
Met/Ais Menu display
MAP
MARA
MET
MGC
MHT
MIL
MIX
MLB
MMA
MNG
MON
MOT
MPG
MPL
MRI
MRK
MRT
MSAW
MST
MTBF
MTCA
MTR
enable/disable MAP display

Modular Architecture for Real-time Applications
METeorological
MaGnetic Correction change
Manual Handling sTrip
MILitary
MIX presentation
display MacroLaBel
Main Menu Area window
MaNaGement
(go to) MON state / MONitor
MOTion
Map Generation System
start Local MaP
Range Mark Intensity
Range MarK selection
Multi Radar Tracking
Minimum Safe Altitude Warning
Move STrip
Mean Time Between Failure
Medium Term Conflict Alert
Mean Time of Repair
NAVAID
NM
NOTAM
NRM
NSA
205678826.doc
D
28/02/2003
NAVigational AID
Nautical Miles
NOtice to AirMan
NoRth Mark selection
New Strip Area
UNCLASSIFIED
Page 202
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
NSL
NVS
Off Block Time

Operational Display Input and Development
Operator input and Display System
OFf Centre
On Line Data Interface
ON Line
Operational
PEN
PHT
PKB
PLB
PLC
PLO
PLF
PLN
PPF
PPST
PSR
PENding tracks
Plot History Trail
ParKing Bay allocation
PLayBack
PLanning Controller
PLOt labels
Primary Label Filter
PLaNning function
Primary Plot Filter
Paper Strip
Primary Surveillance Radar
QNH
Barometric pressure / enter QNH
SAR
SBR
SBY
SDA
SID
SIG
205678826.doc
Nearby Sector Label

NaVigator aid
OBT
ODID
ODS
OFC
OLDI
ONL
OP
RAA
RAR
RCL
RCR
RCS
RDP
RDPAL
REC
REL
REP
REV
RHP
RIC
RNG
ROT
RRA
RRC
RRD
RRR
RRS
RTN
RWY
D
28/02/2003
Restricted Area Alarm

Regulated Area Restriction
en-Route CLearance
en-Route Clearance with Re-routing
Radar Channel Selection
Radar Data Processing
RDP Alarm List
RECording
RELease
Position REport
estimate REVision
Radar Head Processor
sector RIConfiguration
RaNGe scale
ROTate Label
Raw Radar Area
Range Rings Center
Range Rings Display
Range Rings Radius
Raw Radar Selection
RoTate preseNtation
RunWaY
draw ARc and circle
draw BRoken
Stand-BY
System Data Area
Standard Instrumental Departure
fir SIGmet
UNCLASSIFIED
Page 203
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
205678826.doc
SIL
SIM
SLB
SLC
SLS
SMD
SMD
SMS
SPM
SPR
SPS
SPV
SRC
SRD
SRL
SRO
SRP
SRR
SRS
SRT
SRW
SSP
SSR
SST
STAR
STCA
STF
SUM
SVR
SYN
SW
Sector Inbound List

SIMulator processor
Single LaBel
Screen Layout exChange
Store Local Settings
System Messages Dispatching (CSCI)
Supervisor Map Display (order SMD)
Supervisor Map Sending
Supervisor Password Modify
Supervisor Privilege Releasing
Supervisor Privilege Setting
SuPerVisor
global Sector ReConfiguration
SRP presentation center Definition
SSR code ReLease
SRP window On/off
Selected Radar Picture window
SRP Range scale
Suite Radar Data Selection
Single Radar Tracking
SRP Window definition
Suppression Symbol Position
Secondary Surveillance Radar / SSR code assignment
Shift STrip
STandard Approaching Route
Short Term Conflict Alert
Site Transponder Filter
Software User Manual
SuperVisoR message
SYNthetic presentation
SoftWare
TAB
TAS
TBD
TCA
THT
TKF
TMA
TMS
TOC
TRI
TRN
TRW
TST
TXT
TWR
Tab Area window

True Air Speed / change True Air Speed
To Be Defined
Term Conflict Alert
Track History Trail
TaKe-oFf report
TerMinal Area
Terminal Area management
Transfer Of Control
TRIgger selection
TRaiNing
departure RunWay
TeST
free TeXT
control ToWeR
VDU
VFD
VFO
VFR
VMD
VSi
Video Display Unit

Volume Filter Definition
Volume Filter On/off
Visual Flight Rule
Volume Map Display
raw Video Display; i=1..4
UNCLASSIFIED
D
28/02/2003
Page 204
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
205678826.doc
URW
Unified RanWay
WAA
WB
WMD
WSP
WTC
WSP
Warning/Alarm Area window

Window Button
Weather Map Display
StriP reprinting request
WaTChing
Write Strip Paper Print
UNCLASSIFIED
D
28/02/2003
Page 205
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
6.4
6.4.1
D
28/02/2003
APPENDIX D
Reference Help
In this appendix you can find all the references used in the IES Tabular facility, these references are
concerning about Flight, Sup or Alarm.
After someone of these reference names, you can find a little description of the reference and, if
possible, an example of usage.
205678826.doc
UNCLASSIFIED
Page 206
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
6.4.1.1 Flight reference help

______________________________________________________________________
__________________________________________________
__________________________________________________
Category: Flight
__________________________________________________
__________________________________________________
______________________________________________________________________
AIRP_NAME_BY_GROUP_REF
Reference: AIRP_NAME_BY_GROUP_REF
Description:
Handler: flight
Components Usage: tabular
Type: string
Synopsis:
AIRP_NAME_BY_GROUP_REF
Example:
text: ARR_SEP_NAME
(
attribute: @TABLE_NAME@_A_GREAT_TEXT
length: 4;
...
reference_param: AIRP_NAME_BY_GROUP_REF(GROUP_IDX_REF;)
)
______________________________________________________________________
FIX_NAME_BY_GROUP_REF
Reference: FIX_NAME_BY_GROUP_REF
Description:
Handler: flight
Type: string
Synopsis:
FIX_NAME_BY_GROUP_REF
Example:
text: ENR_SEP_NAME
(
length: 5;
...
reference_param: FIX_NAME_BY_GROUP_REF(GROUP_IDX_REF;)
)
______________________________________________________________________
FLIGHT_ACNR_REF
Reference: FLIGHT_ACNR_REF
Description:
Handler: flight
Components Usage: preview
Type: string
Synopsis:
FLIGHT_ACNR_REF
Example:
preview: LFU
(
...
205678826.doc
UNCLASSIFIED
Page 207
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
field: LFI_ACN_FLD
(
label (default: 'AC' )
text
(
default :' 1'
reference: FLIGHT_ACNR_REF
length
: 2
)
)
______________________________________________________________________
FLIGHT_ACR_REF
Reference: FLIGHT_ACR_REF
Description:
This reference is not implemented.
______________________________________________________________________
FLIGHT_ACT_REF
Reference: FLIGHT_ACT_REF
Description:
Handler: flight
Type: string
Synopsis:
FLIGHT_ACT_REF
Example:
text: SEL_ACT
(
attribute: SEL_A_TEXT
length
: 1;
initial : 'SEL_ACT'
actions
(
set_field_attribute
(
CURRENT_TEMPLATE, CURRENT_FIELD, ACT_PRESENCE
)
)
...
reference: FLIGHT_ACT_REF
)
______________________________________________________________________
FLIGHT_ADAL_FIX_REF
Reference: FLIGHT_ADAL_FIX_REF
Description:
Handler: flight
Type:
Synopsis:
FLIGHT_ADAL_FIX_REF
Example:
choice: UNGROUP_ADAL
(
legend:'UNGROUP'
class : EXCLUSIVE_FDD
field : UNGROUP_ADAL_FLD
(
text
(
205678826.doc
UNCLASSIFIED
Page 208
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
)
)
D
28/02/2003
reference: FLIGHT_ADAL_FIX_REF
length
: 5
______________________________________________________________________
FLIGHT_ADAL_NAME_REF
Reference: FLIGHT_ADAL_NAME_REF
Description:
This reference is used to refere the
Airport Departure/Arrival List Name for the flight.
Handler: flight
Components Usage: tabular.
Type: string
Synopsis:
FLIGHT_ADAL_NAME_REF
Examples:
One could relate the referred text field of the presentation object
to the record (i.e. conceptual object) field, of the flight
internal database, named FLIGHT_ADAL_NAME_REF.
text ADAL_NAME:
(
reference: FLIGHT_ADAL_NAME_REF
length
: 5;
)
______________________________________________________________________
FLIGHT_ADSU_REF
Reference: FLIGHT_ADSU_REF
Description:
This reference is used to refere the ADSU Address (is the identify
of the airplane in the ADS comunication) for the flight.
Handler: flight
Components Usage:
Type: string
Synopsis:
FLIGHT_ADSU_REF
Example:
text: MLB_ADSU
(
attribute: MLB_A_TEXT
...
length: 10;
reference: FLIGHT_ADSU_REF
)
______________________________________________________________________
FLIGHT_ADS_ADDR_REF
Reference: FLIGHT_ADS_ADDR_REF
Description:
Handler: flight
Type: string
Synopsis:
FLIGHT_ADS_ADDR_REF
Example:
text: MLB_ADS_ADDR
(
205678826.doc
UNCLASSIFIED
Page 209
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
attribute: @TABLE_NAME@_A_TEXT
...
length
: 4;
reference: FLIGHT_ADS_ADDR_REF
______________________________________________________________________
FLIGHT_AFL_REF
Reference: FLIGHT_AFL_REF
Description:
Handler: flight
Type:
Synopsis:
FLIGHT_AFL_REF
Example:
text: FHI_AFL
(
attribute: FHI_A_TEXT
...
length: 3;
event: ABCK
(
function: FORCED_HOOK ()
f.dialog: DOUBLE_TURN_ELASTIC_HEADING
cursor_ELASTIC_HEADING ""
...
)
reference: FLIGHT_AFL_REF
)
______________________________________________________________________
FLIGHT_ALV_REF
Reference: FLIGHT_ALV_REF
Description:
This reference is used to refer to the
Level Authorization for the flight.
Handler: flight
Components Usage: tabular, preview.
Type: string (Max Length: LEVEL_LENGTH)
Synopsis:
FLIGHT_ALV_REF
Examples:
One could relate the ALV_FIELD text field of the presentation object
internal database, named FLIGHT_ALV_REF.
text: ALV_FIELD
(
reference: FLIGHT_ALV_REF
...
length: LEVEL_LENGTH;
)
______________________________________________________________________
FLIGHT_AOBT_REF
Reference: FLIGHT_AOBT_REF
Description:
Handler: flight
Type: string
205678826.doc
UNCLASSIFIED
Page 210
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Synopsis:
FLIGHT_AOBT_REF
Examples:
internal database, named FLIGHT_AOBT_REF.
text
(
reference: FLIGHT_AOBT_REF
length
: 4;
)
______________________________________________________________________
FLIGHT_ARC_REF
Reference: FLIGHT_ARC_REF
Description:
This reference describes Assigned Rate of
Climbing information.
Handler: flight
Components Usage:
Type: string
Synopsis:
FLIGHT_ARC_REF
Example:
text: FLD_ARC_CRC
(
actions:
(
if flight(FLIGHT_ARC_REF).string = "
"
& TRACK_HIGHLIGHT_REF.state then
visible: TRUE
value : "arc"
else
value :flight(FLIGHT_ARC_REF).string
endif
)
)
______________________________________________________________________
FLIGHT_ASN_REF
Reference: FLIGHT_ASN_REF
Description:
Handler: flight
Components Usage: preview.
Type: string (Max Length:)
Synopsis:
FLIGHT_ASN_REF
Example:
preview: ASQ
(
title :'ASQ: ARR SEQUENCE ' + FLIGHT_CALLSIGN_REF
warning:(line : 2)
...
field : ASQ_SQN_FLD
(
text
(
reference: FLIGHT_ASN_REF
length
: 2
)
)
)
205678826.doc
UNCLASSIFIED
Page 211
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
______________________________________________________________________
FLIGHT_ATY_REF
Reference: FLIGHT_ATY_REF
Description:
ATY for the flight.
Handler: flight
Type: string
Synopsis:
FLIGHT_ATY_REF
Example:
preview: ATY
(
label : 'AIRCRAFT TYPE'
warning: ( line : 2)
field : ATY_FLD
(
text
(
reference: FLIGHT_ATY_REF
length
: 1
)
)
)
______________________________________________________________________
FLIGHT_BRNAV_BIN_REF
Reference: FLIGHT_BRNAV_BIN_REF
Description:
Handler: flight
Type: numeric
Synopsis:
FLIGHT_BRNAV_BIN_REF
Example:
text: ESB_BRNAV
(
attribute: NSA_A_TEXT
...
length: 1;
actions
(
set_field_text
(
CURRENT_TEMPLATE,
CURRENT_FIELD,
brnav_value_tab[FLIGHT_BRNAV_BIN_REF]
)
)
reference: FLIGHT_NULL_REF
______________________________________________________________________
FLIGHT_BRNAV_REF
Reference: FLIGHT_BRNAV_REF
Description:
Handler: flight
205678826.doc
UNCLASSIFIED
Page 212
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Type: string
Synopsis:
FLIGHT_BRNAV_REF
Example:
preview: PCO
(
title:'PCO: PHONE COORD ' + FLIGHT_CALLSIGN_REF
class: EXCLUSIVE_FDD
...
field: PCO_BRNAV_FLD
(
label (default: 'BRNAV' )
text
(
reference: FLIGHT_BRNAV_REF
length
: 1
)
help
(
type
:
visible:
values :
default:
)
)
CHOICE
off
brnav_value_tab
' '
______________________________________________________________________
FLIGHT_CALLSIGN_REF
Reference: FLIGHT_CALLSIGN_REF
Description:
Callsign for the flight.
Handler: flight
Components Usage: tabular, preview, dialog.
Type: string (Max Length: CALLSIGN_LENGTH)
Synopsis:
FLIGHT_CALLSIGN_REF
Examples:
One could relate the SEL_CS text field of the presentation object
internal database, named FLIGHT_CALLSIGN_REF.
text: SEL_CS
(
reference: FLIGHT_CALLSIGN_REF
...
length: CALLSIGN_LENGTH;
)
______________________________________________________________________
FLIGHT_CATEGORY_BIN_REF
Reference: FLIGHT_CATEGORY_BIN_REF
Description:
Category binary value for the flight.
Handler: flight
Type: string
Synopsis:
FLIGHT_CATEGORY_BIN_REF
Examples:
field: IDD_TYPE_FLD
(
label (default: 'TYPE' )
205678826.doc
UNCLASSIFIED
Page 213
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
text
(
reference: FLIGHT_CATEGORY_BIN_REF
length
: 1
)
help
(
type
: CHOICE
visible: off
values : flight_type_value_tab
default:'D'
)
)
______________________________________________________________________
FLIGHT_CATEGORY_REF
Reference: FLIGHT_CATEGORY_REF
Description:
Category for the flight.
Handler: flight
Type: string
Synopsis:
FLIGHT_CATEGORY_REF
Examples:
internal database, named FLIGHT_CATEGORY_REF.
text
(
reference: FLIGHT_CATEGORY_REF
length
: 3;
)
______________________________________________________________________
FLIGHT_CDIS_REF
Reference: FLIGHT_CDIS_REF
Description:
Handler: flight
Type: string (Max Length: )
Synopsis:
FLIGHT_CDIS_REF
Example:
One could relate the FLDA_CDIS_FIELD text field of the presentation object
internal database, named FLIGHT_CDIS_REF.
text: FLDA_CDIS_FIELD
(
attribute: FLDA_A_TEXT
...
length
: 4;
reference: FLIGHT_CDIS_REF
)
______________________________________________________________________
FLIGHT_CILCOL_FIX_REF
Reference: FLIGHT_CILCOL_FIX_REF
Description:
205678826.doc
UNCLASSIFIED
Page 214
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Handler: flight
Type:
Synopsis:
FLIGHT_CILCOL_FIX_REF
Example:
choice: UNGROUP
(
legend: 'UNGROUP'
field : UNGROUP_FLD
(
text
(
reference: FLIGHT_CILCOL_FIX_REF
length
: 5
)
)
)
______________________________________________________________________
FLIGHT_CIL_COL_NAME_REF
Reference: FLIGHT_CIL_COL_NAME_REF
Description:
Cop Inbound List Name for the flight.
Handler: flight
Type: string
Synopsis:
FLIGHT_CIL_COL_NAME_REF
Examples:
internal database, named FLIGHT_CIL_COL_NAME_REF.
text CIL_NAME:
(
reference: FLIGHT_CIL_COL_NAME_REF
length
: 5;
)
______________________________________________________________________
FLIGHT_CLEAR_FLAG_REF
Reference: FLIGHT_CLEAR_FLAG_REF
Description:
Handler: flight
Type: string
Synopsis:
FLIGHT_CLEAR_FLAG_REF
Example:
preview: FFI
(
label :'FAST FLIGHT INBOUND'
...
field: FFI_CLR_FLD
(
label (default: 'CLR' )
text
(
reference: FLIGHT_CLEAR_FLAG_REF
205678826.doc
UNCLASSIFIED
Page 215
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
length
)
D
28/02/2003
: 1
)
______________________________________________________________________
FLIGHT_CODENSSR_REF
Reference: FLIGHT_CODENSSR_REF
Description:
Handler: flight
Type: string
Synopsis:
FLIGHT_CODENSSR_REF
Example:
preview: SSR
(
title: 'SSR: SSR CODE ASS.' + FLIGHT_CALLSIGN_REF
field: NSSR_SSR_FLD
(
label (default: 'NSSR' )
text
(
reference: FLIGHT_CODENSSR_REF
length
: 4
)
)
)
______________________________________________________________________
FLIGHT_CODEPSSR_REF
Reference: FLIGHT_CODEPSSR_REF
Description:
Handler: flight
Type: string
Synopsis:
FLIGHT_CODEPSSR_REF
Example:
preview: SSR
(
field: PSSR_SSR_FLD
(
label (default: 'PSSR' )
text
(
reference: FLIGHT_CODEPSSR_REF
length
: 4
)
)
)
______________________________________________________________________
FLIGHT_CODESSR_REF
Reference: FLIGHT_CODESSR_REF
Description:
Handler: flight
205678826.doc
UNCLASSIFIED
Page 216
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003

Type: string
Synopsis:
FLIGHT_CODESSR_REF
Example:
preview: SSR
(
label :'SSR CODE ASSIGNM'
warning:(line : 2)
field : SSR_SSR_FLD
(
label (default: 'SSR' )
text
(
reference: FLIGHT_CODESSR_REF
length
: 4
)
)
field: SSR_MODESSR_FLD
(
label (default: 'MODE' )
text
(
reference: FLIGHT_MODESSR_REF
length
: 1
default :'A'
)
)
)
______________________________________________________________________
FLIGHT_COD_CAT_SSR_REF
Reference: FLIGHT_COD_CAT_SSR_REF
Description:
This reference will be used to refer to the
Secondary Surveillance Radar category code.
Handler: flight
Type: string
Synopsis:
FLIGHT_COD_CAT_SSR_REF
Example:
Not used.
______________________________________________________________________
FLIGHT_COF_MAS_DOWN_DRAWING_REF
Reference: FLIGHT_COF_MAS_DOWN_DRAWING_REF
Description:
Handler: flight
Components Usage: contact
Type: numeric
Synopsis:
FLIGHT_COF_MAS_DOWN_DRAWING_REF
Example:
template : CONTROLLED
(
class: CONTROLLED
...
label
(
actions: (visible: ~TRACK_LISTED_REF.state)
...
205678826.doc
UNCLASSIFIED
Page 217
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
text: FLD_CALLSIGN
(
...
actions:
(
switch: flight(FLIGHT_COF_MAS_DOWN_DRAWING_REF).num
(
case: COF_MAS_HAND_SEND_CASE (color: HANDOVER_REC_COLOR)
case: COF_MAS_NEARBY_CASE
(color: NEIGHBOUR_COLOR)
case: COF_MAS_HAND_REC_CASE
(color: HANDOVER_REC_COLOR)
case: COF_MAS_CONTROLLED_CASE (color: CONTROLLED_COLOR)
)
...
)
)
)
______________________________________________________________________
FLIGHT_COF_MAS_UP_DRAWING_REF
Reference: FLIGHT_COF_MAS_UP_DRAWING_REF
Description:
Handler: flight
Type: numeric
Synopsis:
FLIGHT_COF_MAS_UP_DRAWING_REF
Example:
template : CONTROLLED
(
class: CONTROLLED
...
label
(
actions: (visible: ~TRACK_LISTED_REF.state)
...
text: FLD_CALLSIGN
(
...
actions:
(
switch: flight(FLIGHT_COF_MAS_UP_DRAWING_REF).num
(
case: COF_MAS_HAND_SEND_CASE (color: HANDOVER_REC_COLOR)
case: COF_MAS_NEARBY_CASE
(color: NEIGHBOUR_COLOR)
case: COF_MAS_HAND_REC_CASE
(color: HANDOVER_REC_COLOR)
case: COF_MAS_CONTROLLED_CASE (color: CONTROLLED_COLOR)
)
...
)
)
)
)
______________________________________________________________________
FLIGHT_COMNAVEQUIP_REF
-- Sorry, Help Is Not Available For This Item
______________________________________________________________________
FLIGHT_COMPUTE_POWER_REF
Reference: FLIGHT_COMPUTE_POWER_REF
Description:
Handler: flight
Type:
205678826.doc
UNCLASSIFIED
Page 218
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Synopsis:
FLIGHT_COMPUTE_POWER_REF
Example:
TogglbelString: "ACR"
set: False
update: ( sensitive : FLIGHT_PWRTBL_REF#ACR_ID.state)
update:
(
component : .HOOK.set
userdata : FLIGHT_COMPUTE_POWER_REF#ACR_ID.state
)
AllComponentCallback: notify
(
FLIGHT_POWER_HCI_REF#ACR_ID
state: allComponent
)
______________________________________________________________________
FLIGHT_COMP_ABB_REF
Reference: FLIGHT_COMP_ABB_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_COMP_FULL_REF
Reference: FLIGHT_COMP_FULL_REF
Description:
Handler: flight
Type:
Synopsis:
FLIGHT_COMP_FULL_REF
Example:
text: FHI_COMP
(
attribute: A_TEXT
...
length: 15;
reference: FLIGHT_COMP_FULL_REF
)
______________________________________________________________________
FLIGHT_COORD_ID_REF
Reference: FLIGHT_COORD_ID_REF
Description:
This reference is used to refere coordination identifier
Handler: flight
Components Usage:
Type: string
Synopsis:
FLIGHT_COORD_ID_REF
Examples:
text: COORDIN_ATYPE
(
205678826.doc
UNCLASSIFIED
Page 219
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
attribute: COORDIN_A_TEXT
...
length: 4;
actions
(
set_field_text
(
CURRENT_TEMPLATE,
CURRENT_FIELD,
coord_type[FLIGHT_COORD_ID_REF]
)
)
event: ABCK (function: HOOKING ())
reference: FLIGHT_COORD_ID_REF
______________________________________________________________________
FLIGHT_COORD_ID_REMINDER_REF
Reference: FLIGHT_COORD_ID_REMINDER_REF
Description:
This reference is used to refere coordination reminder
identifier
Handler: flight
Components Usage:
Type: string
Synopsis:
FLIGHT_COORD_ID_REMINDER_REF
Examples:
text: COORDIN_ACK
(
...
length: 1;
actions
(
if FLIGHT_COORD_ID_REMINDER_REF = 3
then
! 0 = PEL_REJECT - PER
if FLIGHT_COORD_ID_REF = 0 then
field_on (COORDIN_ACK)
else
field_off (COORDIN_ACK)
endif
else
field_off (COORDIN_ACK)
endif
)
)
______________________________________________________________________
FLIGHT_COORD_INIT_SECTOR_REF
Reference: FLIGHT_CORD_INIT_SECTOR_REF
Description:
This reference will be used to refere the init sector code
involved in the coordination value
Handler: flight
Components Usage:
Type: string
Synopsis:
FLIGHT_COORD_INIT_SECTOR_REF
Examples:
Not used
______________________________________________________________________
FLIGHT_COORD_ORIGINAL_VALUE_REF
205678826.doc
UNCLASSIFIED
Page 220
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Reference: FLIGHT_COORD_ORIGINAL_VALUE_REF
Description:
This reference is used to refere the coordination original
value.
Handler: flight
Components Usage:
Type: string
Synopsis:
FLIGHT_COORD_ORIGINAL_VALUE_REF
Examples:
text: COORDIN_ORIGVALUE
(
...
length: 3;
event : ABCK (function: HOOKING ())
reference: FLIGHT_COORD_ORIGINAL_VALUE_REF
)
______________________________________________________________________
FLIGHT_COORD_PARTNER_SECTOR_REF
Reference: FLIGHT_COORD_PARTNER_SECTOR_REF
Description:
This reference is used to refere the partner sector index
Handler: flight
Components Usage:
Type: string
Synopsis:
FLIGHT_COORD_PARTNER_SECTOR_REF
Examples:
text: COORDIN_SECT
(
...
length: 3;
actions
(
switch: DEV_AL_REF
(
case: DEV_AL_TRUE_CASE
(
set_field_attribute
(
CURRENT_TEMPLATE,
CURRENT_FIELD,
FG_DEVIATION_ALERT
)
)
)
)
reference: FLIGHT_COORD_PARTNER_SECTOR_REF
)
______________________________________________________________________
FLIGHT_COORD_TIME_REF
Reference: FLIGHT_COORD_TIME_REF
Description:
This reference is used to refere the partner sector name
Handler: flight
Components Usage:
Type: string
205678826.doc
UNCLASSIFIED
Page 221
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Synopsis:
FLIGHT_COORD_TIME_REF
Examples:
text: COORDIN_TIME
(
...
length: 4;
actions
(
switch: DEV_AL_REF
(
case: DEV_AL_TRUE_CASE
(
set_field_attribute
(
CURRENT_TEMPLATE,
CURRENT_FIELD,
FG_DEVIATION_ALERT
)
)
)
)
event: ABCK
(function: HOOKING ())
reference: FLIGHT_COORD_TIME_REF
)
______________________________________________________________________
FLIGHT_COO_CRC_REF
Reference: FLIGHT_COO_CRC_REF
Description:
crc fir coordinates.
Handler: flight
Components Usage: Widget.
Type: string (Max Length: CRC_LENGTH)
Synopsis:
FLIGHT_COO_CRC_REF
Examples:
One could relate the COO_CRC_FLD text field of the presentation object
internal database, named FLIGHT_COO_CRC_REF.
preview: COO
(
label: 'COO'
...
field: COO_CRC_FLD
(
label (default: 'CRC' )
text
(
reference: FLIGHT_COO_CRC_REF
length
: 1
)
)
)
______________________________________________________________________
FLIGHT_COO_ETO_REF
Reference: FLIGHT_COO_ETO_REF
Description:
Estimated Time Over the outbound fix of
a sector for a flight.
Handler: flight
205678826.doc
UNCLASSIFIED
Page 222
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Type: string (Max Length: TIME_LENGTH)

Synopsis:
FLIGHT_COO_ETO_REF
Examples:
One could relate the ESB_ETA_ATD text field of the presentation object
internal database, named FLIGHT_COO_ETO_REF.
text: ESB_ETA_ATD
(
reference: FLIGHT_COO_ETO_REF
length
: TIME_LENGTH
)
______________________________________________________________________
FLIGHT_COO_FIX_REF
Reference: FLIGHT_COO_FIX_REF
Description:
Fix Fir Coordinates for a flight.
Handler: flight
Type: string
Synopsis:
FLIGHT_COO_FIX_REF
Example:
general
(
...
preview: COO
(
label: 'COO'
...
field: COO_FIX_FLD
(
label (default: 'FIX' )
text
(
reference: FLIGHT_COO_FIX_REF
length
: 5
)
)
)
)
______________________________________________________________________
FLIGHT_COO_SPL_REF
Reference: FLIGHT_COO_SPL_REF
Description:
spl fir coordinates.
Handler: flight
Synopsis:
FLIGHT_COO_SPL_REF
Examples:
One could relate the COO_SPL_FLD text field of the presentation object
internal database, named FLIGHT_COO_SPL_REF.
preview: COO
(
label: 'COO'
205678826.doc
UNCLASSIFIED
Page 223
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
...
field: COO_SPL_FLD
(
label (default: 'SPL' )
text
(
reference: FLIGHT_COO_SPL_REF
length
: 3
)
)
______________________________________________________________________
FLIGHT_COO_TX_REF
Reference: FLIGHT_COO_TX_REF
Description:
tx fir coordinates.
Handler: flight
Type: string (Max Length: TX_LENGTH)
Synopsis:
FLIGHT_COO_TX_REF
Examples:
One could relate the COO_TX_FLD text field of the presentation object
internal database, named FLIGHT_COO_TX_REF.
preview: COO
(
label: 'COO'
...
field: COO_TX_FLD
(
label (default: 'TX' )
text
(
reference: FLIGHT_COO_TX_REF
length
: 1
)
)
)
______________________________________________________________________
FLIGHT_COO_XFL_REF
Reference: FLIGHT_COO_XFL_REF
Description:
Coordinates of Exit Entry Level for the flight.
Handler: flight
Synopsis:
FLIGHT_COO_XFL_REF
Example:
general
(
...
preview: COO
(
label: 'COO'
...
field: COO_XFL_FLD
(
label (default: 'XFL' )
text
205678826.doc
UNCLASSIFIED
Page 224
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
(
reference: FLIGHT_COO_XFL_REF
length
: 3
)
)
______________________________________________________________________
FLIGHT_CRF_REF
Reference: FLIGHT_CRF_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_CS_DRAWING_REF
Reference: FLIGHT_CS_DRAWING_REF
Description:
Handler: flight
Type: numeric
Synopsis:
FLIGHT_CS_DRAWING_REF
Example:
actions:
(
switch: flight(FLIGHT_CS_DRAWING_REF).num
(
...
)
)
______________________________________________________________________
FLIGHT_CTIM_REF
Reference: FLIGHT_CTIM_REF
Description:
Handler: flight
Synopsis:
FLIGHT_CTIM_REF
Example:
One could relate the FLDA_CTIM_FIELD text field of the presentation object
internal database, named FLIGHT_CTIM_REF.
text: FLDA_CTIM_FIELD
(
...
length
: 4;
reference: FLIGHT_CTIM_REF
)
205678826.doc
UNCLASSIFIED
Page 225
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
______________________________________________________________________
FLIGHT_CTOT_REF
Reference: FLIGHT_CTOT_REF
Description:
Handler: flight
Synopsis:
FLIGHT_CTOT_REF
Example:
text: MLB_CTOT
(
...
length
: 4;
reference: FLIGHT_CTOT_REF
)
______________________________________________________________________
FLIGHT_DATE_REF
Reference: FLIGHT_DATE_REF
Description:
Used to refer to the date of the flight (yymmdd)
Handler: flight
Type: string (Max Lenght: GEN_DATE_LENGTH)
Synopsis:
FLIGHT_DATE_REF
Example:
One could relate the ESB_DATE text field of the presentation object
internal database, named FLIGHT_DATE_REF.
text: ESB_DATE
(
attribute: ESB_A_TEXT
...
length: 6;
event: ABCK ( function: HOOKING() )
reference: FLIGHT_DATE_REF
)
______________________________________________________________________
FLIGHT_DEP_REF
Reference: FLIGHT_DEP_REF
Description:
Departure Airport ICAO Code for the flight.
Handler: flight
Type: string (Max Length: AIRPORT_LENGTH)
Synopsis:
FLIGHT_DEP_REF
Examples:
One could relate the DEP_FIELD text field of the presentation object
internal database, named FLIGHT_DEP_REF.
text: DEP_FIELD
(
reference: FLIGHT_DEP_REF
205678826.doc
UNCLASSIFIED
Page 226
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
...
length: AIRPORT_LENGTH;
______________________________________________________________________
FLIGHT_DES_REF
Reference: FLIGHT_DES_REF
Description:
Destination Airport ICAO Code for the flight.
Handler: flight
Type: string (Max Length: AIRPORT_LENGTH)
Synopsis:
FLIGHT_DES_REF
Examples:
One could relate the DES_FIELD text field of the presentation object
internal database, named FLIGHT_DES_REF.
text: DES_FIELD
(
reference: FLIGHT_DES_REF
...
)
______________________________________________________________________
FLIGHT_DIP_REF
Reference: FLIGHT_DIP_REF
Description:
Handler: flight
Type: string
Synopsis:
FLIGHT_DIP_REF
Example:
text: FLDI_D
(
attribute: FLDI_A_TEXT
...
length
: 2;
reference: FLIGHT_DIP_REF
)
______________________________________________________________________
FLIGHT_DLY_REF
Reference: FLIGHT_DLY_REF
Description:
Delay for a flight.
Handler: flight
Type: string (Max Length: DELAY_LENGTH)
Synopsis:
FLIGHT_DLY_REF
Example:
Not used.
______________________________________________________________________
205678826.doc
UNCLASSIFIED
Page 227
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
FLIGHT_DRE_REF
Reference: FLIGHT_DRE_REF
Description:
This reference will be used to refere the direction of supplementary
flight level
Handler: flight
Components Usage:
Type: string
Synopsis:
FLIGHT_DRE_REF
Examples:
Not used
______________________________________________________________________
FLIGHT_DRX_REF
Reference: FLIGHT_DRX_REF
Description:
This reference will used to refere the direction of supplementary
flight level
Handler: flight
Components Usage:
Type: string
Synopsis:
FLIGHT_DRX_REF
Examples:
TopLevelShell: CHOICE_SPL
(
Form: MANAGERFORM
(
Form: FORM_SPL
(
RowColumn: RC
(
PREVIEW_CHOICE_TOGGLEBUTTON: Button_Up
(
CreateCallback: trigger (labelPixmap: "up_spl.xbm" set:FALSE)
previewRef
: FLIGHT_DRX_REF
userData
: 0
)
PREVIEW_CHOICE_TOGGLEBUTTON: Button_Equal
(
CreateCallback: trigger (labelPixmap: "Equal.xbm" set:FALSE)
previewRef
: FLIGHT_DRX_REF
userData
: 1
)
PREVIEW_CHOICE_TOGGLEBUTTON: Button_Down
(
CreateCallback: trigger (labelPixmap: "Down.xbm" set:FALSE)
previewRef
: FLIGHT_DRX_REF
userData
: 2
)
)
)
______________________________________________________________________
FLIGHT_ELTI_REF
Reference: FLIGHT_ELTI_REF
Description:
Estimated Time of Arrival of a flight.
Handler: flight
205678826.doc
UNCLASSIFIED
Page 228
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003

Synopsis:
FLIGHT_ELTI_REF
Examples:
One could relate the ESB_ELTI_ATD text field of the presentation object
internal database, named FLIGHT_ELTI_REF.
text: ESB_ELTI_ATD
(
reference: FLIGHT_ELTI_REF
length
: TIME_LENGTH;
)
______________________________________________________________________
FLIGHT_ENS_SECTOR_REF
Reference: FLIGHT_ENS_SECTOR_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_EQM_SSR_REF
Reference: FLIGHT_EQM_SSR_REF
Description:
Secondary Surveillance Radar T.B.D.
to the flight (the modecode).
Handler: flight
Type: string (Max Length: SSR_CODE_LENGTH)
Synopsis:
FLIGHT_SSR_REF
Examples:
One could relate the SSR_FIELD text field of the presentation object
internal database, named FLIGHT_SSR_REF.
text: SSR_FIELD
(
reference: FLIGHT_SSR_REF
...
length: SSR_CODE_LENGTH;
)
______________________________________________________________________
FLIGHT_EQP_BIN_REF
Reference: FLIGHT_EQP_BIN_REF
Description:
EQP of a flight.
Handler: flight
Type: numeric
Synopsis:
FLIGHT_EQP_BIN_REF
205678826.doc
UNCLASSIFIED
Page 229
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Example:
text: ESB_EQP
(
length: 1;
actions
(
set_field_text
(
CURRENT_TEMPLATE,
CURRENT_FIELD,
eqp_value_tab[FLIGHT_EQP_BIN_REF]
)
)
...
)
______________________________________________________________________
FLIGHT_EQP_REF
Reference: FLIGHT_EQP_REF
Description:
EQP of a flight.
Handler: flight
Type: string (Max Length: 1)
Synopsis:
FLIGHT_EQP_REF
Example:
preview: DCL
(
title: 'DCL: DEP CLEARANCE ' + FLIGHT_CALLSIGN_REF
...
field: DCL_EQP_FLD
(
text
(
reference: FLIGHT_EQP_REF
length
: 1
)
help
(
type
: CHOICE
visible: off
values : eqp_value_tab
default:'N'
)
)
______________________________________________________________________
FLIGHT_EQS_BIN_REF
Reference: FLIGHT_EQS_BIN_REF
Description:
EQS of a flight.
Handler: flight
Type: numeric
Synopsis:
FLIGHT_EQS_BIN_REF
Example:
text: ESB_EQS
(
length: 1;
actions
205678826.doc
UNCLASSIFIED
Page 230
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
(
set_field_text
(
CURRENT_TEMPLATE,
CURRENT_FIELD,
eqs_value_tab[FLIGHT_EQS_BIN_REF]
)
)
...
)
______________________________________________________________________
FLIGHT_EQS_REF
Reference: FLIGHT_EQS_REF
Description:
EQS of a flight.
Handler: flight
Synopsis:
FLIGHT_EQS_REF
Example:
preview: DCL
(
title: 'DCL: DEP CLEARANCE ' + FLIGHT_CALLSIGN_REF
...
field: DCL_EQS_FLD
(
text
(
reference:FLIGHT_EQS_REF
length
: 1
)
help
(
type
:
visible:
values :
default:
)
CHOICE
off
eqs_value_tab
'N'
)
______________________________________________________________________
FLIGHT_ETA_REF
Reference: FLIGHT_ETA_REF
Description:
Handler: flight
Synopsis:
FLIGHT_ETA_REF
Examples:
internal database, named FLIGHT_ETA_REF.
text: ESB_ETA_ATD
(
reference: FLIGHT_ETA_REF
length: TIME_LENGTH;
)
205678826.doc
UNCLASSIFIED
Page 231
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
______________________________________________________________________
FLIGHT_ETD_REF
Reference: FLIGHT_ETD_REF
Description:
Estimated Time of Departure of a flight.
Handler: flight
Synopsis:
FLIGHT_ETD_REF
Examples:
One could relate the ESB_ETD_ATD text field of the presentation object
internal database, named FLIGHT_ETD_REF.
text: ESB_ETD_ATD
(
reference: FLIGHT_ETD_REF
length
: TIME_LENGTH;
)
______________________________________________________________________
FLIGHT_ETF_REF
Reference: FLIGHT_ETF_REF
Description:
Estimated time for the flight.
Handler: fligh
Type: string
Synopsis:
FLIGHT_ETF_REF
Examples:
internal database, named FLIGHT_ETF_REF.
preview: TOT
(
label: 'CTOT'
field: CTO_CTOT_FLD
(
label ( default: 'CTOT' )
text
(
reference: FLIGHT_ETF_REF
length
: 4
default : '
'
)
)
)
______________________________________________________________________
FLIGHT_ETI_REF
Reference: FLIGHT_ETI_REF
Description:
the Estimated Time of Inbound.
Handler: flight
Type: string
205678826.doc
UNCLASSIFIED
Page 232
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Synopsis:
FLIGHT_ETI_REF
Examples:
text: EFL_ETI
(
attribute: EFL_A_TEXT
...
length: 3;
event : ABCK
reference: FLIGHT_ETI_REF
)
______________________________________________________________________
FLIGHT_ETL_REF
Reference: FLIGHT_ETL_REF
Description:
Estimated Time T.B.D. for a flight.
Handler: flight
Synopsis:
FLIGHT_ETL_REF
Examples:
One could relate the ESB_ETL_ATD text field of the presentation object
internal database, named FLIGHT_ETL_REF.
text: ESB_ETL_ATD
(
reference: FLIGHT_ETL_REF
length
: TIME_LENGTH
)
______________________________________________________________________
FLIGHT_ETO_AAL_REF
Reference: FLIGHT_ETO_AAL_REF
Description:
Airport Arrival Time for the flight.
Handler: flight
Type: string
Synopsis:
FLIGHT_ETO_AAL_REF
Examples:
internal database, named FLIGHT_ETO_AAL_REF.
text AAL_ETO:
(
reference: FLIGHT_ETO_AAL_REF
length
: 4;
)
______________________________________________________________________
FLIGHT_ETO_ADL_REF
Reference: FLIGHT_ETO_ADL_REF
Description:
Airport Departure Time for the flight.
205678826.doc
UNCLASSIFIED
Page 233
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Handler: flight
Type: string
Synopsis:
FLIGHT_ETO_ADL_REF
Examples:
internal database, named FLIGHT_ETO_ADL_REF.
text ADL_ETO:
(
reference: FLIGHT_ETO_ADL_REF
length
: 4;
)
______________________________________________________________________
FLIGHT_ETO_CIL_REF
Reference: FLIGHT_ETO_CIL_REF
Description:
Cop Inbound Time for the flight.
Handler: flight
Type: string
Synopsis:
FLIGHT_ETO_CIL_REF
Examples:
internal database, named FLIGHT_ETO_CIL_REF.
text CIL_ETO:
(
reference: FLIGHT_ETO_CIL_REF
length
: 4;
)
______________________________________________________________________
FLIGHT_ETO_COL_REF
Reference: FLIGHT_ETO_COL_REF
Description:
Cop Outbound Time for the flight.
Handler: flight
Type: string
Synopsis:
FLIGHT_ETO_COL_REF
Examples:
internal database, named FLIGHT_ETO_COL_REF.
text CIL_ETO:
(
reference: FLIGHT_ETO_COL_REF
length
: 4;
)
______________________________________________________________________
FLIGHT_ETO_FFX_REF
205678826.doc
UNCLASSIFIED
Page 234
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Reference: FLIGHT_ETO_FFX_REF
Description:
Estimated Time Over of the Feeding Fix Point
for a flight.
Handler: flight
Type: string
Synopsis:
FLIGHT_ETO_FFX_REF
Examples:
text: ESB_ETO_FFX
(
...
length: 4;
actions
(
switch: ETO_FX1_TYPE_REF
(
case: T_ACTUAL_CASE
(
set_field_attribute
(
CURRENT_TEMPLATE,
CURRENT_FIELD,
FG_ACTUAL
)
)
default
(
set_field_attribute
(
CURRENT_TEMPLATE,
CURRENT_FIELD,
STRIP_FLD_COLOR
)
)
)
event
: ABCK ( function: FORCED_HOOK()
f.dialog:"DOUBLE_TURN" "choice_ETO_IFX" ""
...
reference: FLIGHT_ETO_FFX_REF
fdm.REP_ID;)
)
______________________________________________________________________
FLIGHT_ETO_FX1_REF
Reference: FLIGHT_ETO_FX1_REF
Description:
Estimated Time Over the Fix number 1 of a flight.
Handler: flight
Synopsis:
FLIGHT_ETO_FX1_REF
Examples:
One could relate the ESB_ETO_ATO_1 text field of the presentation object
internal database, named FLIGHT_ETO_FX1_REF.
text: ESB_ETO_ATO_1
(
reference: FLIGHT_ETO_FX1_REF
length
: TIME_LENGTH
)
______________________________________________________________________
205678826.doc
UNCLASSIFIED
Page 235
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
FLIGHT_ETO_FX2_REF
Description:
Handler: flight
Synopsis:
FLIGHT_ETO_FX2_REF
Examples:
text: ESB_ETO_ATO_2
(
length
: TIME_LENGTH
)
______________________________________________________________________
FLIGHT_ETO_FX3_REF
Description:
Handler: flight
Synopsis:
FLIGHT_ETO_FX3_REF
Examples:
text: ESB_ETO_ATO_3
(
length
: TIME_LENGTH
)
______________________________________________________________________
FLIGHT_ETO_HFX_REF
Reference: FLIGHT_ETO_HFX_REF
Description:
Estimated Time Over the Holding Fix of
a sector for a flight.
Handler: flight
Synopsis:
FLIGHT_ETO_HFX_REF
Examples:
One could relate the HLD_HLDE text field of the presentation object
internal database, named FLIGHT_ETO_HFX_REF.
text: HLD_HLDE
(
205678826.doc
UNCLASSIFIED
Page 236
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
reference: FLIGHT_ETO_HFX_REF
...
length: TIME_LENGTH
)
______________________________________________________________________
FLIGHT_ETO_IFX_REF
Reference: FLIGHT_ETO_IFX_REF
Description:
Estimated Time Over for the Inbound Fix
of a flight.
Handler: flight
Synopsis:
FLIGHT_ETO_IFX_REF
Examples:
One could relate the ESB_IN_ETO_ATO text field of the presentation object
internal database, named FLIGHT_ETO_IFX_REF.
text: ESB_IN_ETO_ATO
(
reference: FLIGHT_ETO_IFX_REF
length
: TIME_LENGTH
)
______________________________________________________________________
FLIGHT_ETO_IN_SEL_REF
Reference: FLIGHT_ETO_IN_REF
Description:
Estimated Time Over of a flight.
Handler: flight
Synopsis:
FLIGHT_ETO_IN_SEL_REF
Examples:
One could relate the SEL_ETO text field of the presentation object
internal database, named FLIGHT_ETO_IN_SEL_REF.
text: SEL_ETO
(
reference: FLIGHT_ETO_IN_SEL_REF
length
: TIME_LENGTH
)
______________________________________________________________________
FLIGHT_ETO_IOF_REF
Reference: FLIGHT_ETO_IOF_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
205678826.doc
UNCLASSIFIED
Page 237
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
______________________________________________________________________
FLIGHT_ETO_NFIX_REF
Reference: FLIGHT_ETO_NFIX_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_ETO_OCOP_REF
Reference: FLIGHT_ETO_OCOP_REF
Description:
Estimated Time Over of the Outbound Cop Point
for a flight.
Handler: flight
Type: string (Max Length: POINT_NAME_LENGTH)
Synopsis:
FLIGHT_ETO_OCOP_REF
Examples:
template: CURSOR_TRAJECTORY_TYPE
(
limit
: 5
priority: TRAJECTORY_PRIORITY
color
: TRAJECTORY_1_COLOR; TRAJECTORY_2_COLOR;TRAJECTORY_3_COLOR;
label:
(
text: FLD_COORD_ETO
(
reference: FLIGHT_ETO_OCOP_REF
length
: 4
...
)
)
)
______________________________________________________________________
FLIGHT_ETO_OFX_REF
Reference: FLIGHT_ETO_OFX_REF
Description:
Estimated Time Over of the Outbound Fix Point
for a flight.
Handler: flight
Synopsis:
FLIGHT_ETO_OFX_REF
Examples:
One could relate the ESB_OUT_ETO_ATO text field of the presentation object
internal database, named FLIGHT_ETO_OFX_REF.
text: ESB_OUT_ETO_ATO
(
reference: FLIGHT_ETO_OFX_REF
length
: POINT_NAME_LENGTH;
)
205678826.doc
UNCLASSIFIED
Page 238
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
______________________________________________________________________
FLIGHT_ETO_SFL_REF
Reference: FLIGHT_ETO_SFL_REF
Description:
Handler: flight
Type: string
Synopsis:
FLIGHT_ETO_SFL_REF
Example:
text: SIL_ETO
(
attribute: SIL_A_TEXT
length
: 4;
...
reference: FLIGHT_ETO_SFL_REF
)
______________________________________________________________________
FLIGHT_EXS_SECTOR_REF
Reference: FLIGHT_EXS_SECTOR_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_FCF_REF
Reference: FLIGHT_FCF_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_FCK_REF
Reference: FLIGHT_FCK_REF
Description:
This reference is used to display the Formality Check information.
Handler: flight
Type: string (Max Length: FC_LENGTH)
Synopsis:
FLIGHT_FCK_REF
Example:
choice: FCK
(
205678826.doc
UNCLASSIFIED
Page 239
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
title : FLIGHT_CALLSIGN_REF
legend:'FCK'
field : FCK_FLD
(
text
(
reference: FLIGHT_FCK_REF
length
: 9
)
)
)
______________________________________________________________________
FLIGHT_FFX_REF
Reference: FLIGHT_FFX_REF
Description:
Feeding Fix Point Name for a flight.
Handler: flight
Synopsis:
FLIGHT_FFX_REF
Example:
One could relate the FLDA_SEC_FIELD text field of the presentation object
internal database, named FLIGHT_SCT_REF.
text: FLDA_SEC_FIELD
(
...
length
: 2;
reference: FLIGHT_SCT_REF
)
______________________________________________________________________
FLIGHT_FIR_EXIT_POINT_REF
Reference: FLIGHT_FIR_EXIT_POINT_REF
Description:
the Fir exit point.
Handler: flight
Type: string (Max Length: EXIT_POINT_LENGTH)
Synopsis:
FLIGHT_FIR_EXIT_POINT_REF
Examples:
Not used.
______________________________________________________________________
FLIGHT_FIX_01_REF
Reference: FLIGHT_FIX_01_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
205678826.doc
UNCLASSIFIED
Page 240
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
______________________________________________________________________
FLIGHT_FIX_02_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_FIX_03_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_FIX_04_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_FIX_05_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_FIX_06_REF
Description:
Handler: flight
Type:
205678826.doc
UNCLASSIFIED
Page 241
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Synopsis:
Example:
______________________________________________________________________
FLIGHT_FIX_07_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_FIX_08_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_FIX_X1_REF
Reference: FLIGHT_FIX_X1_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_FIX_X2_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_FIX_X3_REF
Description:
Handler: flight
205678826.doc
UNCLASSIFIED
Page 242
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003

Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_FIX_X4_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_FIX_X5_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_FIX_X6_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_FIX_X7_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_FIX_X8_REF
Description:
205678826.doc
UNCLASSIFIED
Page 243
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_FLDA_SCROLL_LIST_REF
Reference: FLIGHT_FLDA_SCROLL_LIST_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_FLT_REF
Reference: FLIGHT_FLT_REF
Description:
Not implemented.
______________________________________________________________________
FLIGHT_FLY_STATUS_REF
Reference: FLIGHT_FLY_STATUS_REF
Description:
Handler: flight
Type: numeric
Synopsis:
FLIGHT_FLY_STATUS_REF
Example:
event: ABCK
(
switch: flight(FLIGHT_FLY_STATUS_REF).num
(
...
)
)
______________________________________________________________________
FLIGHT_FPLM_MSG_REF
Reference: FLIGHT_FPLM_MSG_REF
Description:
Handler: flight
Type: string
Synopsis:
FLIGHT_FPLM_MSG_REF
Example:
component: fplm 1
(
205678826.doc
UNCLASSIFIED
Page 244
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
...
text: FPLM_MSG
(
length
: FPLM_TOT_CHARS_IN_ROW;
reference: FLIGHT_FPLM_MSG_REF
...
)
______________________________________________________________________
FLIGHT_FR_REF
Reference: FLIGHT_FR_REF
Description:
Flight Roule Type for a flight.
Handler: flight
Type: string (Max Length: FR_LENGTH)
Synopsis:
FLIGHT_FR_REF
Examples:
One could relate the ARR_FR text field of the presentation object
internal database, named FLIGHT_FR_REF.
text: ARR_FR
(
reference: FLIGHT_FR_REF
length
: FR_LENGTH;
)
______________________________________________________________________
FLIGHT_FSSBIN_REF
Reference: FLIGHT_FSSBIN_REF
Description:
Handler: flight
Type: string
Synopsis:
FLIGHT_FSSBIN_REF
Example:
table: ARR
(
...
list:
(
...
entry:
(
...
text: ARR_FS
(
attribute: ARR_A_TEXT
length
: 2;
initial : 'ARR_FS'
...
actions
(
set_field_text
(
CURRENT_TEMPLATE,
CURRENT_FIELD,
status_tab[FLIGHT_FSSBIN_REF]
)
205678826.doc
UNCLASSIFIED
Page 245
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
)
)
)
______________________________________________________________________
FLIGHT_FSS_REF
Reference: FLIGHT_FSS_REF
Description:
Handler: flight
Type: string (Max Lenght: FS_LENGTH)
Synopsis:
FLIGHT_FSS_REF
Example:
One could relate the FSS_FIELD text field of the presentation object
internal database, named FLIGHT_FSS_REF.
text: FSS_FIELD
(
...
length: 2;
reference: FLIGHT_FSS_REF
)
______________________________________________________________________
FLIGHT_FVF_REF
Reference: FLIGHT_FVF_REF
Description:
This reference will be used to refere the
FDP Validity Flag
Handler: flight
Components Usage:
Type: string
Synopsis:
FLIGHT_FVF_REF
Example:
Not used
______________________________________________________________________
FLIGHT_FX1_REF
Reference: FLIGHT_FX1_REF
Description:
Fix Point 1 for a flight.
Handler: flight
Synopsis:
FLIGHT_FX1_REF
Examples:
One could relate the ESB_FIX_1 text field of the presentation object
internal database, named FLIGHT_FX1_REF.
text: ESB_FIX_1
(
205678826.doc
UNCLASSIFIED
Page 246
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
reference: FLIGHT_FX1_REF
length
______________________________________________________________________
FLIGHT_FX2_REF
Description:
Handler: flight
Synopsis:
FLIGHT_FX2_REF
Examples:
text: ESB_FIX_2
(
length
)
______________________________________________________________________
FLIGHT_FX3_REF
Description:
Handler: flight
Synopsis:
FLIGHT_FX3_REF
Examples:
text: ESB_FIX_3
(
length
)
______________________________________________________________________
FLIGHT_GOS_REF
Reference: FLIGHT_GOS_REF
Description:
Handler: flight
Type: string
Synopsis:
FLIGHT_GOS_REF
Example:
text: ESB_G
(
205678826.doc
UNCLASSIFIED
Page 247
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
...
length: 1;
actions
(
if FLIGHT_GOS_REF = "G"
then set_field_text
(
CURRENT_TEMPLATE,
CURRENT_FIELD,
' '
)
endif
)
...
reference: FLIGHT_GOS_REF
______________________________________________________________________
FLIGHT_GROUND_SPEED_REF
Reference: FLIGHT_GROUND_SPEED_REF
Description:
Handler: flight
Type:
Synopsis:
FLIGHT_GROUND_SPEED_REF
Example:
text: FHI_GSP
(
attribute: A_TEXT
...
length: 3;
event: ABCK
(
f.dialog: DOUBLE_TURN choice_SPD "" fdm.SPD_ID;
)
reference: FLIGHT_GROUND_SPEED_REF
)
______________________________________________________________________
FLIGHT_HDGUN_REF
Reference: FLIGHT_HDGUN_REF
Description:
Heading Unit for the MHDG field.
Handler: flight
Components Usage:
Type: string
Synopsis:
FLIGHT_HDGUN_REF
Example:
text: MLB_UN_MHDG
(
...
length: 6;
actions
(
set_field_text
(
CURRENT_HEADER_TEMPLATE,
CURRENT_FIELD,
mhdg_unit_tab[FLIGHT_HDGUN_REF]
)
)
205678826.doc
UNCLASSIFIED
Page 248
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
)
______________________________________________________________________
FLIGHT_HDG_REF
Reference: FLIGHT_HDG_REF
Description:
Handler: flight
Type: string
Synopsis:
FLIGHT_HDG_REF
Example:
choice: HDG
(
legend:'HDG'
field : HDG_FLD
(
text
(
reference: FLIGHT_HDG_REF
length
: 3
values
: 5 to 360 step 5
default : 180
)
)
)
______________________________________________________________________
FLIGHT_HFX_REF
Reference: FLIGHT_HFX_REF
Description:
Holding Fix name for the flight.
Handler: flight
Synopsis:
FLIGHT_HFX_REF
Examples:
text: ESB_FFX_H
(
...
length
: 1;
reference: FLIGHT_HFX_REF
)
______________________________________________________________________
FLIGHT_HLD_FX1_REF
Reference: FLIGHT_HLD_FX1_REF
Description:
Holding Fix number 1 for the flight.
Handler: flight
Type: string (Max Length: FLAG_LENGTH)
Synopsis:
FLIGHT_HLD_FX1_REF
205678826.doc
UNCLASSIFIED
Page 249
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Examples:
One could relate the ESB_H_1 text field of the presentation object
internal database, named FLIGHT_HLD_FX1_REF.
text: ESB_H_1
(
reference: FLIGHT_HLD_FX1_REF
length
: FLAG_LENGTH;
)
______________________________________________________________________
FLIGHT_HLD_FX2_REF
Description:
Handler: flight
Synopsis:
FLIGHT_HLD_FX2_REF
Examples:
text: ESB_H_2
(
length
: FLAG_LENGTH;
)
______________________________________________________________________
FLIGHT_HLD_FX3_REF
Description:
Handler: flight
Synopsis:
FLIGHT_HLD_FX3_REF
Examples:
text: ESB_H_3
(
length
: FLAG_LENGTH;
)
______________________________________________________________________
FLIGHT_HLD_IFX_REF
Reference: FLIGHT_HLD_IFX_REF
Description:
Holding Inbound Fix for the flight.
Handler: flight
205678826.doc
UNCLASSIFIED
Page 250
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003

Synopsis:
FLIGHT_HLD_IFX_REF
Examples:
One could relate the ESB_IN_H text field of the presentation object
internal database, named FLIGHT_HLD_IFX_REF.
text: ESB_IN_H
(
...
length
: 1;
reference: FLIGHT_HLD_IFX_REF
)
______________________________________________________________________
FLIGHT_HLD_OFX_REF
Reference: FLIGHT_HLD_OFX_REF
Description:
Holding Out Fix for the flight.
Handler: flight
Synopsis:
FLIGHT_HLD_OFX_REF
Examples:
One could relate the ESB_OUT_H text field of the presentation object
internal database, named FLIGHT_HLD_OFX_REF.
text: ESB_OUT_H
(
reference: FLIGHT_HLD_OFX_REF
length
: FLAG_LENGTH;
)
______________________________________________________________________
FLIGHT_HLD_STATUS_REF
Reference: FLIGHT_HLD_STATUS_REF
Description:
This reference will be used to refere holding status information
Handler: flight
Components Usage:
Type: string
Synopsis:
FLIGHT_HLD_STATUS_REF
Examples:
Not used
______________________________________________________________________
FLIGHT_IASUN_REF
Reference: FLIGHT_IASUN_REF
Description:
Indicated Air Speed Unit for the flight.
Handler: flight
Components Usage:
Type: string
205678826.doc
UNCLASSIFIED
Page 251
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Synopsis:
FLIGHT_IASUN_REF
Example:
text: MLB_UN_IAS
(
...
length: 5;
actions
(
set_field_text
(
CURRENT_FIELD,
ias_unit_tab[FLIGHT_IASUN_REF]
)
)
)
______________________________________________________________________
FLIGHT_IAS_REF
Reference: FLIGHT_IAS_REF
Description:
Indicated Air Speed for the flight.
Handler: flight
Components Usage:
Type: string
Synopsis:
FLIGHT_IAS_REF
Example:
text: MLB_IAS
(
...
length: 5;
actions
(
switch: FLIGHT_IASVD_REF
(
case: 0 (set_field_attribute (CURRENT_HEADER_TEMPLATE, CURRENT_FIELD, NOT_VALID_VAL))
case: 1 (set_field_attribute (CURRENT_HEADER_TEMPLATE, CURRENT_FIELD, VALID_VAL))
case: 2 (set_field_attribute (CURRENT_HEADER_TEMPLATE, CURRENT_FIELD, EXPIRED_VAL))
)
)
reference: FLIGHT_IAS_REF
)
______________________________________________________________________
FLIGHT_ICOP_REF
Reference: FLIGHT_ICOP_REF
Description:
Cop Inbound Name for the flight.
Handler: flight
Type: string
Synopsis:
FLIGHT_ICOP_REF
Examples:
internal database, named FLIGHT_ICOP_REF.
text CIL_ICOP:
205678826.doc
UNCLASSIFIED
Page 252
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
(
reference: FLIGHT_ICOP_REF
length
: 5;
)
______________________________________________________________________
FLIGHT_IFX_REF
Reference: FLIGHT_IFX_REF
Description:
Inbound Fix Point name for a flight.
Handler: flight
Synopsis:
FLIGHT_IFX_REF
Examples:
One could relate the FLDA_FIX_FIELD text field of the presentation object
internal database, named FLIGHT_IFX_REF.
text: FLDA_FIX_FIELD
(
reference: FLIGHT_IFX_REF
...
length
)
______________________________________________________________________
FLIGHT_IN_HOOK_REF
Reference: FLIGHT_IN_HOOK_REF
Description:
This reference is used to refer to if a
flight is in hook.
Handler: flight
Type: string (Max Length: PLANNED_TAS_LENGTH)
Synopsis:
FLIGHT_IN_HOOK_REF
Examples:
One could relate the ESB_TAS text field of the presentation object
internal database, named FLIGHT_IN_HOOK_REF.
text: ESB_TAS
(
reference: FLIGHT_IN_HOOK_REF
...
length: PLANNED_TAS_LENGTH;
)
______________________________________________________________________
FLIGHT_ISID_REF
Reference: FLIGHT_ISID_REF
Description:
Standard Instrumental Departure for the flight.
Handler: flight
Type: string (Max Length: ISID_LENGTH)
Synopsis:
205678826.doc
UNCLASSIFIED
Page 253
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
FLIGHT_ISID_REF
Examples:
One could relate the DEP_SID text field of the presentation object
internal database, named FLIGHT_SID_REF.
component: dep 1
(
text: DEP_ISID
(
attribute: DEP_A_TEXT
length
: 5;
event
: ABCK (function: HOOKING ())
...
reference: FLIGHT_ISID_REF
)
)
______________________________________________________________________
FLIGHT_JOINING_SYMBOL_REF
Reference: FLIGHT_JOINING_SYMBOL_REF
Description:
Handler: flight
Type:
Synopsis:
FLIGHT_JOINING_SYMBOL_REF
Example:
assign: JOINING_BOX_WIDTH tsh;
assign: JOINING_X0 wrx-JOINING_BOX_WIDTH;
assign: wrx wrx-JOINING_BOX_WIDTH;
symbol: @TABLE_NAME@_JOINING
(
event: ABCK
(function: JOINING ())
reference: FLIGHT_JOINING_SYMBOL_REF
...
)
______________________________________________________________________
FLIGHT_LARW_REF
Reference: FLIGHT_LARW_REF
Description:
Last Airway for a flight.
Handler: flight
Type: string (Max Length: LAST_AIRWAY_LENGTH)
Synopsis:
FLIGHT_LARW_REF
Example:
This reference is never used.
______________________________________________________________________
FLIGHT_LASTFIX_REF
Reference: FLIGHT_LASTFIX_REF
Description:
Handler: flight
Type: string
205678826.doc
UNCLASSIFIED
Page 254
E000IES0-09SUM
UNCLASSIFIED
Issue
Date:
D
28/02/2003
Synopsis:
FLIGHT_LASTFIX_REF
Example:
text: SIL_OUT
(
attribute: SIL_A_TEXT
length
: 3;
event
: ABCK
(
f.dialog:"SINGLE_DATA_TURN"
)
...
reference: FLIGHT_LASTFIX_REF
)
"choice_FDD_QUICK" ""
fdm.FLD_ID;
______________________________________________________________________
FLIGHT_LINE_REF
Reference: FLIGHT_LINE_REF
Description:
Flight Line for the flight.
Handler: flight
Type: string
Synopsis:
FLIGHT_LINE_REF
Examples:
internal database, named FLIGHT_LINE_REF.
text HLD_NR:
(
reference: FLIGHT_LINE_REF
length
: 2;
)
______________________________________________________________________
FLIGHT_LSN_REF
Reference: FLIGHT_LSN_REF
Description:
Handler: flight
Type: string (Max Length:)
Synopsis:
FLIGHT_LSN_REF
Example:
preview: ASQ
(
title :'ASQ: ARR SEQUENCE ' + FLIGHT_CALLSIGN_REF
warning:(line : 2)
...
field : ASQ_SEL_FLD
(
text
(
reference: FLIGHT_LSN_REF
length
: 2
)
)
)
205678826.doc
UNCLASSIFIED
Page 255
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
______________________________________________________________________
FLIGHT_LVL_REF
Reference: FLIGHT_LVL_REF
Description:
Last Vac Level for the flight.
Handler: flight
Synopsis:
FLIGHT_LVL_REF
Examples:
One could relate the HLD_LSV text field of the presentation object
internal database, named FLIGHT_LVL_REF.
text: HLD_LSV
(
reference: FLIGHT_LVL_REF
...
)
______________________________________________________________________
FLIGHT_MAF_REF
Reference: FLIGHT_MAF_REF
Description:
Military Approval Flag
Handler: flight
Components Usage:
Type: string
Synopsis:
FLIGHT_MAF_REF
Example:
text: SCL_MILITARY_APPROVAL
(
attribute: SCL_A_TEXT
...
length: 1;
actions
(
set_field_text
(
CURRENT_TEMPLATE,
CURRENT_FIELD,
maf_value_tab[FLIGHT_MAF_REF]
)
)
)
______________________________________________________________________
FLIGHT_MA_FIX_REF
Reference: FLIGHT_MA_MIX_REF
Description:
Missed Approach for the flight.
Handler: flight
Type: string
Synopsis:
FLIGHT_MA_FIX_REF
205678826.doc
UNCLASSIFIED
Page 256
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Examples:
internal database, named FLIGHT_MA_FIX_REF.
preview: MIS
(
title: 'MIS: MISSED APPROACH ' + FLIGHT_CALLSIGN_REF
...
field: MIS_MAF_FLD
(
label (default: 'MAF' )
text
(
reference: FLIGHT_MA_FIX_REF
length
: 5
)
)
)
______________________________________________________________________
FLIGHT_MA_LEV_REF
Reference: FLIGHT_MA_LEV_REF
Description:
Missed Approach for the flight.
Handler: flight
Type: string
Synopsis:
FLIGHT_MA_LEV_REF
Examples:
internal database, named FLIGHT_MA_LEV_REF.
preview: MIS
(
title: 'MIS: MISSED APPROACH ' + FLIGHT_CALLSIGN_REF
...
field: MIS_MAL_FLD
(
label (default: 'MAL' )
text
(
reference: FLIGHT_MA_LEV_REF
length
: 3
)
)
)
______________________________________________________________________
FLIGHT_METAIS_AIR_LOC_REF
Reference: FLIGHT__REF
Description:
Meteorological Aeronautical Information Service
Air Local Message for the flight.
Handler: flight
Type: string
Synopsis:
FLIGHT_METAIS_AIR_LOC_REF
Examples:
205678826.doc
UNCLASSIFIED
Page 257
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003

internal database, named FLIGHT_METAIS_AIR_LOC_REF.
text
(
reference: FLIGHT_METAIS_AIR_LOC_REF
length
: 4;
)
______________________________________________________________________
FLIGHT_METAIS_DB_KEY_REF
Reference: FLIGHT_METAIS_DB_KEY_REF
Description:
Handler: flight
Type:
Synopsis:
FLIGHT_METAIS_DB_KEY_REF
Example:
text: TITLE_REF_FIELD
(
attribute: @TABLE_NAME@_A_TITLE_TEXT
...
length: 4;
reference: FLIGHT_METAIS_DB_KEY_REF
)
______________________________________________________________________
FLIGHT_METAIS_FIR_REF
Description:
Flight Information Region for the flight.
Handler: flight
Type: string
Synopsis:
FLIGHT_METAIS_FIR_REF
Examples:
internal database, named FLIGHT_METAIS_FIR_REF.
text
(
reference: FLIGHT_METAIS_FIR_REF
length
: 4;
)
______________________________________________________________________
FLIGHT_METAIS_LOC_REF
Description:
Local Message for the flight.
Handler: flight
Type: string
Synopsis:
205678826.doc
UNCLASSIFIED
Page 258
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
FLIGHT_METAIS_LOC_REF
Examples:
internal database, named FLIGHT_METAIS_LOC_REF.
text
(
reference: FLIGHT_METAIS_LOC_REF
length
: 15;
)
______________________________________________________________________
FLIGHT_METAIS_NAVAID_REF
Description:
Navigational Aid for the flight.
Handler: flight
Type: string
Synopsis:
FLIGHT_METAIS_NAVAID_REF
Examples:
internal database, named FLIGHT_METAIS_NAVAID_REF.
text
(
reference: FLIGHT_METAIS_NAVAID_REF
length
: 15;
)
______________________________________________________________________
FLIGHT_MET_AIS_MSG_REF
Reference: FLIGHT_MET_AIS_MSG_REF
Description:
Handler: flight
Type:
Synopsis:
FLIGHT_MET_AIS_MSG_REF
Example:
text: MET_AIS_MSG
(
...
length
: @TABLE_NAME@_TOT_CHARS_IN_ROW;
reference: FLIGHT_MET_AIS_MSG_REF
)
______________________________________________________________________
FLIGHT_MHDG_REF
Reference: FLIGHT_MHDG_REF
Description:
Heading for the flight.
Handler: flight
Components Usage:
205678826.doc
UNCLASSIFIED
Page 259
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Type: string
Synopsis:
FLIGHT_MHDG_REF
Example:
text: MLB_MHDG
(
...
length: 5;
actions
(
switch: FLIGHT_HDGVD_REF
(
)
)
reference: FLIGHT_MHDG_REF
)
______________________________________________________________________
FLIGHT_MIL_REF
Reference: FLIGHT_MIL_REF
Description:
Handler: flight
Type: string
Synopsis:
Example:
table: FLDI
(
list:
(
entry:
(
text: FLDI_M
(
attribute: FLDI_A_TEXT
length
: 1;
...
reference: FLIGHT_MIL_REF
)
)
)
)
______________________________________________________________________
FLIGHT_MODENSSR_REF
Reference: FLIGHT_MODENSSR_REF
Description:
Handler: flight
Type: string
Synopsis:
FLIGHT_MODENSSR_REF
Example:
preview: SSR
(
field: NSSR_MODESSR_FLD
(
label (default: 'NMODE' )
205678826.doc
UNCLASSIFIED
Page 260
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
text
(
reference: FLIGHT_MODENSSR_REF
length
: 1
default :'A'
)
)
______________________________________________________________________
FLIGHT_MODEPSSR_REF
Reference: FLIGHT_MODEPSSR_REF
Description:
Handler: flight
Type: string
Synopsis:
FLIGHT_MODEPSSR_REF
Example:
preview: SSR
(
field: PSSR_MODESSR_FLD
(
label (default: 'PMODE' )
text
(
reference: FLIGHT_MODEPSSR_REF
length
: 1
default :'A'
)
)
)
______________________________________________________________________
FLIGHT_MODESSR_REF
Reference: FLIGHT_MODESSR_REF
Description:
Handler: flight
Type: string
Synopsis:
FLIGHT_MODESSR_REF
Example:
preview: RCR
(
label: 'EN-ROUTE REROUTING'
field: RCR_MODESSR_FLD
(
label (default: 'MODE' )
text
(
reference: FLIGHT_MODESSR_REF
length
: 1
default :'A'
)
)
______________________________________________________________________
FLIGHT_MTCD_REF
205678826.doc
UNCLASSIFIED
Page 261
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Reference: FLIGHT_MTCD_REF
Description:
Handler: flight
Type: string
Synopsis:
FLIGHT_MTCD_REF
Example:
text: ESB_C
(
length: 1;
...
actions
(
set_field_text
(
CURRENT_TEMPLATE,
CURRENT_FIELD,
mtcd_value_tab[FLIGHT_MTCD_REF]
)
set_field_attribute
(
CURRENT_TEMPLATE,
CURRENT_FIELD,
STRIP_DA_COLOR
)
)
)
______________________________________________________________________
FLIGHT_MTS_REF
Reference: FLIGHT_MTS_REF
Description:
This reference will be used to refere my track
status information
Handler: flight
Components Usage:
Type: string
Synopsis:
FLIGHT_MTS_REF
Examples:
Not used
______________________________________________________________________
FLIGHT_NEXT_FREQ_REF
Reference: FLIGHT_NEXT_FREQ_REF
Description:
Handler: flight
Type:
Synopsis:
FLIGHT_NEXT_FREQ_REF
Example:
text: SCL_NEXT_FREQ
(
...
length: 6;
event : ABCK
205678826.doc
UNCLASSIFIED
Page 262
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
reference: FLIGHT_NEXT_FREQ_REF
)
______________________________________________________________________
FLIGHT_NEXT_GEO_SECT_REF
Reference: FLIGHT_NEXT_GEO_SECT_REF
Description:
Used to refer to the Next Geo Sector.
Handler: flight
Type:
Synopsis:
FLIGHT_NEXT_GEO_SECT_REF
Example:
One could relate the ESB_SCT text field of the presentation object
internal database, named FLIGHT_NEXT_GEO_SECT_REF.
text: ESB_SCT
(
...
length: 3;
reference: FLIGHT_NEXT_GEO_SECT_REF
)
______________________________________________________________________
FLIGHT_NEXT_SECT_REF
Reference: FLIGHT_NEXT_SECT_REF
Description:
Handler: flight
Type:
Synopsis:
FLIGHT_NEXT_SECT_REF
Example:
table: ESB
(
list:
(
entry:
(
text: ESB_SCT
(
...
length
: 3;
reference: FLIGHT_NEXT_SECT_REF
)
)
)
)
______________________________________________________________________
FLIGHT_NFIX_REF
Reference: FLIGHT_NFIX_REF
Description:
Handler: flight
Type:
205678826.doc
UNCLASSIFIED
Page 263
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Synopsis:
Example:
______________________________________________________________________
FLIGHT_NFR_REF
Reference: FLIGHT_NFR_REF
Description:
This reference is used to refere the next fir ( 4 characters )
Handler: flight
Components Usage: trajectory
Type:
Synopsis:
Examples:
______________________________________________________________________
FLIGHT_NOALPHA_SCT_REF
Reference: FLIGHT_NOALPHA_SCT_REF
Description:
This reference is used to refere the sectors.
Handler: flight
Type: string
Synopsis:
FLIGHT_NOALPHA_SCT_REF
Examples:
internal database, named FLIGHT_NOALPHA_SCT_REF.
text TOC_LEV_FLD:
(
reference: FLIGHT_NOALPHA_SCT_REF
length
: 2;
)
______________________________________________________________________
FLIGHT_NSSR_REF
Reference: FLIGHT_NSSR_REF
Description:
Secondary Surveillance Radar (T.B.D.) assigned code
to the flight.
Handler: flight
Synopsis:
FLIGHT_NSSR_REF
Examples:
internal database, named FLIGHT_NSSR_REF.
text: NSSR_FIELD_REF
(
reference: FLIGHT_NSSR_REF
...
)
______________________________________________________________________
205678826.doc
UNCLASSIFIED
Page 264
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
FLIGHT_NTS_REF
Reference: FLIGHT_NTS_REF
Description:
This reference will be used to refere next track status
information
Handler: flight
Components Usage:
Type: string
Synopsis:
FLIGHT_NTS_REF
Examples:
Not used
______________________________________________________________________
FLIGHT_OBT_REF
Reference: FLIGHT_OBT_REF
Description:
Handler: flight
Synopsis:
FLIGHT_OBT_REF
Examples:
internal database, named FLIGHT_OBT_REF.
text: ESB_ETA_ATD
(
reference: FLIGHT_OBT_REF
length
: TIME_LENGTH;
)
______________________________________________________________________
FLIGHT_OCOP_REF
Reference: FLIGHT_OCOP_REF
Description:
Cop Outbound Name for the flight.
Handler: flight
Type: string
Synopsis:
FLIGHT_OCOP_REF
Examples:
internal database, named FLIGHT_OCOP_REF.
text CIL_OCOP:
(
reference: FLIGHT_OCOP_REF
length
: 5;
)
______________________________________________________________________
FLIGHT_OFX_REF
Reference: FLIGHT_OFX_REF
205678826.doc
UNCLASSIFIED
Page 265
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Description:
Outbound Fix Point name for a flight.
Handler: flight
Synopsis:
FLIGHT_OFX_REF
Examples:
One could relate the ESB_OUT_FIX text field of the presentation object
internal database, named FLIGHT_OFX_REF.
text: ESB_OUT_FIX
(
reference: FLIGHT_OFX_REF
...
length
)
______________________________________________________________________
FLIGHT_OLDI_CRC_REF
Reference: FLIGHT_OLDI_CRC_REF
Description:
the Inbound Crossing Condition.
Handler: flight
Type: string (Max Length: CRC_LENGTH)
Synopsis:
FLIGHT_OLDI_CRC_REF
Examples:
Not used.
______________________________________________________________________
FLIGHT_OLDI_MSG_REF
Reference: FLIGHT_OLDI_MSG_REF
Description:
Handler: flight
Type: string
Synopsis:
FLIGHT_OLDI_MSG_REF
Example:
component: oldi 1
(
text: OLDI_MSG
(
...
length
: OLDI_TOT_CHARS_IN_ROW;
reference: FLIGHT_OLDI_MSG_REF
)
)
______________________________________________________________________
FLIGHT_OLDI_PEL_REF
Reference: FLIGHT_OLDI_PEL_REF
205678826.doc
UNCLASSIFIED
Page 266
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Description:
the Inbound Coordination Level.
Handler: flight
Synopsis:
FLIGHT_OLDI_PEL_REF
Examples:
text: SCL_ENTRY_COO_FL
(
...
length: 3;
reference: FLIGHT_OLDI_PEL_REF
)
______________________________________________________________________
FLIGHT_OLDI_SPL_REF
Reference: FLIGHT_OLDI_SPL_REF
Description:
the Inbound Extimated Level.
Handler: flight
Synopsis:
FLIGHT_OLDI_SPL_REF
Examples:
text: SCL_SUP_FL_1
(
...
length
: 3;
event
: ABCK
reference: FLIGHT_OLDI_SPL_REF
)
______________________________________________________________________
FLIGHT_PAN_SSR_REF
Reference: FLIGHT_PAN_SSR_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_PAS_ACT_TIME_REF
Reference: FLIGHT_PAS_ACT_TIME_REF
Description:
Handler: flight
Type:
Synopsis:
FLIGHT_PAS_ACT_TIME_REF
205678826.doc
UNCLASSIFIED
Page 267
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Example:
component: browse 1
(
table: BROWSE
(
list:
(
entry:
(
text: BROWSE_ACT
(
attribute: BROWSE_A_TEXT
...
length
: 4;
reference: FLIGHT_PAS_ACT_TIME_REF
)
)
)
)
)
______________________________________________________________________
FLIGHT_PAS_AIRT_REF
Reference: FLIGHT_PAS_AIRT_REF
Description:
Handler: flight
Type: string
Synopsis:
FLIGHT_PAS_AIRT_REF
Example:
preview: IFA
(
title: 'IFA: FPL PAS. AM ' + FLIGHT_CALLSIGN_REF
field: IFA_TYPE_FLD
(
label (default: 'TYPE' )
text
(
reference: FLIGHT_PAS_AIRT_REF
length
: 4
)
)
)
______________________________________________________________________
FLIGHT_PAS_CALLSIGN_REF
Reference: FLIGHT_PAS_CALLSIGN_REF
Description:
Handler: flight
Type: string
Synopsis:
FLIGHT_PAS_CALLSIGN_REF
Example:
component: browse 1
(
table: BROWSE
(
list:
(
entry:
(
205678826.doc
UNCLASSIFIED
Page 268
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
)
)
D
28/02/2003
text: BROWSE_CALLSIGN
(
length: 8;
...
event: IBCK
(
function: FORCED_HOOK()
function: POPPINGUP( PASSIVE_id )
)
...
reference: FLIGHT_PAS_CALLSIGN_REF
)
)
______________________________________________________________________
FLIGHT_PAS_DEP_REF
Reference: FLIGHT_PAS_DEP_REF
Description:
Handler: flight
Type: string
Synopsis:
FLIGHT_PAS_DEP_REF
Example:
component: browse 1
(
table: BROWSE
(
list:
(
entry:
(
text: BROWSE_DEP
(
length: 4;
...
reference: FLIGHT_PAS_DEP_REF
)
)
)
)
)
______________________________________________________________________
FLIGHT_PAS_DES_REF
Reference: FLIGHT_PAS_DES_REF
Description:
Handler: flight
Type: string
Synopsis:
FLIGHT_PAS_DES_REF
Example:
component: browse 1
(
table: BROWSE
(
list:
(
205678826.doc
UNCLASSIFIED
Page 269
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
entry:
(
text: BROWSE_DES
(
length: 4;
...
event: ABCK
reference: FLIGHT_PAS_DES_REF
)
)
)
)
______________________________________________________________________
FLIGHT_PAS_DISPLACEMENT
Reference: FLIGHT_PAS_DISPLACEMENT
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_PAS_ELTI_REF
Reference: FLIGHT_PAS_ELTI_REF
Description:
Handler: flight
Type: string
Synopsis:
FLIGHT_PAS_ELTI_REF
Example:
preview: IFA
(
title: 'IFA: FPL PAS. AM ' + FLIGHT_CALLSIGN_REF
field: IFA_ELTI_FLD
(
label (default: 'ELTI' )
text
(
reference: FLIGHT_PAS_ELTI_REF
length
: 4
)
)
)
______________________________________________________________________
FLIGHT_PAS_ETF_REF
Reference: FLIGHT_PAS_FFT_REF
Description:
Handler: flight
Type:
Synopsis:
FLIGHT_PAS_ETF_REF
205678826.doc
UNCLASSIFIED
Page 270
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Example:
preview: FFI
(
label:'FAST FLIGHT INBOUND'
field: FFI_ETF_FLD
(
label (default: 'ETF' )
text
(
reference: FLIGHT_PAS_ETF_REF
length
: 4
)
)
)
______________________________________________________________________
FLIGHT_PAS_ETO_REF
Reference: FLIGHT_PAS_ETO_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_PAS_FFT_REF
Reference: FLIGHT_PAS_FFT_REF
Description:
Handler: flight
Type:
Synopsis:
FLIGHT_PAS_FFT_REF
Example:
component: browse 1
(
table: BROWSE
(
list:
(
entry:
(
text: BROWSE_FFT
(
...
length
: 4;
reference: FLIGHT_PAS_FFT_REF
)
)
)
)
)
______________________________________________________________________
FLIGHT_PAS_FLG_RUL_REF
Reference: FLIGHT_PAS_FLG_RUL_REF
Description:
-
205678826.doc
UNCLASSIFIED
Page 271
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Handler: flight
Type:
Synopsis:
FLIGHT_PAS_FLG_RUL_REF
Example:
component: browse 1
(
table: BROWSE
(
list:
(
entry:
(
text: BROWSE_FR
(
event: ABCK
...
length
: 2;
reference: FLIGHT_PAS_FLG_RUL_REF
)
)
)
)
)
______________________________________________________________________
FLIGHT_PAS_FLTYPE_REF
Reference: FLIGHT_FLTYPE_REF
Description:
Handler: flight
Type:
Synopsis:
FLIGHT_PAS_FLTYPE_REF
Example:
component: browse 1
(
table: BROWSE
(
list:
(
entry:
(
text: BROWSE_TYPE
(
...
length
: 4;
reference: FLIGHT_PAS_FLTYPE_REF
)
)
)
)
)
______________________________________________________________________
FLIGHT_PAS_FLT_REF
Reference: FLIGHT_PAS_FLT_REF
Description:
Handler: flight
Type:
205678826.doc
UNCLASSIFIED
Page 272
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Synopsis:
Example:
______________________________________________________________________
FLIGHT_PAS_FS_REF
Reference: FLIGHT_PAS_FS_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_PAS_HEADER_CALLSIGN_REF
Reference: FLIGHT_PAS_HEADER_CALLSIGN_REF
Description:
Handler: flight
Type: string
Synopsis:
FLIGHT_PAS_HEADER_CALLSIGN_REF
Example:
component: browse 1
(
table: BROWSE
(
list:
(
entry:
(
text: BROWSE_HEADER_CALLSIGN
(
...
length
: 8;
reference: FLIGHT_PAS_HEADER_CALLSIGN_REF
)
)
)
)
)
______________________________________________________________________
FLIGHT_PAS_HEADER_DEP_REF
Reference: FLIGHT_PAS_HEADER_DEP_REF
Description:
Handler: flight
Type: string
Synopsis:
FLIGHT_PAS_HEADER_DEP_REF
Example:
component: browse 1
(
table: BROWSE
(
205678826.doc
UNCLASSIFIED
Page 273
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
list:
(
entry:
(
text: BROWSE_HEADER_DEP
(
...
length
: 4;
reference: FLIGHT_PAS_HEADER_DEP_REF
)
)
)
)
______________________________________________________________________
FLIGHT_PAS_HEADER_DES_REF
Reference: FLIGHT_PAS_HEADER_DES_REF
Description:
Handler: flight
Type:
Synopsis:
FLIGHT_PAS_HEADER_DES_REF
Example:
component: browse 1
(
table: BROWSE
(
list:
(
entry:
(
text: BROWSE_HEADER_DES
(
event
...
length
: 4;
reference: FLIGHT_PAS_HEADER_DES_REF
)
)
)
)
)
______________________________________________________________________
FLIGHT_PAS_IFIR_REF
Reference: FLIGHT_PAS_IFIR_REF
Description:
Handler: flight
Type: string
Synopsis:
FLIGHT_PAS_IFIR_REF
Example:
preview: BRW
(
title:'BRW: FPL PAS. LI '
field: BRW_IFIR_FLD
(
label (default: 'IFIR' )
text
205678826.doc
UNCLASSIFIED
Page 274
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
(
reference: FLIGHT_PAS_IFIR_REF
length
: 4
)
)
______________________________________________________________________
FLIGHT_PAS_MORE_REF
Reference: FLIGHT_PAS_MORE_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_PAS_OBT_BRW_REF
Reference: FLIGHT_PAS_OBT_BRW_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_PAS_OBT_MAX_DATE_REF
Reference: FLIGHT_PAS_OBT_MAX_DATE_REF
Description:
Handler: flight
Type:
Synopsis:
FLIGHT_PAS_OBT_MAX_DATE_REF
Example:
component: browse 1
(
table: BROWSE
(
list:
(
entry:
(
text: BROWSE_HEADER_OBT_MAX_DATE
(
...
length
: 6;
reference: FLIGHT_PAS_OBT_MAX_DATE_REF
)
)
)
)
)
______________________________________________________________________
205678826.doc
UNCLASSIFIED
Page 275
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
FLIGHT_PAS_OBT_MAX_HOUR_REF
Reference: FLIGHT_PAS_OBT_MAX_HOUR_REF
Description:
Handler: flight
Type:
Synopsis:
FLIGHT_PAS_OBT_MAX_HOUR_REF
Example:
component: browse 1
(
table: BROWSE
(
list:
(
entry:
(
text: BROWSE_HEADER_OBT_MAX_TIME
(
...
length
: 4;
reference: FLIGHT_PAS_OBT_MAX_HOUR_REF
)
)
)
)
)
______________________________________________________________________
FLIGHT_PAS_OBT_MIN_DATE_REF
Reference: FLIGHT_PAS_OBT_MIN_DATE_REF
Description:
Handler: flight
Type:
Synopsis:
FLIGHT_PAS_OBT_MIN_DATE_REF
Example:
component: browse 1
(
table: BROWSE
(
list:
(
entry:
(
text: BROWSE_HEADER_OBT_MIN_DATE
(
...
length
: 6;
reference: FLIGHT_PAS_OBT_MIN_DATE_REF
)
)
)
)
)
______________________________________________________________________
FLIGHT_PAS_OBT_MIN_HOUR_REF
Reference: FLIGHT_PAS_OBT_MIN_HOUR_REF
Description:
-
205678826.doc
UNCLASSIFIED
Page 276
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Handler: flight
Type:
Synopsis:
FLIGHT_PAS_OBT_MIN_HOUR_REF
Example:
component: browse 1
(
table: BROWSE
(
list:
(
entry:
(
text: BROWSE_HEADER_OBT_MIN_TIME
(
...
length
: 4;
reference: FLIGHT_PAS_OBT_MIN_HOUR_REF
)
)
)
)
)
______________________________________________________________________
FLIGHT_PAS_OBT_REF
Reference: FLIGHT_PAS_OBT_REF
Description:
Handler: flight
Type: string
Synopsis:
FLIGHT_PAS_OBT_REF
Example:
component: browse 1
(
table: BROWSE
(
list:
(
entry:
(
text: BROWSE_OBT
(
...
length
: 7;
reference: FLIGHT_PAS_OBT_REF
)
)
)
)
)
______________________________________________________________________
FLIGHT_PAS_OFIR_REF
Reference: FLIGHT_PAS_OFIR_REF
Description:
Handler: flight
Type:
205678826.doc
UNCLASSIFIED
Page 277
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Synopsis:
Example:
preview: BRW
(
title:'BRW: FPL PAS. LI '
field: BRW_OFIR_FLD
(
label (default: 'OFIR' )
text
(
reference: FLIGHT_PAS_OFIR_REF
length
: 4
)
)
)
______________________________________________________________________
FLIGHT_PAS_OKEY_REF
Reference: FLIGHT_PAS_OKEY_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_PAS_PLV_REF
Reference: FLIGHT_PAS_PLV_REF
Description:
Handler: flight
Type: string
Synopsis:
FLIGHT_PAS_PLV_REF
Example:
component: browse 1
(
table: BROWSE
(
list:
(
entry:
(
text: BROWSE_PLV
(
...
length
: 3;
event
reference: FLIGHT_PAS_PLV_REF
)
)
)
)
)
______________________________________________________________________
FLIGHT_PAS_PMC_REF
Reference: FLIGHT_PAS_PMC_REF
Description:
-
205678826.doc
UNCLASSIFIED
Page 278
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_PAS_ROUTE_REF
Reference: FLIGHT_PAS_ROUTE_REF
Description:
Handler: flight
Type: string
Synopsis:
FLIGHT_PAS_ROUTE_REF
Example:
component: browse 1
(
table: BROWSE
(
list:
(
entry:
(
text: BROWSE_ROUTE
(
...
length
: 14;
reference: FLIGHT_PAS_ROUTE_REF
)
)
)
)
)
______________________________________________________________________
FLIGHT_PAS_RWY_REF
Reference: FLIGHT_PAS_RWY_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_PAS_SSR_REF
Reference: FLIGHT_PAS_SSR_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
205678826.doc
UNCLASSIFIED
Page 279
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
______________________________________________________________________
FLIGHT_PAS_SYMBOL_DOWN_REF
Reference: FLIGHT_PAS_SYMBOL_DOWN_REF
Description:
Handler: flight
Type:
Synopsis:
FLIGHT_PAS_SYMBOL_DOWN_REF
Example:
symbol: BROWSE_SCROLLING_DOWN
(
event: ABCK (function: BRW_SCROLL (BRW_ID SCROLLING_DOWN))
initial: P_BROWSE_BUTTON_DISABLED
...
reference: FLIGHT_PAS_SYMBOL_DOWN_REF
)
______________________________________________________________________
FLIGHT_PAS_SYMBOL_MODIFY_REF
Reference: FLIGHT_PAS_SYMBOL_MODIFY_REF
Description:
Handler: flight
Type:
Synopsis:
FLIGHT_PAS_SYMBOL_MODIFY_REF
Example:
symbol: BROWSE_ITEM_MODIFY
(
initial : P_ITEM_NOT_MODIFIED
...
reference: FLIGHT_PAS_SYMBOL_MODIFY_REF
)
______________________________________________________________________
FLIGHT_PAS_SYMBOL_UP_REF
Reference: FLIGHT_PAS_SYMBOL_UP_REF
Description:
Handler: flight
Type:
Synopsis:
FLIGHT_PAS_SYMBOL_UP_REF
Example:
symbol: BROWSE_SCROLLING_UP
(
event: ABCK
(function: BRW_SCROLL (BRW_ID SCROLLING_DOWN))
initial: P_BROWSE_BUTTON_DISABLED
...
reference: FLIGHT_PAS_SYMBOL_UP_REF
)
______________________________________________________________________
FLIGHT_PAS_TAS_REF
Reference: FLIGHT_PAS_TAS_REF
205678826.doc
UNCLASSIFIED
Page 280
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Description:
Handler: flight
Type: string
Synopsis:
FLIGHT_PAS_TAS_REF
Example:
component: browse 1
(
table: BROWSE
(
list:
(
entry:
(
text: BROWSE_TAS
(
...
length
: 4;
event
reference: FLIGHT_PAS_TAS_REF
)
)
)
)
)
______________________________________________________________________
FLIGHT_PAS_TCT_REF
Reference: FLIGHT_PAS_TCT_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_PAS_TRU_ROB_REF
Reference: FLIGHT_PAS_TRU_ROB_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_PAS_USER_MSG_REF
Reference: FLIGHT_PAS_USER_MSG_REF
Description:
Handler: flight
Type:
Synopsis:
205678826.doc
UNCLASSIFIED
Page 281
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
FLIGHT_PAS_USER_MSG_REF
Example:
text: BROWSE_HEADER_MORE_FLAG
(
...
length
: 9;
reference: FLIGHT_PAS_USER_MSG_REF
)
______________________________________________________________________
FLIGHT_PAS_XLV_REF
Reference: FLIGHT_PAS_XLV_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_PBN_REF
Reference: FLIGHT_PBN_REF
Description:
Parking Bay Name assigned to the flight.
Handler: flight
Type: string (Max Length: PARKING_BAY_LENGTH)
Synopsis:
FLIGHT_PBN_REF
Examples:
One could relate the ARR_PB text field of the presentation object
internal database, named FLIGHT_PBN_REF.
text: ARR_PB
(
reference: FLIGHT_PBN_REF
...
length: PARKING_BAY_LENGTH;
)
______________________________________________________________________
FLIGHT_PDIS_REF
Reference: FLIGHT_PDIS_REF
Description:
Handler: flight
Synopsis:
FLIGHT_PDIS_REF
Example:
One could relate the FLDA_PDIS_FIELD text field of the presentation object
internal database, named FLIGHT_PDIS_REF.
text: FLDA_PDIS_FIELD
(
205678826.doc
UNCLASSIFIED
Page 282
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
...
length
: 4;
reference: FLIGHT_PDIS_REF
______________________________________________________________________
FLIGHT_PEL_DRAWING_REF
Reference: FLIGHT_PEL_DRAWING_REF
Description:
Handler: flight
Type: numeric
Synopsis:
FLIGHT_PEL_DRAWING_REF
Example:
actions:
(
switch: flight(FLIGHT_PEL_DRAWING_REF).num
(
...
)
)
______________________________________________________________________
FLIGHT_PEL_REF
Reference: FLIGHT_PEL_REF
Description:
Used to refer to the Proposal Entry Level
during a sector co-ordination.
Handler: flight
Type: string (Max Lenght: COORD_INFO_LENGTH)
Synopsis:
FLIGHT_TEXT_REF
Example:
One could relate the EFL_PEL text field of the presentation object
internal database, named FLIGHT_PEL_REF.
text: EFL_PEL
(
...
length
: 3;
reference: FLIGHT_PEL_REF
)
______________________________________________________________________
FLIGHT_PEL_WARNING_REF
Reference: FLIGHT_PEL_WARNING_REF
Description:
This reference will be used to refere pel warning
information
Handler: flight
Components Usage:
Type: string
Synopsis:
FLIGHT_PEL_WARNING_REF
Examples:
205678826.doc
UNCLASSIFIED
Page 283
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Not used
______________________________________________________________________
FLIGHT_PER_DRAWING_REF
Reference: FLIGHT_PER_DRAWING_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_PER_REF
Reference: FLIGHT_PER_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_PLV_REF
Reference: FLIGHT_PLV_REF
Description:
Planning Level for the flight.
Handler: flight
Synopsis:
FLIGHT_PLV_REF
Examples:
One could relate the PLV_FIELD text field of the presentation object
internal database, named FLIGHT_PLV_REF.
text: PLV_FIELD
(
reference: FLIGHT_PLV_REF
...
)
______________________________________________________________________
FLIGHT_POB_REF
Reference: FLIGHT_POB_REF
Description:
Handler: flight
Type: string
Synopsis:
205678826.doc
UNCLASSIFIED
Page 284
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
FLIGHT_POB_REF
Example:
field: LFI_POB_FLD
(
label (default: 'POB' )
text
(
reference: FLIGHT_POB_REF
length
: 4
)
)
______________________________________________________________________
FLIGHT_POWER_HCI_REF
Reference: FLIGHT_POWER_HCI_REF
Description:
This reference is used to refer to hci power into
power_table defined in FLIGHT ATC.
Handler: flight
Synopsis:
FLIGHT_POWER_HCI_REF
Examples:
internal database, named FLIGHT_POWER_HCI_REF.
text: ESB_TAS
(
reference: FLIGHT_POWER_HCI_REF
...
)
______________________________________________________________________
FLIGHT_PRO_SSR_REF
Reference: FLIGHT_PRO_SSR_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_PSSR_REF
Reference: FLIGHT_PSSR_REF
Description:
Secondary Surveillance Radar (T.B.D.) assigned code
to the flight.
Handler: flight
Synopsis:
FLIGHT_PSSR_REF
Examples:
205678826.doc
UNCLASSIFIED
Page 285
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
internal database, named FLIGHT_PSSR_REF.

text: PSSR_FIELD
(
reference: FLIGHT_PSSR_REF
...
)
______________________________________________________________________
FLIGHT_PTIM_REF
Reference: FLIGHT_PTIM_REF
Description:
Handler: flight
Synopsis:
FLIGHT_PTIM_REF
Example:
One could relate the FLDA_PDIS_FIELD text field of the presentation object
internal database, named FLIGHT_PTIM_REF.
text: FLDA_PDIS_FIELD
(
...
length
: 4;
reference: FLIGHT_PTIM_REF
)
______________________________________________________________________
FLIGHT_PTS_REF
Reference: FLIGHT_PTS_REF
Description:
This reference will be used to refere previous track status
information
Handler: flight
Components Usage:
Type: string
Synopsis:
FLIGHT_PTS_REF
Examples:
Not used
______________________________________________________________________
FLIGHT_PWRTBL_REF
Reference: FLIGHT_PWRTBL_REF
Description:
power_table defined in FLIGHT ATC.
Handler: flight
Synopsis:
FLIGHT_PWRTBL_REF
Examples:
internal database, named FLIGHT_PWRTBL_REF.
205678826.doc
UNCLASSIFIED
Page 286
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
text: ESB_TAS
(
reference: FLIGHT_PWRTBL_REF
...
)
______________________________________________________________________
FLIGHT_RECORD_FDM_PRESENCE_REF
Description:
This reference is used to trigger the Record Initial Action,
that defines how a flight item (message) received from
Flight Data Manager csci shall be managed:
Allowed values are:
TRUE_CASE: The record should exist (corresponds to INSERT command).
FASE_CASE: The record should not exist (corresponds to DELETE command).
NOP_CASE: Default (corresponds to UPDATE and any other command).
Allowed values for the list identifier (#<list instance>) are:
ESB_LIST, DEP_STRIP, ARR_STRIP, OVF_STRIP, ENR_STRIP,
DEP_LIST, ARR_LIST, HLD_LIST, SIL_LIST, FLDI_LIST,
SEL_LIST, PDL_LIST, SCL_LIST, VFL_LIST, EFL_LIST,
SOL_LIST, CIL_LIST, COL_LIST, AAL_LIST, ADL_LIST.
Handler: flight
Type: num
Synopsis:
FLIGHT_RECORD_FDM_PRESENCE_REF#FLDI_LIST
______________________________________________________________________
FLIGHT_RECURRENT_DRAWING_REF
Description:
This reference is used to indicate a recurrent flight \
for a sector
Handler: flight
Type:
num
Synopsis:
FLIGHT_RECURRENT_DRAWING_REF
______________________________________________________________________
FLIGHT_REGN_REF
Reference: FLIGHT_REGN_REF
Description:
REGN for the flight.
Handler: flight
Type: string
Synopsis:
FLIGHT_REGN_REF
Examples:
internal database, named FLIGHT_REGN_REF.
text REGN_FIELD:
(
...
reference: FLIGHT_REGN_REF
length
: 8;
)
205678826.doc
UNCLASSIFIED
Page 287
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
______________________________________________________________________
FLIGHT_REG_REF
Reference: FLIGHT_REG_REF
Description:
Handler: flight
Type: string (Max Length: REG_LENGTH)
Synopsis:
FLIGHT_REG_REF
Example:
preview: REG
(
label: 'REGISTER NUMBER'
field: REG_TEXT_FLD
(
label (default: 'REGISTRATION' )
text
(
reference: FLIGHT_REG_REF
length
: 8
)
)
)
______________________________________________________________________
FLIGHT_RFL_REF
Reference: FLIGHT_RFL_REF
Description:
Handler: flight
Type: string
Synopsis:
FLIGHT_RFL_REF
Example:
component: flda 3
(
text: RFL_FIELD
(
...
length
: 3;
reference: FLIGHT_RFL_REF
)
)
______________________________________________________________________
FLIGHT_ROUTE1_REF
Reference: FLIGHT_ROUTE1_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_ROUTE_REF
205678826.doc
UNCLASSIFIED
Page 288
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Reference: FLIGHT_ROUTE_REF
Description:
This reference is used to refer to the Route of a flight.
Handler: flight
Type: string (Max Length: ROB_LENGTH)
Synopsis:
FLIGHT_ROUTE_REF
Examples:
One could relate the ARR_ROUTE text field of the presentation object
internal database, named FLIGHT_ROUTE_REF.
text: ARR_ROUTE
(
attribute: ARR_A_TEXT
...
truncation: '*'
length
: 18;
event
: ABCK
reference : FLIGHT_ROUTE_REF
)
______________________________________________________________________
FLIGHT_RVSM_BIN_REF
Reference: FLIGHT_RVSM_BIN_REF
Description:
RVSM of a flight.
Handler: flight
Type: numeric
Synopsis:
FLIGHT_RVSM_BIN_REF
Example:
component: fldi 1
(
...
table: FLDI
(
...
list:
(
...
entry:
(
...
text: MLB_RVSM
(
length: 1;
actions
(
set_field_text
(
CURRENT_FIELD,
rvsm_value_tab[FLIGHT_RVSM_BIN_REF]
)
)
)
)
)
)
)
______________________________________________________________________
FLIGHT_RVSM_REF
205678826.doc
UNCLASSIFIED
Page 289
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Reference: FLIGHT_RVSM_REF
Description:
RVSM of a flight.
Handler: flight
Synopsis:
FLIGHT_RVSM_REF
Example:
preview: RCL
(
title: 'RCL: EN-R. CLEAR ' + FLIGHT_CALLSIGN_REF
field: RCL_RVSM_FLD
(
label (default: 'RVSM' )
text
(
reference: FLIGHT_RVSM_REF
length
: 1
)
help
(
type
: CHOICE
visible: off
values : prw_rvsm_value_tab
default:'W'
)
)
______________________________________________________________________
FLIGHT_RWY_AIRPORT_REF
Reference: FLIGHT_RWY_AIRPORT_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_RWY_ARR_REF
Reference: FLIGHT_RWY_ARR_REF
Description:
Arrival Runway Code for the flight.
Handler: flight
Type: string (Max Length: RWY_LENGTH)
Synopsis:
FLIGHT_RWY_ARR_REF
Examples:
One could relate the ARR_RWY_ARR text field of the presentation object
internal database, named FLIGHT_RWY_ARR_REF.
text: ARR_RWY_ARR
(
reference: FLIGHT_RWY_ARR_REF
...
205678826.doc
UNCLASSIFIED
Page 290
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
length: RWY_LENGTH;
)
______________________________________________________________________
FLIGHT_RWY_DEPRATE_REF
Reference: FLIGHT_RWY_DEPRATE_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_RWY_DEP_REF
Reference: FLIGHT_RWY_DEP_REF
Description:
Departure Runway Code for the flight.
Handler: flight
Type: string (Max Length: RWY_LENGTH)
Synopsis:
FLIGHT_RWY_DEP_REF
Examples:
One could relate the DEP_RWY_DEP text field of the presentation object
internal database, named FLIGHT_RWY_DEP_REF.
text: DEP_RWY_DEP
(
reference: FLIGHT_RWY_DEP_REF
...
length: RWY_LENGTH
)
______________________________________________________________________
FLIGHT_RWY_LNDRATE_REF
Reference: FLIGHT_RWY_LNDRATE_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_RWY_LND_REF
Reference: FLIGHT_RWY_LND_REF
Description:
Handler: flight
Type: string(Max lenght: POINT_NAME_LENGTH)
Synopsis:
205678826.doc
UNCLASSIFIED
Page 291
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
FLIGHT_RWY_LND_REF
Example:
preview: URW
(
label: 'DEP/LND RUNWAY'
...
field: URW_LND_FLD
(
label (default: 'LND RWY' )
text
(
reference: FLIGHT_RWY_LND_REF
length: 3
)
)
______________________________________________________________________
FLIGHT_RWY_MIXRATE_REF
Reference: FLIGHT_RWY_MIXRATE_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_RWY_NOCHECK_REF
Reference: FLIGHT_RWY_NOCHECK_REF
Description:
Handler: flight
Type: string
Synopsis:
FLIGHT_RWY_NOCHECK_REF
Example:
preview: FFP
(
title: 'FFP: FAST FLIGHT PLAN'
...
field: FFP_RWY_FLD
(
label ( default:'RWY' )
text
(
reference: FLIGHT_RWY_NOCHECK_REF
length
: 3
)
)
)
______________________________________________________________________
FLIGHT_RWY_RWY1_REF
Reference: FLIGHT_RWY_RWY1_REF
Description:
Handler: flight
205678826.doc
UNCLASSIFIED
Page 292
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003

Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_RWY_RWY2_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_RWY_RWY3_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_RWY_RWY4_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_RWY_RWY5_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_RWY_RWY6_REF
Description:
205678826.doc
UNCLASSIFIED
Page 293
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_RWY_ST1_REF
Reference: FLIGHT_RWY_ST1_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_RWY_ST2_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_RWY_ST3_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_RWY_ST4_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_RWY_ST5_REF
205678826.doc
UNCLASSIFIED
Page 294
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_RWY_ST6_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_SCT_REF
Reference: FLIGHT_SCT_REF
Description:
Used to display the name of the actual Sector.
Handler: flight
Type: string (Max Lenght: SECTOR_NAME_LENGTH)
Synopsis:
FLIGHT_SCT_REF
Example:
One could relate the FLDA_SEC_FIELD text field of the presentation object
internal database, named FLIGHT_SCT_REF.
text: FLDA_SEC_FIELD
(
...
length: 2;
reference: FLIGHT_SCT_REF
)
______________________________________________________________________
FLIGHT_SCT_TOC_REF
Reference: FLIGHT_SCT_TOC_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_SEC_SKIP_REF
Reference: FLIGHT_SEC_SKIP_REF
205678826.doc
UNCLASSIFIED
Page 295
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Description:
Sector Skip for the flight.
Handler: flight
Type: string
Synopsis:
FLIGHT_SEC_SKIP_REF
Examples:
internal database, named FLIGHT_SEC_SKIP_REF.
choice: SKP
(
legend:'SKIP'
field: SKP_SCT_FLD
(
text
(
reference: FLIGHT_SEC_SKIP_REF
length
: 3
)
)
)
______________________________________________________________________
FLIGHT_SEL_REF
Reference: FLIGHT_SEL_REF
Description:
Handler: flight
Type: string ( Max Lenght: POINT_TYPE_LENGTH )
Synopsis:
FLIGHT_SEL_REF
Example:
One could relate the FLDA_F_FIELD text field of the presentation object
internal database, named FLIGHT_SEL_REF.
text: FLDA_F_FIELD
(
...
length
: 1;
reference: FLIGHT_SEL_REF
)
______________________________________________________________________
FLIGHT_SEP_REF
Reference: FLIGHT_SEP_REF
Description:
Handler: flight
Type: string
Synopsis:
FLIGHT_SEP_REF
Example:
One could relate the LSC_LAB_FLD field of the LSC preview to the record
205678826.doc
UNCLASSIFIED
Page 296
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
field of the flight internal database, name FLIGHT_SEP_REF.

preview: LSC
(
label: 'CREATE LABEL STRIP'
field: LSC_LAB_FLD
(
text
(
reference: FLIGHT_SEP_REF
length
: 5
)
)
)
______________________________________________________________________
FLIGHT_SEQUENCY_ACT_REF
Reference: FLIGHT_SEQUENCY_ACT_REF
Description:
Handler: flight
Type: string
Synopsis:
FLIGHT_SEQUENCY_ACT_REF
Example:
text: SQN_ACT
(
attribute: SQN_A_TEXT
length
: 5;
...
actions
(
set_field_text
(
CURRENT_TEMPLATE, CURRENT_FIELD, seq_action_tab[FLIGHT_SEQUENCY_ACT_REF]
)
)
)
______________________________________________________________________
FLIGHT_SEQUENCY_ACT_TIME_REF
Reference: FLIGHT_SEQUENCY_ACT_TIME_REF
Description:
Handler: flight
Type: string
Synopsis:
FLIGHT_SEQUENCY_ACT_TIME_REF
Example:
text: SQN_ACTT
(
length
: 4;
initial :'SQN_'
...
reference: FLIGHT_SEQUENCY_ACT_TIME_REF
)
______________________________________________________________________
205678826.doc
UNCLASSIFIED
Page 297
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
FLIGHT_SEQUENCY_AIRP_NAME_REF
Reference: FLIGHT_SEQUENCY_AIRP_NAME_REF
Description:
Handler: flight
Type: string
Synopsis:
FLIGHT_SEQUENCY_AIRP_NAME_REF
Example:
text: SQN_AIRPORT_NAME
(
attribute: SQN_A_TITLE_TEXT
...
length
: 4;
reference: FLIGHT_SEQUENCY_AIRP_NAME_REF
)
______________________________________________________________________
FLIGHT_SEQUENCY_CONF_REF
Reference: FLIGHT_SEQUENCY_CONF_REF
Description:
Handler: flight
Type: string
Synopsis:
FLIGHT_SEQUENCY_CONF_REF
Example:
text: SQN_CONF
(
length
: 1;
actions
(
set_field_text
(
CURRENT_TEMPLATE, CURRENT_FIELD, seq_conf_tab[FLIGHT_SEQUENCY_CONF_REF]
)
)

______________________________________________________________________
FLIGHT_SEQUENCY_CS_REF
Reference: FLIGHT_SEQUENCY_CS_REF
Description:
Handler: flight
Type: string
Synopsis:
FLIGHT_SEQUENCY_CS_REF
Example:
text: SQN_CS
(
...
length: 8;
event : ABCK (function: HOOKING ())
205678826.doc
UNCLASSIFIED
Page 298
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
...
reference: FLIGHT_SEQUENCY_CS_REF
______________________________________________________________________
FLIGHT_SEQUENCY_EST_REF
Reference: FLIGHT_SEQUENCY_EST_REF
Description:
Handler: flight
Type: string
Synopsis:
FLIGHT_SEQUENCY_EST_REF
Example:
text: SQN_EST
(
length
: 4;
initial :'SQN_'

reference: FLIGHT_SEQUENCY_EST_REF
______________________________________________________________________
FLIGHT_SEQUENCY_NUM_REF
Reference: FLIGHT_SEQUENCY_NUM_REF
Description:
Handler: flight
Type: string
Synopsis:
FLIGHT_SEQUENCY_NUM_REF
Example:
preview: SQN
(
title: 'ASQ ' + FLIGHT_CALLSIGN_REF
class: EXCLUSIVE_RAD
field: SQN_VALUE1_FLD
(
label ( default: 'SEQ NUM' )
text
(
reference: FLIGHT_SEQUENCY_NUM_REF
length
: 2
)
)
(
...
)
)
______________________________________________________________________
FLIGHT_SEQUENCY_PRT_REF
Reference: FLIGHT_SEQUENCY_PRT_REF
Description:
Handler: flight
205678826.doc
UNCLASSIFIED
Page 299
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003

Type: string
Synopsis:
FLIGHT_SEQUENCY_PRT_REF
Example:
text: SQN_PRT
(
length
: 4;
initial :'SQN_'
reference: FLIGHT_SEQUENCY_PRT_REF
)
______________________________________________________________________
FLIGHT_SEQUENCY_RWY_REF
Reference: FLIGHT_SEQUENCY_RWY_REF
Description:
Handler: flight
Type: string
Synopsis:
FLIGHT_SEQUENCY_RWY_REF
Example:
preview: SQN
(
title: 'ASQ ' + FLIGHT_CALLSIGN_REF
class: EXCLUSIVE_RAD
(
...
)
(
visible: off
label ( default: 'RWY' )
text
(
reference: FLIGHT_SEQUENCY_RWY_REF
length
: 3
)
)
)
______________________________________________________________________
FLIGHT_SEQUENCY_TYPE_REF
Reference: FLIGHT_SEQUENCY_TYPE_REF
Description:
Handler: flight
Type: string
Synopsis:
FLIGHT_SEQUENCY_TYPE_REF
Example:
text: SQN_TYPE
(
length: 1;
...
actions
(
set_field_text
(
CURRENT_TEMPLATE, CURRENT_FIELD, seq_type_tab[FLIGHT_SEQUENCY_TYPE_REF]
205678826.doc
UNCLASSIFIED
Page 300
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
)
)
)
______________________________________________________________________
FLIGHT_SID_REF
Reference: FLIGHT_SID_REF
Description:
Standard Instrumental Departure for the flight.
Handler: flight
Type: string (Max Length: SID_LENGTH)
Synopsis:
FLIGHT_SID_REF
Examples:
One could relate the DEP_SID text field of the presentation object
internal database, named FLIGHT_SID_REF.
text: DEP_SID
(
reference: FLIGHT_SID_REF
...
length: SID_LENGTH;
)
______________________________________________________________________
FLIGHT_SIL_NAME_REF
Reference: FLIGHT_SIL_NAME_REF
Description:
Sector Inbound List Name for the flight.
Handler: flight
Type: string
Synopsis:
FLIGHT_SIL_NAME_REF
Examples:
internal database, named FLIGHT_SIL_NAME_REF.
text SIL_NAME:
(
attribute: SIL_A_TITLE_TEXT
reference: FLIGHT_SIL_NAME_REF
length
: 5;
)
______________________________________________________________________
FLIGHT_SLT_REF
Reference: FLIGHT_SLT_REF
Description:
Handler: flight
Type: string
Synopsis:
205678826.doc
UNCLASSIFIED
Page 301
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
FLIGHT_SLT_REF
Example:
preview: SCL
(
label :'START UP CLEARANCE'
warning:(line : 2)
field
(
...
)
: SCL_EOBT_FLD
field: SCL_TAXI_TIME_FLD
(
label (default: 'TAXI TIME' )
text
(
reference: FLIGHT_SLT_REF
length
: 4
default : '
'
)
)
______________________________________________________________________
FLIGHT_SPD_MACH_REF
Reference: FLIGHT_SPD_MACH_REF
Description:
Handler: flight
Type: numeric
Synopsis:
FLIGHT_SPD_MACH_REF
Example:
choice: SPD_MACH
(
legend:'SPD MACH'
field : LND_SPD_MACH_FLD
(
label (default: 'SPD' )
text
(
reference: FLIGHT_SPD_MACH_REF
length
: 4
prevalues: '
'
values
: 60 to 150 step 1
default : 100
)
)
)
______________________________________________________________________
FLIGHT_SPD_REF
Reference: FLIGHT_SPD_REF
Description:
Handler: flight
Components Usage: tabular, preview
Type: string
Synopsis:
FLIGHT_SPD_REF
Example:
205678826.doc
UNCLASSIFIED
Page 302
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Within a tabular syntax:

text: FHI_ASP
(
attribute: A_TEXT
length: 4;
...
event: ABCK
(
f.dialog: DOUBLE_TURN choice_SPD "" fdm.SPD_ID;
)
event: IBCK
(
f.dialog: DOUBLE_TURN choice_SPD_MACH "" fdm.SPD_ID;
)
...
reference: FLIGHT_SPD_REF
)
Within a preview syntax:
choice: SPD
(
title: FLIGHT_CALLSIGN_REF
legend: 'SPD KNOTS'
field: LND_SPD1_FLD
(
label (default: 'SPD' )
text
(
reference: FLIGHT_SPD_REF
length
: 4
prevalues: '
'
values
: 0 to 990 step 10
default : 180
)
)
)
______________________________________________________________________
FLIGHT_SPL_PEL_REF
Reference: FLIGHT_SPL_PEL_REF
Description:
This reference will be used to refere supplementary
entry flight level
Handler: flight
Components Usage:
Type: string
Synopsis:
FLIGHT_SPL_PEL_REF
Examples:
Not used
______________________________________________________________________
FLIGHT_SPL_XFL_REF
Reference: FLIGHT_SPL_XFL_REF
Description:
This reference is used to refere supplementary
exit flight level
Handler: flight
Components Usage:
Type: string
Synopsis:
FLIGHT_SPL_XFL_REF
Examples:
205678826.doc
UNCLASSIFIED
Page 303
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
choice: PEL
(
legend: 'PEL'
field : PEL_FLD
(
label ( default: 'PEL' )
text
(
reference: FLIGHT_PEL_REF
length
: 6
values
: 'ACCEPT'
'REJECT'
'MODIFY'
)
)
)
______________________________________________________________________
FLIGHT_SSP_REF
Reference: FLIGHT_SSP_REF
Description:
Handler: flight
Type: string
Synopsis:
FLIGHT_SSP_REF
Example:
text: ESB_PRO_SSR
(
start_ref_pos: 1
...
length
: 4;
reference: FLIGHT_SSP_REF
)
______________________________________________________________________
FLIGHT_SSR_NOCHECK_REF
Reference: FLIGHT_SSR_NOCHECK_REF
Description:
Secondary Surveillance Radar Without check (T.B.D.) assigned code
to the flight.
Handler: flight
Synopsis:
FLIGHT_SSR_NOCHECK_REF
Examples:
internal database, named FLIGHT_SSR_NOCHECK_REF.
text: SSR_NOT_CHECKED_FIELD
(
reference: FLIGHT_SSR_NOCHECK_REF
...
)
______________________________________________________________________
FLIGHT_SSR_REF
205678826.doc
UNCLASSIFIED
Page 304
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Reference: FLIGHT_SSR_REF
Description:
Secondary Surveillance Radar assigned code
to the flight (the modecode).
Handler: flight
Synopsis:
FLIGHT_SSR_REF
Examples:
internal database, named FLIGHT_SSR_REF.
text: SSR_FIELD
(
reference: FLIGHT_SSR_REF
...
)
______________________________________________________________________
FLIGHT_SST_REF
Reference: FLIGHT_SST_REF
Description:
Shift Strip for the flight.
Handler: flight
Type: string
Synopsis:
FLIGHT_SST_REF
Examples:
internal database, named FLIGHT_SST_REF.
text TOC_LEV_FLD:
(
reference: FLIGHT_SST_REF
length
: 2;
)
______________________________________________________________________
FLIGHT_STAR_REF
Reference: FLIGHT_STAR_REF
Description:
Star Information of a flight.
Handler: flight
Type: string (Max Length: STAR_LENGTH)
Synopsis:
FLIGHT_STAR_REF
Examples:
internal database, named FLIGHT_STAR_REF.
text: ARR_STAR
(
reference: FLIGHT_STAR_REF
length
: STAR_LENGTH;
205678826.doc
UNCLASSIFIED
Page 305
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
)
______________________________________________________________________
FLIGHT_STATE_REF
Reference: FLIGHT_STATE_REF
Description:
Handler: flight
Type: string
Synopsis:
FLIGHT_STATE_REF
Example:
text: ESB_Y
(
...
length
: 1;
reference: FLIGHT_STATE_REF
)
______________________________________________________________________
FLIGHT_STATUSBIN_REF
Reference: FLIGHT_STATUSBIN_REF
Description:
Handler: flight
Type: string
Synopsis:
FLIGHT_STATUSBIN_REF
Example:
text: WDA_STATUS
(
#include <event_hook.dsp>
length
: 1;
actions
(
set_field_text
(
CURRENT_TEMPLATE,
CURRENT_FIELD,
wda_status_tab[FLIGHT_STATUSBIN_REF]
)
)
...
)
______________________________________________________________________
FLIGHT_STATUS_REF
Reference: FLIGHT_STATUS_REF
Description:
Status for the flight.
Handler: flight
Type: string
Synopsis:
FLIGHT_STATUS_REF
205678826.doc
UNCLASSIFIED
Page 306
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Examples:
internal database, named FLIGHT_STATUS_REF.
text
(
reference: FLIGHT_STATUS_REF
length
: 3;
)
______________________________________________________________________
FLIGHT_STX_REF
Reference: FLIGHT_STX_REF
Description:
Strip text for the flight.
Handler: flight
Type: string (Max Length: STRING_TEXT_LENGTH)
Synopsis:
FLIGHT_STX_REF
Examples:
internal database, named FLIGHT_STX_REF.
preview: TXT
(
title: 'TXT: TEXT ' + FLIGHT_CALLSIGN_REF
...
field: TXT_TEXT_FLD
(
text
(
reference:FLIGHT_STX_REF
length
: 16
)
)
)
______________________________________________________________________
FLIGHT_TAS_IFX_REF
Reference: FLIGHT_TAS_IFX_REF
Description:
Planned True Air Speed Over the Inbound Fix
for the flight.
Handler: flight
Type: string
Synopsis:
FLIGHT_TAS_IFX_REF
Examples:
One could relate the FLDA_TAS_FIELD text field of the presentation object
internal database, named FLIGHT_TAS_IFX_REF.
text: FLDA_TAS_FIELD
(
position: C#43; R#0;
)
______________________________________________________________________
205678826.doc
UNCLASSIFIED
Page 307
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
FLIGHT_TAS_REF
Reference: FLIGHT_TAS_REF
Description:
Planned True Air Speed Over the Point
for the flight.
Handler: flight
Synopsis:
FLIGHT_TAS_REF
Examples:
internal database, named FLIGHT_TAS_REF.
text: ESB_TAS
(
...
)
______________________________________________________________________
FLIGHT_TCT_REF
Reference: FLIGHT_TCT_REF
Description:
Current Turbolence Category value for the flight.
Handler: flight
Type: string (Max Length: CATEGORY_LENGTH)
Synopsis:
FLIGHT_TCT_REF
Examples:
One could relate the TCT_FIELD text field of the presentation object
internal database, named FLIGHT_TCT_REF.
text: TCT_FIELD
(
reference: FLIGHT_TCT_REF
...
length: CATEGORY_LENGTH;
)
______________________________________________________________________
FLIGHT_TEXT_REF
Reference: FLIGHT_TEXT_REF
Description:
This reference is used to refer to a
Free Text assigned to the flight.
Handler: flight
Type: string (Max Length: LABEL_TEXT_LENGTH)
Synopsis:
FLIGHT_TEXT_REF
Examples:
One could relate the ESB_FREE_TEXT text field of the presentation object
internal database, named FLIGHT_TEXT_REF.
text: ESB_FREE_TEXT
205678826.doc
UNCLASSIFIED
Page 308
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
(
reference: FLIGHT_TEXT_REF
length: LABEL_TEXT_LENGTH;
)
______________________________________________________________________
FLIGHT_TRACK_SECTOR_WARNING_REF
Reference: FLIGHT_TRACK_SECTOR_WARNING_REF
Description:
This reference will be used to refere track sector warning
information
Handler: flight
Components Usage:
Type: string
Synopsis:
FLIGHT_TRACK_SECTOR_WARNING_REF
Examples:
Not used
______________________________________________________________________
FLIGHT_TYPE_REF
Reference: FLIGHT_TYPE_REF
Description:
Aircraft Type for the flight.
Handler: flight
Type: string (Max Length: AIR_TYPE_LENGTH)
Synopsis:
FLIGHT_TYPE_REF
Examples:
One could relate the TYPE_FIELD text field of the presentation object
internal database, named FLIGHT_TYPE_REF.
text: TYPE_FIELD
(
reference: FLIGHT_TYPE_REF
...
)
______________________________________________________________________
FLIGHT_VTRUN_REF
Reference: FLIGHT_VTRUN_REF
Description:
Vertical Rate Unit for the VTR field.
Handler: flight
Components Usage:
Type:
string
Synopsis:
FLIGHT_VTRUN_REF
Example:
text: MLB_UN_VTR
(
...
length: 8;
actions
(
205678826.doc
UNCLASSIFIED
Page 309
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
set_field_text
(
CURRENT_FIELD,
vtr_unit_tab[FLIGHT_VTRUN_REF]
)
)
______________________________________________________________________
FLIGHT_VTR_REF
Reference: FLIGHT_VTR_REF
Description:
Vertical Rate for the flight.
Handler: flight
Components Usage:
Type: string
Synopsis:
FLIGHT_VTR_REF
Example:
text: MLB_VTR
(
...
length: 5;
actions
(
switch: FLIGHT_VTRVD_REF
(
)
)
reference: FLIGHT_VTR_REF
)
______________________________________________________________________
FLIGHT_W_REF
Reference: FLIGHT_W_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_XFL_COORD_REF
Reference: FLIGHT_XFL_COORD_REF
Description:
Exit Entry Level fir coordinates.
Handler: flight
Synopsis:
FLIGHT_COO_XFL_REF
Examples:
205678826.doc
UNCLASSIFIED
Page 310
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
One could relate the COO_XFL_FLD text field of the presentation object
internal database, named FLIGHT_COO_XFL_REF.
preview: COO
(
field: COO_XFL_FLD
(
label (default: 'XFL')
text
(
reference: FLIGHT_COO_XFL_REF
length
: 1
)
)
)
______________________________________________________________________
FLIGHT_XFL_DRAWING_REF
Reference: FLIGHT_XFL_DRAWING_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_XFL_REF
Reference: FLIGHT_XFL_REF
Description:
Exit Flight Level for the flight.
Handler: flight
Type: string (Max Length: COORD_INFO_LENGTH)
Synopsis:
FLIGHT_XFL_REF
Example:
One could relate the EFL_XFL text field of the presentation object
internal database, named FLIGHT_XFL_REF.
text: EFL_XFL
(
...
length
: 3;
reference: FLIGHT_XFL_REF
)
______________________________________________________________________
FLIGHT_XFL_STRIP_REF
Reference: FLIGHT_XFL_STRIP_REF
Description:
Strip Exit Entry Level for the flight.
Handler: flight
Type: string
Synopsis:
FLIGHT_XFL_STRIP_REF
205678826.doc
UNCLASSIFIED
Page 311
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Examples:
internal database, named FLIGHT_XFL_STRIP_REF.
text
(
reference: FLIGHT_XFL_STRIP_REF
length
: 6;
)
______________________________________________________________________
FLIGHT_XFL_WARNING_REF
Reference: FLIGHT_XFL_WARNING_REF
Description:
This reference will be used to refere xfl warning
information
Handler: flight
Components Usage:
Type: string
Synopsis:
FLIGHT_XFL_WARNING_REF
Examples:
Not used
______________________________________________________________________
FLIGHT_XFR_DRAWING_REF
Reference: FLIGHT_XFR_DRAWING_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_XFR_REF
Reference: FLIGHT_XFR_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
FLIGHT_XLV_FX1_REF
Reference: FLIGHT_XLV_FX1_REF
Description:
Crosssing Level at Fix 1 for the flight.
Handler: flight
205678826.doc
UNCLASSIFIED
Page 312
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Synopsis:
FLIGHT_XLV_FX1_REF
Examples:
Not used.
______________________________________________________________________
FLIGHT_XLV_FX2_REF
Description:
Handler: flight
Synopsis:
FLIGHT_XLV_FX2_REF
Examples:
Not used.
______________________________________________________________________
FLIGHT_XLV_FX3_REF
Description:
Handler: flight
Synopsis:
FLIGHT_XLV_FX3_REF
Examples:
Not used.
______________________________________________________________________
FLIGHT_XLV_HFX_REF
Reference: FLIGHT_XLV_HFX_REF
Description:
Crossing Level at Holding Fix for the flight.
Handler: flight
Synopsis:
FLIGHT_XLV_HFX_REF
Example:
preview: HOE
(
title :'HOE: HOLD. EXIT ' + FLIGHT_CALLSIGN_REF
field: HOE_ATX_FLD
(
...
)
field: HOE_XLV_FLD
(
label (default: 'XLV' )
text
205678826.doc
UNCLASSIFIED
Page 313
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
(
reference: FLIGHT_XLV_HFX_REF
length
: 3
)
)
______________________________________________________________________
FLIGHT_XLV_IFX_REF
Reference: FLIGHT_XLV_IFX_REF
Description:
Crosssing Level at Inbound Fix for the flight.
Handler: flight
Synopsis:
FLIGHT_XLV_IFX_REF
Examples:
One could relate the FLDA_XLV_FIELD text field of the presentation object
internal database, named FLIGHT_XLV_IFX_REF.
text: FLDA_XLV_FIELD
(
reference: FLIGHT_XLV_IFX_REF
...
)
______________________________________________________________________
FLIGHT_XLV_OCOP_REF
Reference: FLIGHT_XLV_OCOP_REF
Description:
Crossing Level at Outbound Cop for the flight.
Handler: flight
Synopsis:
FLIGHT_XLV_OCOP_REF
______________________________________________________________________
FLIGHT_XLV_OFX_REF
Reference: FLIGHT_XLV_OFX_REF
Description:
Crosssing Level at the Out Fix for the flight.
Handler: flight
Synopsis:
FLIGHT_XLV_FX1_REF
Examples:
Not used.
______________________________________________________________________
FLIGHT_XPT_REF
Reference: FLIGHT_XPT_REF
205678826.doc
UNCLASSIFIED
Page 314
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Description:
Handler: flight
Type: text
Synopsis:
FLIGHT_XPT_REF
Example:
choice: XPT
(
label: 'EXIT POINT'
field: XPT_FLD
(
text
(
reference: FLIGHT_XPT_REF
length
: 3
)
)
)
______________________________________________________________________
GROUP_IDX_REF
Reference: FLIGHT_IDX_REF
Description:
Handler: flight
Type: string
Synopsis:
GROUP_IDX_REF
Example:
text: ARR_SEP_NAME
(
length
: 4;
reference_param: AIRP_NAME_BY_GROUP_REF(GROUP_IDX_REF;)
...
)
______________________________________________________________________
MAX_MET_AIS_REF
Reference: MAX_MET_AIS_REF
Description:
Handler: flight
Type:
Synopsis:
Example:
______________________________________________________________________
MAX_PASSIVE_REF
Reference: FLIGHT_PASSIVE_REF
Description:
Handler: flight
Type:
205678826.doc
UNCLASSIFIED
Page 315
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Synopsis:
MAX_PASSIVE_REF
Example:
text: BROWSE_FS
(
#include <event_hook.dsp>
...
length
: 2;
reference: FLIGHT_PAS_FS_REF
)
______________________________________________________________________
205678826.doc
UNCLASSIFIED
Page 316
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
6.4.1.2 Alarm reference help

______________________________________________________________________
__________________________________________________
_________________________________________________
Category: Alarm
__________________________________________________
__________________________________________________
______________________________________________________________________
ALARM_CALLSIGN1_REF
Description:
This reference is used to refere the field
Callsign1 Alarm within an alarm record.
Handler: alarm
Components Usage: Tabular
Synopsis:
ALARM_CALLSIGN1_REF
Examples:
Within a Tabular text declaration:
reference: ALARM_CALLSIGN1_REF
______________________________________________________________________
ALARM_CALLSIGN2_OR_AREA_ID_REF
Description:
Callsign2 Alarm within an alarm record.
Handler: alarm
Synopsis:
ALARM_CALLSIGN2_OR_AREA_ID_REF
Examples:
reference: ALARM_CALLSIGN2_OR_AREA_ID_REF
______________________________________________________________________
ALARM_CALLSIGN_REF
Description:
Handler: alarm
______________________________________________________________________
ALARM_CCH_REF
Description:
ICM Warning Alert within an alarm record.
Handler: alarm
Synopsis:
ALARM_CCH_REF
Examples:
reference: ALARM_CCH_REF
205678826.doc
UNCLASSIFIED
Page 317
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
______________________________________________________________________
ALARM_CONF_DIST_REF
Description:
Handler: alarm
______________________________________________________________________
ALARM_CONF_NUM_REF
Description:
Conf. Num. Warning Alert within an alarm record.
Handler: alarm
Synopsis:
ALARM_CONF_NUM_REF
Examples:
reference: ALARM_CONF_NUM_REF
______________________________________________________________________
ALARM_CONF_TIME_REF
Description:
Conf. Time Warning Alert within an alarm record.
Handler: alarm
Synopsis:
ALARM_CONF_TIME_REF
Examples:
reference: ALARM_CONF_TIME_REF
______________________________________________________________________
ALARM_DAIW_REF
Description:
Danger Area Infringment Warning Alert within
an alarm record.
Handler: alarm
Synopsis:
ALARM_DAIW_REF
Examples:
reference: ALARM_DAIW_REF
______________________________________________________________________
ALARM_DA_REF
Description:
Handler: alarm
205678826.doc
UNCLASSIFIED
Page 318
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
______________________________________________________________________
ALARM_DIAL_MSG_REF
Description:
Dial. Msg. Alarm within an alarm record.
Handler: alarm
Synopsis:
ALARM_DIAL_MSG_REF
Examples:
reference: ALARM_DIAL_MSG_REF
______________________________________________________________________
ALARM_EMG_REF
Description:
Emergency Alert within an alarm record.
Handler: alarm
Synopsis:
ALARM_EMG_REF
Examples:
reference: ALARM_EMG_REF
______________________________________________________________________
ALARM_FDPAL_REF
Description:
Flight Data Processing Alert within an alarm
record.
Handler: alarm
Synopsis:
ALARM_FDPAL_REF
Examples:
reference: ALARM_FDPAL_REF
Within a Tabular action:
actions: ENTRY_PRELIMINARY_ACTION
(
switch: FDP_ALARM_REF
(
case: MTCA_CASE
(
set_template (NORMAL_TEMPLATE)
)
)
)
______________________________________________________________________
ALARM_HIJ_REF
Description:
205678826.doc
UNCLASSIFIED
Page 319
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003

Hijack Alert within an alarm record.
Handler: alarm
Synopsis:
ALARM_HIJ_REF
Examples:
reference: ALARM_HIJ_REF
______________________________________________________________________
ALARM_ICM_REF
Description:
ICM Warning Alert within an alarm record.
Handler: alarm
Synopsis:
ALARM_ICM_REF
Examples:
reference: ALARM_ICM_REF
______________________________________________________________________
ALARM_MSAW_REF
Description:
Minimum Safe Altitude Warning Alert within
an alarm record.
Handler: alarm
Synopsis:
ALARM_MSAW_REF
Examples:
reference: ALARM_MSAW_REF
______________________________________________________________________
ALARM_MTCA_REF
Description:
Handler: alarm
______________________________________________________________________
ALARM_MTCD_CONFLICT_NUMBER_REF
Description:
Handler: alarm
______________________________________________________________________
ALARM_MTCD_CS1_REF
Description:
205678826.doc
UNCLASSIFIED
Page 320
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Handler: alarm
______________________________________________________________________
ALARM_MTCD_CS2_REF
Description:
Handler: alarm
______________________________________________________________________
ALARM_MTCD_MARKER1_REF
Description:
Handler: alarm
______________________________________________________________________
ALARM_MTCD_MARKER2_REF
Description:
Handler: alarm
______________________________________________________________________
ALARM_MTCD_TFI_DISTANCE_REF
Description:
Handler: alarm
______________________________________________________________________
ALARM_MTCD_TFI_REF
Description:
Handler: alarm
______________________________________________________________________
ALARM_MTCD_TMD_DISTANCE_REF
Description:
Handler: alarm
______________________________________________________________________
ALARM_MTCD_TMD_REF
Description:
Handler: alarm
______________________________________________________________________
ALARM_OUT_REF
Description:
OUT Warning Alert within an alarm record.
Handler: alarm
Synopsis:
ALARM_OUT_REF
205678826.doc
UNCLASSIFIED
Page 321
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Examples:
reference: ALARM_OUT_REF
______________________________________________________________________
ALARM_OVL_REF
Description:
Handler: alarm
______________________________________________________________________
ALARM_PLANAR_CONV_REF
Description:
Planar Conv. Warning Alert within an alarm record.
Handler: alarm
Synopsis:
ALARM_PLANAR_CONV_REF
Examples:
reference: ALARM_PLANAR_CONV_REF
______________________________________________________________________
ALARM_RAD_REF
Description:
Radar Alert within an alarm record.
Handler: alarm
Synopsis:
ALARM_RAD_REF
Examples:
reference: ALARM_RAD_REF
______________________________________________________________________
ALARM_SCA_CS_MAC_AREA_REF
Description:
Handler: alarm
______________________________________________________________________
ALARM_SCA_CS_MAC_REF
Description:
Handler: alarm
______________________________________________________________________
ALARM_SCA_REF
Description:
-
205678826.doc
UNCLASSIFIED
Page 322
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Handler: alarm
______________________________________________________________________
ALARM_SCA_SUBTYPE_REF
Description:
Handler: alarm
______________________________________________________________________
ALARM_STCA_REF
Description:
short Term Conflict Alert within an alarm
record.
Handler: alarm
Components Usage: Tabular, Widget.
Synopsis:
ALARM_STCA_REF
Examples:
Within a Tabular field declaration:
reference: ALARM_STCA_REF
Within a Tabular action:
if (ALARM_STCA_REF)
set_template(CURR_TPL, STCA_TEMPLATE)
______________________________________________________________________
ALARM_TYPE_REF
Description:
Type Warning Alert within an alarm record.
Handler: alarm
Synopsis:
ALARM_TYPE_REF
Examples:
reference: ALARM_TYPE_REF
______________________________________________________________________
ALARM_URGENCY_REF
Description:
Urgency Warning Alert within an alarm record.
Handler: alarm
Synopsis:
ALARM_URGENCY_REF
Examples:
reference: ALARM_URGENCY_REF
______________________________________________________________________
ALARM_VERTICAL_CONV_REF
205678826.doc
UNCLASSIFIED
Page 323
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Description:
Vertical Conv. Warning Alert within an alarm record.
Handler: alarm
Synopsis:
ALARM_VERTICAL_CONV_REF
Examples:
reference: ALARM_VERTICAL_CONV_REF
______________________________________________________________________
205678826.doc
UNCLASSIFIED
Page 324
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
6.4.1.3 Supervisor reference help

______________________________________________________________________
__________________________________________________
__________________________________________________
Category: Sup
__________________________________________________
__________________________________________________
______________________________________________________________________
QNH_REF
Description:
Barometric Pressure.
Handler: sup
Type:
string
Synopsis:
QNH_REF
Examples:
One could relate the QNH_FIELD text field of the presentation object
internal database, named QNH_REF.
text: QNH_FIELD
(
reference: QNH_REF
length: 6
)
______________________________________________________________________
SUP_CH_REF
Description:
Handler: sup
______________________________________________________________________
SUP_COL_RMM_REF
Description:
Handler: sup
______________________________________________________________________
SUP_CONF_NEW_PASSW_REF
Description:
Handler: sup
______________________________________________________________________
SUP_DF_GENERAL_REF
Description:
Handler: sup
______________________________________________________________________
SUP_DF_REF
Description:
-
205678826.doc
UNCLASSIFIED
Page 325
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Handler: sup
______________________________________________________________________
SUP_ELS_NAME_REF
Description:
Local setting string.
Handler: sup
Components Usage: Widget, preview
Type:
string
Synopsis:
SUP_ELS_NAME_REF.string
Examples:
Within a Widget syntax:
In this example you can see the usage of the reference SUP_ELS_NAME_REF,
within the update syntax section.
When the referred reference SUP_ELS_NAME_REF changes, the application notifies this
change. Then, through the update section, it changes the "labelstring"
Motif widget resource, making use of the SUP_ELS_NAME_REF.string.
Label: LOCAL_SETTING
(
labelString: "
"
update: ( labelString: SUP_ELS_NAME_REF.string )
)
______________________________________________________________________
SUP_ENV_REF
Description:
ENV State into ONL, TRN, PLB.
Handler: sup
Type:
num (integer)
Synopsis:
SUP_ENV_REF.num
Examples:
In this example you can see the usage of the reference SUP_ENV_REF,
When the referred reference SUP_ENV_REF changes, the application notifies this
change. Then, through the update section, it changes the "labelString"
Motif widget resource, making use of the SUP_ENV_REF.num.
Label: STATE
(
update:
(
if SUP_ENV_REF.num = 2 then
labelString: "ONL"
else
labelString: "TRN"
else
labelString: "PLB"
else
labelString: "
"
endif
endif
endif
)
)
205678826.doc
UNCLASSIFIED
Page 326
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
______________________________________________________________________
SUP_ENV_RMM_REF
Description:
Handler: sup
______________________________________________________________________
SUP_EXPECTED_MODE_REF
Description:
Handler: sup
______________________________________________________________________
SUP_FDP_REF
Description:
Flight Data Processing.
Handler: sup
Type:
string
num ( integer )
Synopsis:
SUP_FDP_REF.num
SUP_FDP_REF.string1
SUP_FDP_REF.num1
SUP_FDP_REF.string2
SUP_FDP_REF.num2
Examples:
In this example you can see a multi usage of the reference SUP_FDP_REF,
When the referred reference SUP_FDP_REF changes, the application notifies this
change. Then, through the update section, the application creates a string used to
change the "labelstring" Motif widget resource, making use of the SUP_FDP_REF.num,
the SUP_FDP_REF.num1, SUP_FDP_REF.num2, SUP_FDP_REF.string1 and the
SUP_FDP_REF.string2.
Label: FDP_SLAVE
(
labelString: "
"
update:
(
if SUP_FDP_REF.num = 1 then
if SUP_FDP_REF.num2 = 0 then
labelString: SUP_FDP_REF.string2 +
else
labelString: SUP_FDP_REF.string2 +
endif
else
if SUP_FDP_REF.num = 2 then
labelString: SUP_FDP_REF.string1
else
endif
else
else
endif
endif
endif
)
)
"2" + "OFF"
"2"
+ "1" + "OFF"
+ "1"
+ " " + "OFF"

+ " "
______________________________________________________________________
205678826.doc
UNCLASSIFIED
Page 327
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
SUP_FUN_REF
Description:
Function State into WTC, EXE, PLN, etc.
Handler: sup
Type:
num (integer)
Synopsis:
SUP_FUN_REF.num
Examples:
In this example you can see the usage of the reference SUP_FUN_REF,
When the referred reference SUP_FUN_REF changes, the application notifies this
change. Then, through the update section, it changes the "labelString"
Motif widget resource, making use of the SUP_FUN_REF.num value.
Label: FUNCTION
(
update:
(
if SUP_FUN_REF.num = 0 then
labelString: "WTC"
else
labelString: "EXE"
else
labelString: "PLN"
else
labelString: "EXE+PLN"
else
labelString: "ASS"
else
labelString: "SUP"
endif
endif
endif
endif
endif
endif
)
______________________________________________________________________
SUP_GML_REF
Description:
Handler: sup
______________________________________________________________________
SUP_HIDDEN_CMD_REF
Description:
Handler: sup
______________________________________________________________________
SUP_ICA_REF
Description:
Handler: sup
205678826.doc
UNCLASSIFIED
Page 328
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
______________________________________________________________________
SUP_ICC_REF
Description:
Handler: sup
______________________________________________________________________
SUP_ICM_REF
Description:
Handler: sup
______________________________________________________________________
SUP_IMG_REF
Description:
Interconsole Message.
Handler: sup
Type:
string
state (boolean)
Synopsis:
SUP_IMG_REF.string
SUP_IMG_REF.state
Examples:
In this example you can see a multi usage of the reference SUP_IMG_REF,
When the referred reference SUP_IMG_REF changes his value, the application
notifies this change.
Then, through the update section, it changes the "labelString"
Motif widget resource, making use of the SUP_IMG_REF.state value.
Label: ORG_DST_LAB
(
labelString: "
"
update:
(
labelString: SUP_IMG_REF.string1
if SUP_IMG_REF.state = false then
foreground: FOREGROUND_ERROR_COL
else
foreground: LABEL_FOREGROUND_COL
endif
)
)
______________________________________________________________________
SUP_IMG_SECTOR_REF
Description:
Handler: sup
______________________________________________________________________
SUP_IMG_TEXT_REF
Description:
Handler: sup
______________________________________________________________________
205678826.doc
UNCLASSIFIED
Page 329
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
SUP_INT_ID_REF
Description:
Handler: sup
______________________________________________________________________
SUP_LCI_REF
Description:
Logical console string.
Handler: sup
Type:
string
Synopsis:
SUP_LCI_REF.string
Examples:
In this example you can see the usage of the reference SUP_LCI_REF,
When the referred reference SUP_LCI_REF changes, the application notifies this
Motif widget resource, making use of the SUP_LCI_REF.string.
Label: LOGICAL_CONSOLE
(
labelString: "
"
update: ( labelString: SUP_LCI_REF.string )
)
______________________________________________________________________
SUP_LCT_CONSOLE_REF
Description:
Handler: sup
______________________________________________________________________
SUP_LCT_REF
Description:
Handler: sup
______________________________________________________________________
SUP_LCT_SUITE_REF
Description:
Handler: sup
______________________________________________________________________
SUP_LCT_TEXT_REF
Description:
Handler: sup
______________________________________________________________________
SUP_LEVEL_REF
Description:
Handler: sup
205678826.doc
UNCLASSIFIED
Page 330
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
______________________________________________________________________
SUP_LOC_TEXT_REF
Description:
Local Text string.
Handler: sup
Type:
string
Synopsis:
SUP_LOC_TEXT_REF.string
Examples:
In this example you can see the usage of the reference SUP_LOC_TEXT_REF,
When the referred reference SUP_LOC_TEXT_REF changes, the application notifies this
Motif widget resource, making use of the SUP_LOC_TEXT_REF.string.
Label: LOC_TEXT
(
labelString: ""
update:
(
labelString: SUP_LOC_TEXT_REF.string
)
)
______________________________________________________________________
SUP_MAP_COO_LAB_REF
Description:
Handler: sup
______________________________________________________________________
SUP_MAP_COO_REF
Description:
Map Coo state.
Handler: sup
Type:
state (boolean)
Synopsis:
SUP_MAP_COO_REF#1
Examples:
In this example you can see an usage of the reference SUP_MAP_COO_REF,
When the referred reference SUP_MAP_COO_REF changes his value, for instance when
the concerning ToggleButton is pressed, the application notifies this change.
Then, through the update section, it changes the "set" Motif widget resource,
making use of the GRP_MAP_COO_REF#1.state and changes the "labelString" Motif widget
resource making use the GRP_MAP_COO_NAME_REF#1.string value.
ToggleButton: GLO1
(
labelString: "GLO1"
valueChangedCallback:
notify ( sup(SUP_MAP_COO_REF#1))
trigger( set: GRP_MAP_COO_REF#1.state
update:
(
205678826.doc
UNCLASSIFIED
Page 331
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
set: GRP_MAP_COO_REF#1.state
)
(
)
labelString: GRP_MAP_COO_NAME_REF#1.string
)
______________________________________________________________________
SUP_MAP_DNG_LAB_REF
Description:
Handler: sup
______________________________________________________________________
SUP_MAP_DNG_REF
Description:
Map Dangerous state.
Handler: sup
Type:
state (boolean)
Synopsis:
SUP_MAP_DNG_REF#1
Examples:
In this example you can see an usage of the reference SUP_MAP_DNG_REF,
When the referred reference SUP_MAP_DNG_REF changes his value, for instance when
the concerning ToggleButton is pressed, the application notifies this change.
Then, through the update section, it changes the "set" Motif widget resource,
making use of the GRP_MAP_DNG_REF#1.state and changes the "labelString" Motif widget
resource making use the GRP_MAP_DNG_NAME_REF#1.string value.
ToggleButton: GLO11
(
labelString: "GLO11"
valueChangedCallback:
notify ( sup(SUP_MAP_DNG_REF#1))
trigger( set: GRP_MAP_DNG_REF#1.state )
update:
(
set: GRP_MAP_DNG_REF#1.state
)
(
labelString: GRP_MAP_DNG_NAME_REF#1.string
)
)
______________________________________________________________________
SUP_MESSAGE_REF
Description:
Handler: sup
______________________________________________________________________
SUP_MON_STATE_REF
Description:
Monitor state.
Handler: sup
Type:
205678826.doc
num (integer)
UNCLASSIFIED
Page 332
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Synopsis:
SUP_MON_STATE_REF.num
Examples:
In this example you can see an usage of the reference SUP_MON_STATE_REF,
When the referred reference SUP_MON_STATE_REF changes his value, the application
Motif widget resource, making use of the SUP_MON_STATE_REF.num value.
Label: MONITOR_STATE
(
labelString: "
"
update:
(
if SUP_MON_STATE_REF.num = 1 then
labelString: "MONITOR"
else
if SUP_MON_STATE_REF.num = 0 then
labelString: "
"
else
labelString: "Error !"
endif
endif
)
)
______________________________________________________________________
SUP_NEW_PASSW_REF
Description:
Handler: sup
______________________________________________________________________
SUP_OLD_PASSW_REF
Description:
Handler: sup
______________________________________________________________________
SUP_PASSW_REF
Description:
Handler: sup
______________________________________________________________________
SUP_PAUSE_REF
Description:
Handler: sup
______________________________________________________________________
SUP_PHYS_CONS_REF
Description:
Phisical console string.
Handler: sup
Type:
205678826.doc
string
UNCLASSIFIED
Page 333
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Synopsis:
SUP_PHYS_CONS_REF.string
Examples:
In this example you can see the usage of the reference SUP_PHYS_CONS_REF,
When the referred reference SUP_PHYS_CONS_REF changes, the application notifies this
Motif widget resource, making use of the SUP_PHYS_CONS_REF.string.
Label: PHISICAL_CONSOLE
(
labelString: "
"
update: ( labelString: SUP_PHYS_CONS_REF.string )
)
______________________________________________________________________
SUP_PLOT_PSC_REF
Description:
number of secondary plots.
Handler: sup
Type:
num ( integer )
Synopsis:
SUP_PLOT_PSC_REF.num
______________________________________________________________________
SUP_PLOT_PSR_REF
Description:
number of primary plots.
Handler: sup
Type:
num ( integer )
Synopsis:
SUP_PLOT_PSR_REF.num
______________________________________________________________________
SUP_QNH_VALUE1_REF
Description:
Barometric Pressure value 1.
Handler: sup
Type:
string
Synopsis:
SUP_QNH_VALUE1_REF
Examples:
One could relate the referred text field, of the flight
internal database, named SUP_QNH_VALUE1_REF.
text
(
reference: SUP_QNH_VALUE1_REF
length: 4
)
205678826.doc
UNCLASSIFIED
Page 334
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
______________________________________________________________________
SUP_QNH_VALUE2_REF
Description:
Barometric Pressure value 2.
Handler: sup
Type:
string
Synopsis:
SUP_QNH_VALUE2_REF
Examples:
One could relate the referred text field, of the flight
internal database, named SUP_QNH_VALUE2_REF.
text
(
reference: SUP_QNH_VALUE2_REF
length: 1
)
______________________________________________________________________
SUP_RADAR_NAME_REF
Description:
Handler: sup
______________________________________________________________________
SUP_RAD_LIST_DISSNAME_REF
Description:
Radar List Disseminator Name.
Handler: sup
Type:
string
Synopsis:
SUP_RAD_LIST_DISSNAME_REF.string
Examples:
In this example you can see an usage of the reference SUP_RAD_LIST_DISSNAME_REF,
When the referred reference SUP_RAD_LIST_DISSNAMEUS_REF changes his value,
the application notifies this change.
Motif widget resource, making use of the SUP_RAD_LIST_DISSNAME_REF#2.string.
Label:
(
labelString: "
"
update:
(
labelString: SUP_RAD_LIST_DISSNAME_REF#2.string
)
)
______________________________________________________________________
SUP_RAD_LIST_RADCHAN_REF
Description:
Radar List Channel.
205678826.doc
UNCLASSIFIED
Page 335
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Handler: sup
Type:
string
Synopsis:
SUP_RAD_LIST_RADCHAN_REF.string
Examples:
In this example you can see an usage of the reference SUP_RAD_LIST_RADCHAN_REF,
When the referred reference SUP_RAD_LIST_RADSTATUS_REF changes his value,
Motif widget resource, making use of the SUP_RAD_LIST_RADSTATUS_REF#2.state and
the SUP_RAD_LIST_RADSTATUS_REF#2.string.
Label:
(
labelString: " "
update:
(
labelString: SUP_RAD_LIST_RADCHAN_REF#2.string
)
(
if SUP_RAD_LIST_RADSTATUS_REF#2.state = false then
labelString: ""
else
labelString: SUP_RAD_LIST_RADSTATUS_REF#2.string
endif
)
)
______________________________________________________________________
SUP_RAD_LIST_RADNAME_REF
Description:
Radar List Name.
Handler: sup
Type:
state (boolean)
Synopsis:
SUP_RAD_LIST_RADNAME_REF.string
Examples:
In this example you can see an usage of the reference SUP_RAD_LIST_RADNAME_REF,
Then, through the update section, it changes the "foreground"
Motif widget resource, making use of the SUP_RAD_LIST_RADSTATUS_REF.state value.
Label:
(
labelString: " "
update:
(
labelString: SUP_RAD_LIST_RADNAME_REF#2.string
)
(
foreground: FOREGROUND_ERROR_COL
else
foreground: LABEL_FOREGROUND_COL
endif
)
)
______________________________________________________________________
205678826.doc
UNCLASSIFIED
Page 336
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
SUP_RAD_LIST_RADSTATUS_REF
Description:
Radar List Status.
Handler: sup
Type:
string
state (boolean)
Synopsis:
SUP_RAD_LIST_RADSTATUS_REF.string
SUP_RAD_LIST_RADSTATUS_REF.state
Examples:
In this example you can see a multi usage of the reference SUP_RAD_LIST_RADSTATUS_REF,
Then, through the update section, it changes the "foreground"
Motif widget resource, making use of the SUP_RAD_LIST_RADSTATUS_REF#2.state value and
the SUP_RAD_LIST_RADSTATUS_REF#2.string value.
Label:
(
labelString: " "
update:
(
labelString: SUP_RAD_LIST_RADCHAN_REF#2.string
)
(
labelString: ""
else
labelString: SUP_RAD_LIST_RADSTATUS_REF#2.string
endif
)
)
______________________________________________________________________
SUP_RAD_MODE_REF
Description:
Rad Mode.
Handler: sup
Type:
num (integer)
Synopsis:
SUP_RAD_MODE_REF.num
Examples:
In this example you can see an usage of the reference SUP_RAD_MODE_REF,
When the referred reference SUP_RAD_MODE_REF changes his value, the application
Motif widget resource, making use of the SUP_RAD_MODE_REF.num value.
Label: STATUS
(
labelString: "
"
update:
(
if SUP_RAD_MODE_REF.num = 0 then
labelString: "DARD"
else
205678826.doc
UNCLASSIFIED
Page 337
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
if SUP_RAD_MODE_REF.num = 1 then
labelString: "MRT"
endif
endif
)
______________________________________________________________________
SUP_RANGE_REF
Description:
Handler: sup
______________________________________________________________________
SUP_RCS_RMM_REF
Description:
Handler: sup
______________________________________________________________________
SUP_RDP_REF
Description:
Radar Data Processing.
Handler: sup
Type:
string
num ( integer )
Synopsis:
SUP_RDP_REF.num
SUP_RDP_REF.string1
SUP_RDP_REF.num1
SUP_RDP_REF.string2
SUP_RDP_REF.num2
Examples:
In this example you can see a multi usage of the reference SUP_RDP_REF,
When the referred reference SUP_RDP_REF changes, the application notifies this
Motif widget resource, making use of the SUP_RDP_REF.num, the SUP_RDP_REF.num1,
SUP_RDP_REF.num2, SUP_RDP_REF.string1, SUP_RDP_REF.string2.
Label: RDP_SLAVE
(
labelString: "
"
update:
(
if SUP_RDP_REF.num = 1 then
if SUP_RDP_REF.num2 = 0 then
labelString: SUP_RDP_REF.string2 +
else
labelString: SUP_RDP_REF.string2 +
endif
else
if SUP_RDP_REF.num = 2 then
labelString: SUP_RDP_REF.string1
else
endif
else
else
endif
205678826.doc
"2" + "OFF"
"2"
+ "1" + "OFF"
+ "1"
+ " " + "OFF"

+ " "
UNCLASSIFIED
Page 338
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
endif
endif
)
______________________________________________________________________
SUP_RFB_REF
Description:
Radar Data Processing.
Handler: sup
Type:
string
num ( integer )
Synopsis:
SUP_RFB_REF.num
SUP_RFB_REF.string1
SUP_RFB_REF.num1
SUP_RFB_REF.string2
SUP_RFB_REF.num2
Examples:
In this example you can see a multi usage of the reference SUP_RFB_REF,
When the referred reference SUP_RFB_REF changes, the application notifies this
Motif widget resource, making use of the SUP_RFB_REF.num, the SUP_RFB_REF.num1,
SUP_RFB_REF.num2, SUP_RFB_REF.string1, SUP_RFB_REF.string2.
Label: RDP_SLAVE
(
labelString: "
"
update:
(
if SUP_RFB_REF.num = 1 then
if SUP_RFB_REF.num2 = 0 then
labelString: SUP_RFB_REF.string2 +
else
labelString: SUP_RFB_REF.string2 +
endif
else
if SUP_RFB_REF.num = 2 then
labelString: SUP_RFB_REF.string1
else
endif
else
else
endif
endif
endif
)
)
"2" + "OFF"
"2"
+ "1" + "OFF"
+ "1"
+ " " + "OFF"

+ " "
______________________________________________________________________
SUP_SECTOR_FAM_REF
Description:
Sector Family Table into TWR, APP, etc.
Handler: sup
Type:
num (integer)
Synopsis:
205678826.doc
UNCLASSIFIED
Page 339
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
SUP_SECTOR_FAM_REF.num
Examples:
In this example you can see the usage of the reference SUP_WORK_MODE_REF,
When the referred reference SUP_SECTOR_FAM_REF changes, the application
Motif widget resource, making use of the SUP_SECTOR_FAM_REF.num.
Label: CONTROLLED_TYPE
(
labelString: "
"
update:
(
if SUP_SECTOR_FAM_REF.num = 0 then
labelString: "TWR"
else
labelString: "APP"
else
labelString: "ACC"
else
labelString: " "
else
labelString: "
"
endif
endif
endif
endif
)
)
______________________________________________________________________
SUP_SECTOR_FREQUENCY_REF
Description:
Handler: sup
______________________________________________________________________
SUP_SECTOR_ID_REF
Description:
Handler: sup
______________________________________________________________________
SUP_SECTOR_LIST_REF
Description:
Sector List string.
Handler: sup
Type:
string
Synopsis:
SUP_SECTOR_LIST_REF.string
Examples:
In this example you can see the usage of the reference SUP_SECTOR_LIST_REF,
When the referred reference SUP_SECTOR_LIST_REF changes, the application
notifies this change. Then, through the update section, it changes the "value"
Motif widget resource, making use of the SUP_SECTOR_LIST_REF.string.
205678826.doc
UNCLASSIFIED
Page 340
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
ScrolledText: SECTOR_LIST
(
update:
(
value: SUP_SECTOR_LIST_REF.string
)
)
______________________________________________________________________
SUP_SECTOR_REF
Description:
Sector Name string.
Handler: sup
Type:
string
Synopsis:
SUP_SECTOR_REF.string
Examples:
In this example you can see the usage of the reference SUP_SECTOR_REF,
When the referred reference SUP_SECTOR_REF changes, the application notifies this
Motif widget resource, making use of the SUP_SECTOR_REF.string.
Label: SECTOR_NAME
(
labelString: "
"
update: ( labelString: SUP_SECTOR_REF.string )
)
______________________________________________________________________
SUP_SIM_EXER_REF
Description:
Handler: sup
______________________________________________________________________
SUP_SLC_AUX_DIM_REF
Description:
Auxiliary window(BIG/SMALL).
Handler: sup
Type:
state (boolean)
Synopsis:
SUP_SLC_AUX_DIM_REF.state
Examples:
In this example you can see an usage of the reference SUP_SLC_AUX_DIM_REF,
When the referred reference SUP_SLC_AUX_DIM_REF changes his value, for instance
when the corrispondent ToggleButton is pressed, the application notifies this change.
Then, through the update section, it changes the "set" and the "labelString"
Motif widget resources, making use of the SUP_SLC_AUX_DIM_REF.state value.
ToggleButton: GRP_DIM
(
labelString: "SMALL"
205678826.doc
UNCLASSIFIED
Page 341
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
valueChangedCallback: notify ( SUP_SLC_AUX_DIM_REF )

update:
(
set: SUP_SLC_AUX_DIM_REF.state
if SUP_SLC_AUX_DIM_REF.state then
labelString: "BIG"
else
endif
)
______________________________________________________________________
SUP_SLC_AUX_RIG_REF
______________________________________________________________________
SUP_SLC_AUX_SCREEN_REF
______________________________________________________________________
SUP_SLC_AUX_TOP_REF
______________________________________________________________________
SUP_SLC_AUX_VIS_REF
______________________________________________________________________
SUP_SLC_CHECK_ATCWINDOW
Description:
Check ATC window string on the "Slc" Interface.
Handler: sup
Type:
string
Synopsis:
SUP_SLC_CHECK_ATCWINDOW.string
Examples:
In this example you can see an usage of the reference SUP_SLC_CHECK_ATCWINDOW,
When the referred reference SUP_SLC_CHECK_ATCWINDOW changes his value,
Then, through the update section, it changes the "value" Motif widget resources,
making use of the SUP_SLC_CHECK_OVERLAP.string and the SUP_SLC_CHECK_ATCWINDOW.string
values for a string creation.
TextField:
(
cursorPositionVisible: False
resizeWidth: False
update:
(
value: SUP_SLC_CHECK_OVERLAP.string + SUP_SLC_CHECK_ATCWINDOW.string
)
)
______________________________________________________________________
SUP_SLC_CHECK_OVERLAP
Description:
Check Overlap string on the "Slc" Interface.
Handler: sup
205678826.doc
UNCLASSIFIED
Page 342
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
Type:
D
28/02/2003
string
Synopsis:
SUP_SLC_CHECK_OVERLAP.string
Examples:
In this example you can see an usage of the reference SUP_SLC_CHECK_OVERLAP,
When the referred reference SUP_SLC_CHECK_OVERLAP changes his value,
Then, through the update section, it changes the "value" Motif widget resources,
making use of the SUP_SLC_CHECK_OVERLAP.string and the SUP_SLC_CHECK_ATCWINDOW.string
values for a string creation.
TextField:
(
cursorPositionVisible: False
resizeWidth: False
update:
(
value: SUP_SLC_CHECK_OVERLAP.string + SUP_SLC_CHECK_ATCWINDOW.string
)
)
______________________________________________________________________
SUP_SLC_ESB_DIM_REF
Description:
Electronic Strip Bay Window Dimension state (BIG/SMALL).
Handler: sup
Type:
state (boolean)
Synopsis:
SUP_SLC_ESB_DIM_REF.state
Examples:
In this example you can see an usage of the reference SUP_SLC_ESB_DIM_REF,
When the referred reference SUP_SLC_ESB_DIM_REF changes his value, for instance
Motif widget resources, making use of the SUP_SLC_ESB_DIM_REF.state value.
ToggleButton: ESB_DIM
(
valueChangedCallback: notify ( SUP_SLC_ESB_DIM_REF )
update:
(
set: SUP_SLC_ESB_DIM_REF.state
if SUP_SLC_ESB_DIM_REF.state then
labelString: "BIG"
else
endif
)
)
______________________________________________________________________
SUP_SLC_ESB_RIG_REF
Description:
Electronic Strip Bay Window Right/Left state.
Handler: sup
205678826.doc
UNCLASSIFIED
Page 343
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
Type:
D
28/02/2003
state (boolean)
Synopsis:
SUP_SLC_ESB_RIG_REF.state
Examples:
In this example you can see an usage of the reference SUP_SLC_ESB_RIG_REF,
When the referred reference SUP_SLC_ESB_RIG_REF changes his value, for instance
Motif widget resources, making use of the SUP_SLC_ESB_RIG_REF.state value.
ToggleButton: ESB_RIG
(
labelString: "LEFT"
valueChangedCallback: notify ( SUP_SLC_ESB_RIG_REF )
update:
(
set: SUP_SLC_ESB_RIG_REF.state
if SUP_SLC_ESB_RIG_REF.state then
labelString: "RIGHT"
else
labelString: "LEFT"
endif
)
)
______________________________________________________________________
SUP_SLC_ESB_SCREEN_REF
Description:
Electronic Strip Bay Window screen.
Handler: sup
Type:
state (boolean)
Synopsis:
SUP_SLC_ESB_SCREEN_REF.state
Examples:
In this example you can see an usage of the reference SUP_SLC_ESB_SCREEN_REF,
When the referred reference SUP_SLC_ESB_SCREEN_REF changes his value, for instance
Motif widget resources, making use of the SUP_SLC_ESB_SCREEN_REF.state value.
ToggleButton: ESB_SCREEN
(
labelString: "SCREEN: 0"
valueChangedCallback: notify ( SUP_SLC_ESB_SCREEN_REF )
update:
(
set: SUP_SLC_ESB_SCREEN_REF.state
if SUP_SLC_ESB_SCREEN_REF.state then
else
endif
)
)
______________________________________________________________________
SUP_SLC_ESB_TOP_REF
Description:
Electronic Strip Bay Window Top/Bottom state.
205678826.doc
UNCLASSIFIED
Page 344
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Handler: sup
Type:
state (boolean)
Synopsis:
SUP_SLC_ESB_TOP_REF.state
Examples:
In this example you can see an usage of the reference SUP_SLC_ESB_TOP_REF,
When the referred reference SUP_SLC_ESB_TOP_REF changes his value, for instance
Motif widget resources, making use of the SUP_SLC_ESB_TOP_REF.state value.
ToggleButton: ESB_TOP
(
labelString: "DOWN"
valueChangedCallback: notify ( SUP_SLC_ESB_TOP_REF )
update:
(
set: SUP_SLC_ESB_TOP_REF.state
if SUP_SLC_ESB_TOP_REF.state then
labelString: "UP"
else
labelString: "DOWN"
endif
)
)
______________________________________________________________________
SUP_SLC_ESB_VIS_REF
Description:
Electronic Strip Bay Window Visual state.
Handler: sup
Type:
state (boolean)
Synopsis:
SUP_SLC_ESB_VIS_REF.state
Examples:
In this example you can see an usage of the reference SUP_SLC_ESB_VIS_REF,
When the referred reference SUP_SLC_ESB_VIS_REF changes his value, for instance
Motif widget resources, making use of the SUP_SLC_ESB_VIS_REF.state value.
ToggleButton: ESB_VIS
(
labelString: "OFF"
valueChangedCallback: notify ( SUP_SLC_ESB_VIS_REF )
update:
(
set: SUP_SLC_ESB_VIS_REF.state
if SUP_SLC_ESB_VIS_REF.state then
labelString: "ON"
else
labelString: "OFF"
endif
)
)
______________________________________________________________________
SUP_SLC_GRP_DIM_REF
205678826.doc
UNCLASSIFIED
Page 345
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Description:
General Radar Picture Dimension state (BIG/SMALL).
Handler: sup
Type:
state (boolean)
Synopsis:
SUP_SLC_GRP_DIM_REF.state
Examples:
In this example you can see an usage of the reference SUP_SLC_GRP_DIM_REF,
When the referred reference SUP_SLC_GRP_DIM_REF changes his value, for instance
Motif widget resources, making use of the SUP_SLC_GRP_DIM_REF.state value.
ToggleButton: GRP_DIM
(
valueChangedCallback: notify ( SUP_SLC_GRP_DIM_REF )
update:
(
set: SUP_SLC_GRP_DIM_REF.state
if SUP_SLC_GRP_DIM_REF.state then
labelString: "BIG"
else
endif
)
)
______________________________________________________________________
SUP_SLC_GRP_RIG_REF
Description:
General Radar Picture Right/Left state.
Handler: sup
Type:
state (boolean)
Synopsis:
SUP_SLC_GRP_RIG_REF.state
Examples:
In this example you can see an usage of the reference SUP_SLC_GRP_RIG_REF,
When the referred reference SUP_SLC_GRP_RIG_REF changes his value, for instance
Motif widget resources, making use of the SUP_SLC_GRP_RIG_REF.state value.
ToggleButton: GRP_RIG
(
labelString: "LEFT"
valueChangedCallback: notify ( SUP_SLC_GRP_RIG_REF )
update:
(
set: SUP_SLC_GRP_RIG_REF.state
if SUP_SLC_GRP_RIG_REF.state then
labelString: "RIGHT"
else
labelString: "LEFT"
endif
)
)
205678826.doc
UNCLASSIFIED
Page 346
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
______________________________________________________________________
SUP_SLC_GRP_SCREEN_REF
Description:
General Radar Picture screen.
Handler: sup
Type:
state (boolean)
Synopsis:
SUP_SLC_GRP_SCREEN_REF.state
Examples:
In this example you can see an usage of the reference SUP_SLC_GRP_SCREEN_REF,
When the referred reference SUP_SLC_GRP_SCREEN_REF changes his value, for instance
Motif widget resources, making use of the SUP_SLC_GRP_SCREEN_REF.state value.
ToggleButton: GRP_SCREEN
(
valueChangedCallback: notify ( SUP_SLC_GRP_SCREEN_REF )
update:
(
set: SUP_SLC_GRP_SCREEN_REF.state
if SUP_SLC_GRP_SCREEN_REF.state then
else
endif
)
)
______________________________________________________________________
SUP_SLC_GRP_TOP_REF
Description:
General Radar Picture Top/Bottom state.
Handler: sup
Type:
state (boolean)
Synopsis:
SUP_SLC_GRP_TOP_REF.state
Examples:
In this example you can see an usage of the reference SUP_SLC_GRP_TOP_REF,
When the referred reference SUP_SLC_GRP_TOP_REF changes his value, for instance
Motif widget resources, making use of the SUP_SLC_GRP_TOP_REF.state value.
ToggleButton: GRP_TOP
(
labelString: "DOWN"
valueChangedCallback: notify ( SUP_SLC_GRP_TOP_REF )
update:
(
set: SUP_SLC_GRP_TOP_REF.state
if SUP_SLC_GRP_TOP_REF.state then
labelString: "UP"
else
205678826.doc
UNCLASSIFIED
Page 347
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
labelString: "DOWN"
endif
)
______________________________________________________________________
SUP_SLC_GRP_VIS_REF
Description:
General Radar Picture Visual state.
Handler: sup
Type:
state (boolean)
Synopsis:
SUP_SLC_GRP_VIS_REF.state
Examples:
In this example you can see an usage of the reference SUP_SLC_GRP_VIS_REF,
When the referred reference SUP_SLC_GRP_VIS_REF changes his value, for instance
Motif widget resources, making use of the SUP_SLC_GRP_VIS_REF.state value.
ToggleButton: GRP_VIS
(
labelString: "OFF"
valueChangedCallback: notify ( SUP_SLC_GRP_VIS_REF )
update:
(
set: SUP_SLC_GRP_VIS_REF.state
if SUP_SLC_GRP_VIS_REF.state then
labelString: "ON"
else
labelString: "OFF"
endif
)
)
______________________________________________________________________
SUP_SLC_MMA_SCREEN_REF
Description:
Main Menu Area Window screen.
Handler: sup
Type:
state (boolean)
Synopsis:
SUP_SLC_MMA_SCREEN_REF.state
Examples:
In this example you can see an usage of the reference SUP_SLC_MMA_SCREEN_REF,
When the referred reference SUP_SLC_MMA_SCREEN_REF changes his value, for instance
Motif widget resources, making use of the SUP_SLC_MMA_SCREEN_REF.state value.
ToggleButton: MMA_SCREEN
(
valueChangedCallback: notify ( SUP_SLC_MMA_SCREEN_REF )
update:
(
205678826.doc
UNCLASSIFIED
Page 348
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
set: SUP_SLC_MMA_SCREEN_REF.state
if SUP_SLC_MMA_SCREEN_REF.state then
else
endif
)
______________________________________________________________________
SUP_SLC_MMA_TOP_REF
Description:
Main Menu Area Window Top/Bottom state.
Handler: sup
Type:
state (boolean)
Synopsis:
SUP_SLC_MMA_TOP_REF.state
Examples:
In this example you can see an usage of the reference SUP_SLC_MMA_TOP_REF,
When the referred reference SUP_SLC_MMA_TOP_REF changes his value, for instance
Motif widget resources, making use of the SUP_SLC_MMA_TOP_REF.state value.
ToggleButton: MMA_TOP
(
labelString: "DOWN"
valueChangedCallback: notify ( SUP_SLC_MMA_TOP_REF )
update:
(
set: SUP_SLC_MMA_TOP_REF.state
if SUP_SLC_MMA_TOP_REF.state then
labelString: "UP"
else
labelString: "DOWN"
endif
)
)
______________________________________________________________________
SUP_SLC_REF
Description:
Enter or Cancel PushButton on the "Slc" Interface.
Handler: sup
Type:
state (boolean)
Synopsis:
SUP_SLC_REF#enter.state
SUP_SLC_REF#cancel.state
Examples:
In this example you can see an usage of the reference SUP_SLC_REF,
When the referred reference SUP_SLC_REF changes his value, for instance
when the corrispondent PushButton is pressed, the application notifies this change.
Motif widget resources, making use of the SUP_SLC_REF#enter.state value.
PushButton: ENTER
205678826.doc
UNCLASSIFIED
Page 349
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
(
labelString: "ENTER"
foreground: SDA_WRITABLE_COL
activateCallback:
notify
(
SUP_SLC_GRP_VIS_REF
state: .GRP_VIS.set
)
( SUP_SLC_REF#enter )
trigger
(
if ~SUP_SLC_REF#enter.state then
f.popdown: SLC
endif
)
)
______________________________________________________________________
SUP_SLC_REFRESH
Description:
Check ATC window string on the "Slc" Interface.
Handler: sup
Type:
string
Synopsis:
SUP_SLC_REFRESH
Examples:
In this example you can see an usage of the reference SUP_SLC_REFRESH,
When the referred reference SUP_SLC_REFRESH changes his value,
popupCallback:
notify
(
SUP_SLC_REFRESH
)
______________________________________________________________________
SUP_SLS_INDEX_REF
Description:
Store Local Setting index string.
Handler: sup
Type:
string
Synopsis:
SUP_SLS_INDEX_REF
______________________________________________________________________
SUP_SLS_NAME_REF
Description:
Store Local Setting name string.
Handler: sup
Type:
205678826.doc
string
UNCLASSIFIED
Page 350
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Synopsis:
SUP_SLS_NAME_REF
______________________________________________________________________
SUP_SOF_RDP_REF
Description:
Handler: sup
______________________________________________________________________
SUP_SOF_RFB_REF
Description:
Handler: sup
______________________________________________________________________
SUP_SPFBIT_REF
Description:
Handler: sup
______________________________________________________________________
SUP_SPF_REF
Description:
Handler: sup
______________________________________________________________________
SUP_SPV_PRIV_REF
Description:
Privilege string.
Handler: sup
Type:
num
Synopsis:
SUP_SPV_PRIV_REF.num
Examples:
In this example you can see the usage of the reference SUP_SPV_PRIV_REF,
When the referred reference SUP_SPV_PRIV_REF changes his value, the application
notifies this change. Then, through the update section, it changes the "labelstring"
Motif widget resource, making use of the SUP_SPV_PRIV_REF.num value.
Label: PRIVILEGE
(
labelString: "
"
update:
(
if SUP_SPV_PRIV_REF.num = 0 then
labelString: "
"
else
labelString: "SUP"
endif
)
)
______________________________________________________________________
SUP_STATE_RDP_REF
205678826.doc
UNCLASSIFIED
Page 351
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Description:
Handler: sup
______________________________________________________________________
SUP_STATE_RFB_REF
Description:
Handler: sup
______________________________________________________________________
SUP_SUITE_REF
Description:
Handler: sup
______________________________________________________________________
SUP_TAB_REF
Description:
Handler: sup
______________________________________________________________________
SUP_TRACK_CONVENTIONAL_REF
Description:
number of conventional tracks.
Handler: sup
Type:
num ( integer )
Synopsis:
SUP_TRACK_CONVENTIONAL_REF.num
______________________________________________________________________
SUP_TRACK_MODES_REF
Description:
number of modes tracks.
Handler: sup
Type:
num ( integer )
Synopsis:
SUP_TRACK_MODES_REF.num
______________________________________________________________________
SUP_TRACK_TO_REF
Description:
number of modes tracks coming from adjacent station.
Handler: sup
Type:
205678826.doc
num ( integer )
UNCLASSIFIED
Page 352
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
Synopsis:
SUP_TRACK_TO_REF.num
______________________________________________________________________
SUP_UNIT_MEASURE_REF
Description:
Handler: sup
______________________________________________________________________
SUP_WORK_MODE_REF
Description:
Operative State into operative, standby, disable etc.
Handler: sup
Type:
num (integer)
Synopsis:
SUP_WORK_MODE_REF.num
Examples:
In this example you can see the usage of the reference SUP_WORK_MODE_REF,
When the referred reference SUP_WORK_MODE_REF changes, the application
Motif widget resource, making use of the SUP_WORK_MODE_REF.num.
Label: OPERATIVE_STATE
(
update:
(
if SUP_WORK_MODE_REF.num = 0 then
labelString: "
"
else
labelString: "OPS"
else
labelString: "SBY"
else
labelString: "FAI"
else
labelString: "DSD"
endif
endif
endif
endif
endif
)
)
______________________________________________________________________
SYSTEM_TIME_REF
Description:
Handler: sup
______________________________________________________________________
205678826.doc
UNCLASSIFIED
Page 353
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
TLV_REF
Description:
Handler: sup
______________________________________________________________________
__________________________________________________
205678826.doc
UNCLASSIFIED
Page 354
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
LIST OF FIGURES
FIG._ 1-1 TABULAR PARSING AND COMPILING PHASES.....................................2

FIG.__ 3.1-1 FLDI TABULAR COMPONENT GRAPHICAL APPEARANCE
EXAMPLE.............................................................................................................................6
FIG.__ 3.2-2 LOADING A TABULAR COMPONENT FROM I.E.S. TABULAR
MAIN MENU........................................................................................................................7
FIG.__ 3.2-3 TABULAR COMPONENT ("ARR") STRUCTURAL TREE..................8
FIG.__ 3.2-4 TABULAR COMPONENT ("ARR") PREVIEW......................................9
FIG.__ 3.2-5 TABULAR COMPONENT ("ARR") PREVIEW WITH LAYOUT
FRAME..................................................................................................................................9
FIG.___ 3.2.1-1 PICKING A TEXTFIELD ON THE BLACKBOARD........................10
FIG.___ 3.2.1-2 PICKING A PRIMITIVEP_CSL_ENTRY_BOTTOM_SYMBOL,
REFERRED BY A SYMBOLFIELD, ON THE BLACKBOARD OF THE CSL
TABLE.................................................................................................................................11
FIG.__ 3.3-6 OPENING THE PROPERTIES EDITOR FOR TABLE NODE............12
FIG.__ 3.3-7 TABLE NODE PROPERTIES EDITOR (1ST HALF)............................13
FIG.__ 3.3-8 TABLE NODE PROPERTIES EDITOR (2ND HALF)...........................14
FIG.__ 3.3-9 TABLE LIST PROPERTIES EDITOR (1-ST PART).............................18
FIG.__ 3.3-10 TABLE LIST NODE PROPERTIES EDITOR (2-ND PART)..............21
FIG.___ 3.3.1-3 TABLE NODE "EVENTS" RESOURCE EXAMPLE.......................22
FIG.___ 3.3.2-4 TABLE NODE "GROUPS" RESOURCE EXAMPLE.......................23
FIG.___ 3.3.3-5 TABLE NODE "ACTIONS" RESOURCE EXAMPLE.....................24
205678826.doc
UNCLASSIFIED
Page 355
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
FIG.___ 3.3.4-6 TABLE NODE "ASSIGN" RESOURCE EDITOR ............................26

FIG.__ 3.4-11 TABLE TITLE GRID AND STRUCTURE.............................................27
FIG.___ 3.4.1-7 OPENING THE PROPERTIES EDITOR FOR A TITLE
TEXTFIELD FROM THE PREVIEWER.......................................................................29
FIG.___ 3.4.1-8 PROPERTIES EDITOR FOR TITLE TEXTFIELD "ARR_TITLE"
...............................................................................................................................................30
FIG.___ 3.4.1-9 "REFERENCE_PARAM" EDITOR FOR "ARR_SEP_NAME"
TEXTFIELD........................................................................................................................32
FIG.____ 3.4.1.1-1 SELECTING A GRAPHICAL ATTRIBUTE FOR THE
TEXTFIELD "ARR_TITLE"...........................................................................................34
FIG.____ 3.4.1.2-2 CSL TABLE WITH THE FIELD REFERRING
P_CSL_ENTRY_BOTTOM_SYMBOL MULTI PRIMITIVE SELECTED..........35
FIG.____ 3.4.1.2-3 PROPERTIES EDITOR OF THE
P_CSL_ENTRY_BOTTOM_SYMBOL MULTI PRIMITIVE.................................36
FIG.____ 3.4.1.2-4 SIL TABLE WITH P_SIL_ENTRY_BOTTOM_SYMBOL
MULTI PRIMITIVE SELECTED....................................................................................36
FIG.____ 3.4.1.2-5 PROPERTIES EDITOR OF THE
P_SIL_ENTRY_BOTTOM_SYMBOL MULTI PRIMITIVE..................................37
FIG.____ 3.4.1.2-6 RUNTIME REPRESENTATION OF CSL AND SIL TABLES
...............................................................................................................................................38
FIG.____ 3.4.1.2-7 PROPERTIES EDITOR FOR TITLE SYMBOLFIELD
"ARR_MOVING"..............................................................................................................39
FIG.____ 3.4.1.3-8 PROPERTIES EDITOR FOR THE RECTANGLE GRAPHICAL
PRIMITIVE ("P_ARR_MOVING") RELATED TO THE SYMBOLFIELD
"ARR_MOVING"..............................................................................................................40
FIG.____ 3.4.1.4-9 PROPERTIES EDITOR FOR THE PRIMITIVE GRAPHICAL
ATTRIBUTE "A_BORDER" AND VIEWING THE SYMBOL STYLE ASSIGNED
("OUTLINE0")...................................................................................................................41
FIG.__ 3.5-12 TABLE HEADER GRID AND STRUCTURE........................................42
205678826.doc
UNCLASSIFIED
Page 356
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
FIG.__ 3.6-13 TABLE LIST GRID AND STRUCTURE................................................44

FIG.___ 3.6.1-10 PROPERTIES EDITOR FOR A LIST ENTRYTEXTFIELD
("ARR_ETL").....................................................................................................................46
FIG.____ 3.6.1.1-10 "EVENTS" RESOURCE FOR THE ENTRYTEXTFIELD
"ARR_ETL"........................................................................................................................48
FIG.____ 3.6.1.2-11 PROPERTIES EDITOR FOR A LIST ENTRYTEXTFIELD
("ARR_CS")........................................................................................................................52
FIG.____ 3.6.1.2-12 "ACTIONS" RESOURCE FOR THE ENTRYTEXTFIELD
"ARR_CS"..........................................................................................................................53
FIG.__ 3.7-14 LOADING THE "ESB" (ENTRY STRIP BAY) TABLE:
STRUCTURAL TREE VIEW (1ST).................................................................................54
STRUCTURAL TREE VIEW (2ND)................................................................................55
STRUCTURAL TREE VIEW (3RD)................................................................................56
FIG.__ 3.7-17 "ESB" TABLE PREVIEW........................................................................57
FIG.__ 3.7-18 "ESB_IN_FIX" ENTRYTEXTFIELD STRUCTURE DECLARATION
PROPERTIES EDITOR....................................................................................................58
FIG.__ 3.7-19 SELECTING A TEMPLATE....................................................................58
FIG.__ 3.7-20 APPLYING "ESB_ARR_ACT_TEMPLATE": STRUCTURAL TREE
VIEW....................................................................................................................................59
FIG.__ 3.7-21 APPLYING "ESB_ARR_ACT_TEMPLATE": TABLE PREVIEW...60
FIG.___ 3.7.1-11 ENTRYTEXTFIELD WITHIN "ESB_ARR_ACT_TEMPLATE"
TEMPLATE DECLARATION
PROPERTIES EDITOR.........................................61
FIG.___ 3.7.2-12 PROPERTIES EDITOR FOR "ESB_ARR_ACT_TEMPLATE"...63
FIG.___ 3.7.2-13 SELECTING A BOTTOM SYMBOL FOR THE
SIL_NORMAL_TEMPLATE........................................................................................65
205678826.doc
UNCLASSIFIED
Page 357
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
FIG___ 3.7.2.1-1 EDITOR FOR "ENTRY TEMPLATE SORT"

"ESB_ARR_ACT_TEMPLATE" RESOURCE..............................................................66
FIG._____ 3.7.3.1.2-1 TABLE "ACTIONS" SYNTAX FOR FLIGHT TYPE
LAYOUT..............................................................................................................................72
FIG._____ 3.7.3.1.3-2 "ESB_DEP_PEN_TEMPLATE" ENTRYTEMPLATE
FIG._____ 3.7.3.1.3-3 "SORT_TEMPLATE" RESOURCE SYNTAX WITHIN THE
"ESB_DEP_PEN_TEMPLATE" PROPERTIES EDITOR...........................................73
FIG._____ 3.7.3.1.3-4 "ESB_ARR_PEN_TEMPLATE" ENTRYTEMPLATE
"ESB_ARR_PEN_TEMPLATE" PROPERTIES EDITOR..........................................74
FIG._____ 3.7.3.1.3-6 "ESB_ENR_PEN_TEMPLATE" ENTRYTEMPLATE
"ESB_ENR_PEN_TEMPLATE" PROPERTIES EDITOR..........................................75
FIG._____ 3.7.3.1.3-8 TABLE "ACTIONS" SYNTAX ENTRIES ORDERING BY
FLIGHT TYPE...................................................................................................................76
FIG._____ 3.7.3.1.4-9 "GROUPS" TABLE RESOURCE EDITING EXAMPLE.......77
FIG._____ 3.7.3.1.5-13 TABLE "ACTIONS" SYNTAX ENTRIES ORDERING BY
FLIGHT TYPE AND GROUP IDENTIFIER..................................................................79
FIG._____ 3.7.3.1.6-14 "DEP_SEPARATOR_TEMPLATE" ENTRYTEMPLATE
205678826.doc
UNCLASSIFIED
Page 358
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003

"DEP_SEPARATOR_TEMPLATE" PROPERTIES EDITOR....................................81
FIG._____ 3.7.3.1.6-16 "ARR_SEPARATOR_TEMPLATE" ENTRYTEMPLATE
"ARR_SEPARATOR_TEMPLATE" PROPERTIES EDITOR...................................82
FIG._____ 3.7.3.1.6-18 "ENR_SEPARATOR_TEMPLATE" ENTRYTEMPLATE
"ENR_SEPARATOR_TEMPLATE" PROPERTIES EDITOR...................................82
FIG._____ 3.7.3.1.6-23 TABLE "ACTIONS" SYNTAX FOR ADDING GROUP
HEADER ENTRIES...........................................................................................................84
FIG._____ 3.7.3.1.7-27 TABLE "ACTIONS" SYNTAX TO ALLOW MULTIPLE
ORDERING.........................................................................................................................88
FIG._____ 3.7.3.1.8-28 TABLE "ACTIONS" SYNTAX FOR FLIGHT STATUS
DEPENDING LAYOUTS (1ST)........................................................................................90
205678826.doc
UNCLASSIFIED
Page 359
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
FIG._____ 3.7.3.1.8-29 TABLE "ACTIONS" SYNTAX FOR FLIGHT STATUS

DEPENDING LAYOUTS (2ND).......................................................................................91
"ESB_DEP_ACT_TEMPLATE" PROPERTIES EDITOR..........................................93
"ESB_ARR_ACT_TEMPLATE" PROPERTIES EDITOR..........................................94
"ESB_ENR_ACT_TEMPLATE" PROPERTIES EDITOR..........................................95
DEP_SEPARATOR_TEMPLATE" PROPERTIES EDITOR......................................95
FIG.__ 3.8-22 TABLE STRUCTURE VARIABLES REPRESENTATION.................97
FIG.__ 3.9-23 ADDING DEFINES USING LIST CONFIGURATION EDITOR ....100
FIG.__ 3.9-24 LIST EDITOR SHELL............................................................................101
FIG.__ 4.1-25 IES TABULAR MAIN MENU BAR......................................................103
FIG.___ 4.1.1-14 IES TABULAR "FILE" MENU BUTTON......................................104
FIG.____ 4.1.1.1-13 IES TABULAR "LOAD" BUTTON............................................104
FIG.____ 4.1.1.1-14 IES WARNING BOX.....................................................................104
FIG.____ 4.1.1.1-15 IES TABULAR COMPONENT SELECTION...........................106
FIG.____ 4.1.1.1-16 TABLE (NSA) LAYOUT IN THE PREVIEW AREA................106
205678826.doc
UNCLASSIFIED
Page 360
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
FIG.____ 4.1.1.2-17 IES TABULAR "NEW" BUTTON..............................................107

FIG.____ 4.1.1.2-18 IES WARNING BOX.....................................................................107
FIG.____ 4.1.1.2-19 IES TABULAR NEW TABLE SHELL NAME...........................107
FIG.____ 4.1.1.2-20 GFR LAYOUT................................................................................108
FIG.____ 4.1.1.2-21 IES TABULAR "GRF" TABLE TREE.......................................108
FIG.____ 4.1.1.3-22 IES TABULAR "SAVE" BUTTON.............................................109
FIG.____ 4.1.1.3-23 ERROR DIALOG" FOR SAVE IN TEMPLATE MODE.......109
FIG.____ 4.1.1.4-24 "SAVE AS" BUTTON...................................................................110
FIG.____ 4.1.1.4-25 FILESELECTIONBOX.................................................................110
FIG.____ 4.1.1.5-26 IES TABULAR "EXIT" BUTTON..............................................111
FIG.____ 4.1.1.5-27 EXIT MASK...................................................................................111
FIG.__ 4.1-26 IES TABULAR "EDIT" MENU BUTTON...........................................112
FIG._____ 4.1.2.1.1-37 "LOCAL PRIMITIVE" BUTTON..........................................112
FIG._____ 4.1.2.1.1-38 PRIMITIVE SELECTION BOX.............................................113
FIG._____ 4.1.2.1.1-39 "SYMBOL_FCF_ON" PRIMITIVE PROPERTIES EDITOR
.............................................................................................................................................113
FIG._____ 4.1.2.1.1-40 "ATTRIBUTE SELECTION" FOR LOCAL PRIMITIVE
PROPERTIES EDITOR..................................................................................................114
FIG._____ 4.1.2.1.1-41 "RECTANGLE PRIMITIVE" PROPERTIES EDITOR.....115
FIG._____ 4.1.2.1.1-42 "TEXT EDITOR FOR LOCAL PRIMITIVE PROPERTIES
EDITOR.............................................................................................................................116
FIG._____ 4.1.2.1.1-43 "POLYLINE PRIMITIVE" PROPERTIES EDITOR..........116
205678826.doc
UNCLASSIFIED
Page 361
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
FIG._____ 4.1.2.1.1-44 "ADD/REMOVE MENU" FOR LOCAL PRIMITIVE

FIG._____ 4.1.2.1.1-45 "LIST OF PRIMITIVE" PROPERTIES EDITOR...............117
FIG._____ 4.1.2.1.1-46 "ERROR DIALOG" FOR LOCAL PRIMITIVE
FIG._____ 4.1.2.1.1-47 "ERROR DIALOG" FOR LOCAL PRIMITIVE
FIG._____ 4.1.2.1.2-48 "GLOBAL PRIMITIVE" BUTTON.......................................119
FIG._____ 4.1.2.1.3-49 "PARAMETRIC PRIMITIVE" BUTTON............................120
FIG._____ 4.1.2.1.4-50 "PARAMETRIC MULTI_PRIMITIVE" BUTTON.............120
FIG._____ 4.1.2.1.5-51 "ALL PRIMITIVE" BUTTON................................................121
FIG._____ 4.1.2.2.1-52 "LOCAL ATTRIBUTE" BUTTON........................................122
FIG._____ 4.1.2.2.1-53 SELECTION ITEM IN ATTRIBUTE BOX...........................122
FIG._____ 4.1.2.2.1-54 ATTRIBUTE (BG_EMERGENCY) PROPERTIES EDITOR
.............................................................................................................................................123
FIG._____ 4.1.2.2.2-55 "GLOBAL ATTRIBUTE" BUTTON.....................................123
FIG._____ 4.1.2.2.3-56 "PARAMETRIC ATTRIBUTE" BUTTON...........................124
FIG._____ 4.1.2.2.4-57 "ALL ATTRIBUTE" BUTTON..............................................125
FIG.____ 4.1.2.3-28 SELECTION ITEM IN TEMPLATE BOX.................................125
FIG.____ 4.1.2.3-29 TEMPLATE (ESB_ARR_ACT_TEMPLATE) PROPERTIES
EDITOR.............................................................................................................................126
FIG.____ 4.1.2.4-30 INCLUDE SECTION EDITOR SHELL......................................126
FIG.____ 4.1.2.4-31 "SAVE" BUTTON IN THE EDITOR SHELL...........................127
FIG.____ 4.1.2.5-32 GENERAL VARIABLES EDITOR SHELL...............................127
205678826.doc
UNCLASSIFIED
Page 362
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003

FIG.__ 4.1-27 IES TABULAR "OPTIONS" MENU BUTTON...................................129
FIG.____ 4.1.3.1-34 "VIEW NAME FIELDS" BUTTON............................................129
FIG.____ 4.1.3.1-35 IES TABULAR CHANGED BUTTON LAYOUT......................129
FIG.____ 4.1.3.1-36 TREE LAYOUT WITH FIELDS NAME ONLY........................130
FIG.__ 4.1-28 IES TABULAR "CREATE" MENU BUTTON....................................131
FIG.____ 4.1.4.1-37 "NEW PRIMITIVE" CASCADE BUTTON...............................131
FIG._____ 4.1.4.1.1-58 "RECTANGLE" BUTTON......................................................131
FIG._____ 4.1.4.1.1-59 NEW PRIMITIVE NAME SHELL.........................................131
FIG._____ 4.1.4.1.1-60 PROPERTIES EDITOR OF THE NEW PRIMITIVE
"RECT_PRIM_1"............................................................................................................132
FIG._____ 4.1.4.1.2-61 "POLYLINE" BUTTON..........................................................132
FIG._____ 4.1.4.1.3-62 "LIST OF PRIMITIVE" BUTTON........................................132
FIG.____ 4.1.4.2-38 "NEW ATTRIBUTE" CASCADE BUTTON.............................133
FIG._____ 4.1.4.2.1-63 "TEXT ATTRIBUTE" BUTTON...........................................133
FIG._____ 4.1.4.2.1-64 NEW TEXT ATTRIBUTE NAME SHELL............................133
FIG._____ 4.1.4.2.1-65 PROPERTIES EDITOR OF NEW TEXT ATTRIBUTE
(NEW_TEXT_ATTR_1)..................................................................................................134
FIG._____ 4.1.4.2.2-66 "SYMBOL ATTRIBUTE" BUTTON.....................................134
FIG.____ 4.1.4.3-39 "NEW TEMPLATE" CASCADE BUTTON...............................135
FIG._____ 4.1.4.3.1-67 "TABLETEMPLATE" BUTTON...........................................135
FIG._____ 4.1.4.3.1-68 NEW TABLETEMPLATE NAME SHELL...........................135
205678826.doc
UNCLASSIFIED
Page 363
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
FIG._____ 4.1.4.3.1-69 PROPERTIES EDITOR OF NEW TABLETEMPLATE

"NEW_T_TEMPLATE_1"..............................................................................................136
FIG._____ 4.1.4.3.2-70 "ENTRYTEMPLATE" BUTTON..........................................137
FIG._____ 4.1.4.3.3-71 "ENTRYSTATE" BUTTON....................................................137
FIG.__ 4.1-29 IES TABULAR "SEL_TABLE" MENU BUTTON..............................138
FIG.____ 4.1.5.1-40 SELECTION ITEM IN SINGLE TABLE BOX.........................138
FIG.__ 4.1-30 IES TABULAR "BROWSER" BUTTON.............................................139
FIG.____ 4.1.6.1-41 TEXT EDITOR SHELL EMPTY.................................................139
FIG.____ 4.1.6.1-42 "LOAD" BUTTON IN THE TEXT EDITOR SHELL..............139
FIG.____ 4.1.6.1-43 SELECTING A FILE ON THE FILE SELECTION BOX........140
FIG.____ 4.1.6.1-44 SEARCH SHELL...........................................................................140
FIG.____ 4.1.6.1-45 "TEXT EDITOR" WINDOW WITH "FLDI" TABLE
SYNTACTICAL DEFINITION......................................................................................141
FIG.____ 4.1.6.1-46 SAVE SHELL.................................................................................142
FIG.____ 4.1.6.2-47 LOG WINDOW TEXT EDITOR.............................................143
FIG.____ 4.1.6.3-48 LIST EDITOR SHELL..................................................................144
FIG.____ 4.1.6.3-50 FILE SELECTION BOX FOR "LISTS.DSP" SHELL..............145
FIG.____ 4.1.6.4-51 LIST CONFIGURATION EDITOR SHELL..............................146
FIG.__ 4.1-31 "REMOVE" BUTTON............................................................................148
FIG.____ 4.1.7.1-53 SELECTION ITEM IN REMOVE TEMPLATE BOX..............148
205678826.doc
UNCLASSIFIED
Page 364
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
FIG.____ 4.1.7.1-54 IES WARNING BOX FOR REMOVE TEMPLATE.............149

FIG.___ 4.1.8-15 "PAPER STRIP" MENU...................................................................149
FIG.__ 4.2-32 IES TABULAR POP-UP MENU FOR "FLDI" TABLE.....................150
FIG.___ 4.2.1-16 IES TABULAR "DEFAULT_GRID (GRID)" PROPERTIES
EDITOR.............................................................................................................................151
FIG.___ 4.2.2-17 IES TABULAR "ERROR DIALOG" FOR EXISTENT LIST NODE
.............................................................................................................................................151
FIG.___ 4.2.3-18 IES TABULAR NEW GRID TEST_GRID AND THE
CORRESPONDENT PROPERTIES EDITOR ............................................................152
FIG.___ 4.2.4-19 IES TABULAR NEW FIELD TEXT TEST_TEXT WITH
CORRESPONDENT PROPERTIES EDITOR.............................................................154
FIG.___ 4.2.4-20 FIELD TEXT TEST_TEXT WITH CORRESPONDENT
PROPERTIES EDITOR IN A NEW POSITION..........................................................155
FIG.___ 4.2.7-21 "IES TABULAR NEW INSERT" SHELL.......................................156
FIG.___ 4.2.7-22 NEW DUPLICATED FIELD TEXT
TEST_TABLE_DUPLICATE_FIELD_000...............................................................157
FIG.___ 4.2.10-23 IES WARNING BOX .......................................................................158
FIG.___ 4.2.11-24 NOTHING TO REPOSITION ERROR DIALOG ...................158
FIG.___ 4.2.11-25 WRONG REPOSITION ERROR DIALOG .................................159
FIG.__ 4.3-33 IES TABULAR RADIO BUTTONS.......................................................160
FIG.___ 4.3.2-26 IES TABULAR "TEMPLATE SELECTION" WINDOW.............161
FIG.___ 4.3.3-27 LOG WINDOW FOR CHECK GEOMETRY IN A CORRECT
SITUATION......................................................................................................................161
FIG.___ 4.3.3-28 A SECTION OF THE FLDI TABLE WITH COMPONENTS
OVERLAP ON THE BLACKBOARD...........................................................................162
205678826.doc
UNCLASSIFIED
Page 365
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
FIG.___ 4.3.3-29 LOG WINDOW FOR CHECK GEOMETRY IN A WRONG

SITUATION......................................................................................................................162
FIG.__ 5.1-34 DISABLED "PAPER STRIP" MENU ..................................................163
FIG.__ 5.1-35 ENABLED "PAPER STRIP" MENU AFTER THE SWITCH...........164
FIG.__ 5.1-36 THE NSA TABLE REPRESENTATION IN ELECTRONIC TABLES
CUSTOMIZATION STATE ...........................................................................................164
FIG.__ 5.1-37 THE NSA TABLE REPRESENTATION IN PAPER STRIP
CUSTOMIZATION STATE ...........................................................................................164
FIG.___ 5.1.1-30 THE ESB_CS ENTRY-FIELD PROPERTIES EDITOR IN
PAPER STRIP CUSTOMIZATION STATE.................................................................165
FIG.___ 5.1.1-31 THE ENTRY-FIELD PPST_FONT RESOURCE CHOICE......168
FIG.___ 5.1.1-32 A SECTION OF THE BLACKBOARD WITH ESB_CS FIELD
WITH DEFAULT RESOURCES VALUES...................................................................168
WITH 2X3SP VALUE FOR THE PPST_FONT RESOURCE................................169
FIG.___ 5.1.1-34 A SECTION OF THE ESB_CS FIELD PROPERTIES EDITOR
WITH MODIFIED RESOURCESVALUES..................................................................169
WITH 3X4SP VALUE FOR PPST_FONT, 3 FOR PPST_TRUNCATION AND ON
FOR PPST_REVERSE.....................................................................................................169
FIG.___ 5.1.2-36 STRIP_PRINTER_GRID PROPERTIES EDITOR...................170
FIG.___ 5.1.2-37 THE NSA TABLE WITH DEFAULT STRIP_PRINTER_GRID
PROPERTIES (CHAR_WIDTH, CHAR_HEIGHT)...................................................171
FIG.___ 5.1.2-38 THE NSA TABLE WITH ENLARGED
STRIP_PRINTER_GRID PROPERTIES (CHAR_WIDTH, CHAR_HEIGHT). .171
FIG.___ 5.2.1-39 PROPERTIES EDITOR FOR "PPST_TEMPLATE01"................172
FIG.___ 5.2.2-40 IES TABULAR RADIO BUTTONS..................................................173
205678826.doc
UNCLASSIFIED
Page 366
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
FIG.___ 5.2.2-41 SELECTION ITEM IN TEMPLATE SELECTION BOX.............174

FIG.___ 5.2.2-42 TRYING TO EDIT A TEMPLATE DURING A TEMPLATE
EDITING SESSION.........................................................................................................174
FIG.___ 5.2.2-43 PROPERTIES EDITOR OF AN ENTRY FIELD IN TEMPLATE
MODE................................................................................................................................175
FIG.___ 5.2.2-44 WARNING FOR TEMPLATE WITHOUT FIELDS SET.............176
FIG.____ 5.2.3.1-55 ENTER NEW NAME BOX.......................................................177
FIG.____ 5.2.3.2-56 SELECTING AN ITEM IN THE SELECTION BOX
TEMPLATE .....................................................................................................................177
FIG.____ 5.2.3.3-57 SELECTING AN ITEM IN THE REMOVE TEMPLATE
SELECTION BOX............................................................................................................178
FIG.____ 5.2.3.3-58 IES WARNING BOX FOR REMOVE TEMPLATE.............179
FIG.____ 5.2.3.4-59 SELECTING AN ITEM IN THE TEMPLATE TO CLONE
SELECTION BOX............................................................................................................179
FIG.____ 5.2.3.4-60 CLONE NAME FOR PPST_TEMPLATE BOX....................180
FIG.____ 5.2.3.5-61 SELECTING AN ITEM IN THE TEMPLATE TO EXPORT
SELECTION BOX............................................................................................................180
FIG.____ 5.2.3.6-62 FLIGHT STATES TEMPLATES MATRIX PROPERTIES
EDITOR LAYOUT...........................................................................................................181
FIG.____ 5.2.3.6-63 TEMPLATES SELECTION BOX FROM THE FLIGHT
STATES TEMPLATES MATRIX PROPERTIES EDITOR..................................182
FIG.____ 5.2.3.6-64 FLIGHT STATES TEMPLATES MATRIX PROPERTIES
EDITOR WITH SOME TEMPLATES SELECTED....................................................183
FIG.____ 5.3.1.1-65 INSERT PSEUDO NAME BOX...................................................184
FIG.____ 5.3.1.1-66 PSEUDO_01 PSEUDO GRAPHIC PROPERTIES EDITOR
.............................................................................................................................................184
205678826.doc
UNCLASSIFIED
Page 367
UNCLASSIFIED
E000IES0-09SUM
Issue
Date:
D
28/02/2003
FIG.____ 5.3.1.1-67 THE METACHARACTER USED FOR PSEUDO GRAPHIC

PRIMITIVE EDITING....................................................................................................185
FIG.____ 5.3.1.1-68 A SECTION OF THE BLACKBOARD DURING PSEUDO
GRAPHIC PRIMITIVE EDITING PHASE..................................................................185
FIG.____ 5.3.1.1-69 A SELECTED METACHARACTER DURING THE PSEUDO
GRAPHIC PRIMITIVE EDITING PHASE..................................................................186
FIG.____ 5.3.1.1-70 A SECTION OF THE BLACKBOARD DURING
METACHARACTER DRAWING..................................................................................186
FIG.____ 5.3.1.1-71 A SECTION OF THE BLACKBOARD AFTER
METACHARACTER DRAWING..................................................................................186
FIG.____ 5.3.1.1-72 THE METATEXT EDITOR OF THE META TEXT PSEUDO
RESOURCE......................................................................................................................187
FIG._____ 5.3.1.1.1-72 THE PAPER STRIP TEMPLATE PROPERTIES EDITOR
WITH A REFERENCED PSEUDO GRAPHIC............................................................187
FIG._____ 5.3.1.1.1-73 THE PSEUDO GRAPHIC PRIMITIVE SELECTION BOX
.............................................................................................................................................188
FIG.____ 5.3.1.2-73 THE PSEUDO PRIMITIVE SELECTION BOX........................189
FIG.___ 5.4.1-45 TEMPLATE SELECTION BOX.......................................................191
FIG.___ 5.4.1-46 IES WARNING BOX FOR FDMPERS.BIN FILE CREATION
.............................................................................................................................................192
.............................................................................................................................................192
.............................................................................................................................................193
205678826.doc
UNCLASSIFIED
Page 368

E000ies0-09sum D

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

E000ies0-09sum D

Transféré par

Droits d'auteur :

Formats disponibles

Alenia Marconi Systems

SOFTWARE USER MANUAL

The copyright in this document is the property of Alenia

Alenia Marconi Systems

DOCUMENT SECURITY CLASSIFICATION:

Alenia Marconi Systems

This document contains a total of 259 pages1

Alenia Marconi Systems

AMENDMENT RECORD SHEET

Alenia Marconi Systems

REVISIONS RECORD SHEET

Document Change Note

Added paragraphs for New Menus

Paper Strip management added

List Upgrade Sytnax changes

Alenia Marconi Systems

Alenia Marconi Systems

Alenia Marconi Systems

4.1.7.1 MENU "REMOVE", ITEM "TEMPLATE".................................................................148

5 PAPER STRIP CUSTOMIZATION............................................................................163

Alenia Marconi Systems

6.4.1.1 Flight reference help..........................................................................................................207

Alenia Marconi Systems

INTERFACE EDITOR SYSTEM

Alenia Marconi Systems

Alenia Marconi Systems

Fig._ 1-1 Tabular Parsing And Compiling Phases

In the previous figure, the following information can be observed:

Alenia Marconi Systems

Alenia Marconi Systems

Alenia Marconi Systems

[PR-1] PPA-D-01 rev. A AMS - Processo Software 2 giugno 1999.

Alenia Marconi Systems

EDITING TABULAR COMPONENTS

TABULAR GRAPHIC OBJECTS DESCRIPTION

Fig.__ 3.1-1 FLDI Tabular Component Graphical Appearance Example

Alenia Marconi Systems

LOADING AN EXISTENT TABULAR COMPONENT

Alenia Marconi Systems

Fig.__ 3.2-3 Tabular Component ("ARR") Structural Tree

Alenia Marconi Systems

Fig.__ 3.2-4 Tabular Component ("ARR") Preview

Fig.__ 3.2-5 Tabular Component ("ARR") Preview With Layout Frame

In the next paragraphs are described the different objects represented.

Alenia Marconi Systems

Identifing Name And Location Of Objects

Fig.___ 3.2.1-1 Picking A TextField On The BlackBoard

Alenia Marconi Systems

Fig.___ 3.2.1-2 Picking A PrimitiveP_CSL_ENTRY_BOTTOM_SYMBOL, Referred By A

Alenia Marconi Systems

TABLE AND TABLE LIST RESOURCES

Fig.__ 3.3-6 Opening The Properties Editor For Table Node

Alenia Marconi Systems

Fig.__ 3.3-7 Table Node Properties Editor (1st half)

Alenia Marconi Systems

Fig.__ 3.3-8 Table Node Properties Editor (2nd half)

table name: cannot be edited, but may be

Alenia Marconi Systems

realised as presentation object.

Alenia Marconi Systems

container min height:

{numeric non-negative integer expression }

short name to be displayed on the container