SIST EN 28651-1:1997
(Main)Information processing systems - Computer graphics - Graphical Kernel System (GKS) language bindings - Part 1: FORTRAN (ISO 8651-1:1988)
Information processing systems - Computer graphics - Graphical Kernel System (GKS) language bindings - Part 1: FORTRAN (ISO 8651-1:1988)
Graphische Systeme der Informationsverarbeitung - Sprachbindungen für das Graphische Kernsystem (GKS) - Teil 1: FORTRAN (ISO 8651-1:1988)
Systemes de traitement de l'information - Infographie - Interfaces langage avec GKS - Partie 1: FORTRAN (ISO 8651-1:1988)
Information processing systems - Computer graphics - Graphical Kernel System (GKS) language bindings - Part 1: FORTRAN (ISO 8651-1:1988)
General Information
Standards Content (Sample)
SLOVENSKI STANDARD
SIST EN 28651-1:1997
01-december-1997
Information processing systems - Computer graphics - Graphical Kernel System
(GKS) language bindings - Part 1: FORTRAN (ISO 8651-1:1988)
Information processing systems - Computer graphics - Graphical Kernel System (GKS)
language bindings - Part 1: FORTRAN (ISO 8651-1:1988)
Graphische Systeme der Informationsverarbeitung - Sprachbindungen für das
Graphische Kernsystem (GKS) - Teil 1: FORTRAN (ISO 8651-1:1988)
Systemes de traitement de l'information - Infographie - Interfaces langage avec GKS -
Partie 1: FORTRAN (ISO 8651-1:1988)
Ta slovenski standard je istoveten z: EN 28651-1:1992
ICS:
35.060 Jeziki, ki se uporabljajo v Languages used in
informacijski tehniki in information technology
tehnologiji
35.140 5DþXQDOQLãNDJUDILND Computer graphics
SIST EN 28651-1:1997 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
SIST EN 28651-1:1997
---------------------- Page: 2 ----------------------
SIST EN 28651-1:1997
---------------------- Page: 3 ----------------------
SIST EN 28651-1:1997
---------------------- Page: 4 ----------------------
SIST EN 28651-1:1997
ISO
INTERNATIONAL STANDARD
86514
First edition
1988-04-15
INTERNATIONAL ORGANIZATION FOR STANDARDIZATION
ORGANISATION INTERNATIONALE DE NORMALISATION
MEXfiYHAPOAHAf! OPrAHM3A~Wl l-l0 CTAH~APTM3A~MM
Information processing Systems -
Computer graphics - Graphical Kerne1
System (GKS) language bindings -
Part 1 :
FORTRAN
S ystkmes de traitemen t de l’informa tion - In fographie - Systeme graphique de base (GKS)
- Interface langage -
Partie 7 : FORTRAN
Reference number
ISO 8651-1 : 1988 (E)
---------------------- Page: 5 ----------------------
SIST EN 28651-1:1997
ISO 86514 : 1988 (E)
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of
national Standards bodies (ISO member bodies). The work of preparing International
Standards is normally carried out through ISO technical committees. Esch member
body interested in a subject for which a technical committee has been established has
the right to be represented on that committee. International organizations, govern-
mental and non-governmental, in liaison with ISO, also take patt in the work. ISO
collaborates closely with the International Electrotechnical Commission (IEC) on all
matters of electrotechnical standardization.
Draft International Standards adopted by the technical committees are circulated to
the member bodies for approval before their acceptance as International Standards by
the ISO Council. They are approved in accordance with ISO procedures requiring at
least 75 % approval by the member bodies voting.
International Standard ISO 8651-1 was prepared by Technical Committee ISO/TC 97,
Information processing Systems.
Users should note that all International Standards undergo revision from time to time
and that any reference made herein to any other International Standard implies its
latest edition, unless otherwise stated.
International Organkation for Standardkation, 1988
Printed in Switzerland
ii
---------------------- Page: 6 ----------------------
SIST EN 28651-1:1997
ISO 86514 : 1988 (E)
Contents
Page
.................................................................................................................................... 1
Introduction
2
Scope and field of application .
....................................................................................................................................... 3
References
The FORTRAN language binding of GKS . 4
4
3.1 Speciflcation .
...................................... 4
3.2 Mapping of GKS function names to FORTRAN subroutine names
Parameters . 4
3.3
......................................................................................................... 4
3.4 The FORTRAN subset
Error handling . s
3.6
....................................................................................... 0
Generating FORTRAN subroutine names
8
......................................................................................................................................
Data types
........................................................................................................................ 12
Enumeration types
Lists of the GKS function names . 16
......................................................................... 16
7.1 List ordered alphabetically by beund name
List ordered alphabetically by GKS function name . 19
7.2
..................................................... 24
7.3 List ordered alphabetically by bound name within level
................................................................... 28
8 GKS errors specific to the FORTRAN binding
.......................................................................................................... 29
The GKS function interface
29
9.1 General principles .
................................................................................................................ 29
9.2 Control functions
Output functions . 32
9.3
34
9.4 Output attributes .
9.4.1 Workstation independent primitive attributes . 34
................................................................... 38
9.4.2 Workstation attributes (representations)
40
Transformation functions .
9.6
................................................................................... 40
9.6.1 Normalication transformation
41
9.6.2 Workstation transformation .
............................................................................................................... 42
9.0 Segment functions
42
9.6.1 Segment manipulation functions .
43
9.6.9 Segment attributes .
.................................................................................................................... 44
9.7 Input functions
44
9.7.1 Initialisation of input devices .
................................................................................... 47
9.7.2 Setting mode of input devices
9.7.3 Request input functions . 49
............................................................................................. 51
9.7.4 Sample input functions
............................................................................................... 53
97.6 Event input functions
................................................................................................................ SS
9.8 Metafile functions
9.9 Inquiry functions . 56
................................................................ 56
9.9.1 Inquiry function for operating state value
9.9.2 Inquiry functions for GKS description table . 57
58
9.9.3 Inquiry functions for GKS state list .
............................................................... 66
9.9.4 Inquiry functions for workstation state list
9.9.5 Inquiry functions for workstation descriptioa table . 76
.................................................................... 88
9.9.6 Inquiry functions for Segment state list
........................................................................................................... 88
9.9.7 Pixel inquiries
89
9.9.8 Inquiry function for GKS error state list .
90
9.10 Utility functions .
90
....................................................................................................................
9.11 Error handling
................................................................................... 91
9.12 Utility functions not defined in GKS
Annexes
94
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .~***~*.~~.~.~.~~~~.~.~.*.~.
A FORTRAN examples
11s
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .*.
B Metafile Item Types
. . .
Ill
---------------------- Page: 7 ----------------------
SIST EN 28651-1:1997
This page intentionally left blank
---------------------- Page: 8 ----------------------
SIST EN 28651-1:1997
ISO 8651-1: 1988 (E)
INTERNATIONAL STANDARD
Information processing Systems -
Computer graphics - Graphical Kerne1
System (GKS) language bindings -
Part 1 :
FORTRAN
0 Introduction
The Graphical Kerne1 System (GKS), the functional description of which is given in ISO 7942, is
specified in a language independent manner and needs to be embedded in language dependent
layers (language bindings) for use with particular programming languages. The purpose of this
part of ISO 8651 is to define a Standard binding for the FORTRAN Computer programming
language.
---------------------- Page: 9 ----------------------
SIST EN 28651-1:1997
ISO 86514: 1988 (E)
1 Scope and field of application
s eci es a language independent nucleus of a graphics System. For integration
ISO 7942 (GKS) p fi
into a programming language, GKS is embedded in a language dependent layer obeying the par-
ticular conventions of that language. This part of ISO 8651 specifies such a language dependent
layer for the FORTRAN language.
---------------------- Page: 10 ----------------------
SIST EN 28651-1:1997
ISO 8651-1: 1988 (E)
2 References
ISO 7942, Information Proceasing - Computer graphica - Graphical Kerne1 Syatem (GKS) func-
tional deacription.
ISO 1539, Programming Languagea - FORTRAN.
---------------------- Page: 11 ----------------------
SIST EN 28651-1:1997
ISO 86514 : 1988 (E)
3 The FORTRAN language binding of GKS
3.1 Specification
The GKS language binding interface for ISO FORTRAN 77 (ISO 1539) shall be described as in
clauses 3, 4, 5, 6, 7, 8, and 9.
3.2 Mapping of GKS function names to FORTRAN subroutine names
The function names of GKS are all mapped to FORTRAN subroutine names which Start with the
letter G. The mapping is generally done in a one-to-one correspondence to ISO 7942. However,
some inquiry functions are Split into more than one subroutine in this binding, due to the number
of Parameters required. The remaining letters after the first one are obtained by deriving a unique
ACTIVATE becomes AC, WORKSTATION
acronym from the words of the function name; e.g.,
becomes WK. Hence, the FORTRAN subroutine name of GKS function ACTIVATE WORKS-
TATION is GACWK. For a list of all abbreviations, see clause 4. Names used internally which
may be known outside GKS, e.g., during linking, Start with some easily recogniced and docu-
mented form such as GK (subroutine, function, and common block names). Therefore, no exter-
na1 names starting with this construct should be Chosen when using GKS, in Order to avoid name
conflicts. Globally used GKS names may be renamed if necessary.
3.3 Parameters
In general, the Order of GKS function Parameters is preserved. For some subroutines, however,
there are additional Parameters which have been inserted in the normal Parameter sequence (e.g.,
array length for arrays which are output Parameters).
Values of input Parameters are unaltered by any GKS function, by PACK DATA RECORD, or
by UNPACK DATA RECORD.
In Order that the application program may inquire any element of a list (member of a Set), such
as the set of Segment names, in this binding the inquiry functions return only a Single element of
a list (member of a Set). In addition, the total number of elements of the list (members of the
set) is always returned. The elements (members) are numbered starting from 1; each invocation
of the inquiry function requires the desired element (member) number as an input Parameter and
returns the corresponding element (member). When the list (Set) is empty, a eero is returned as
the number of elements (members) and the Parameter representing the Single element in the list is
undefined.
3.4 The FORTRAN subset
The binding for FORTRAN 77 Subset is different from that for full FORTRAN 77 in Order to
accommodate the FORTRAN 77 Subset restrictions.
Those GKS subroutines in the full FORTRAN 77 binding that have arguments of type CHAR-
ACTER*( *) have alternative subroutine definitions that include fixed length Character strings,
CHARACTER*80, for the Subset.
In some cases, an additional INTEGER Parameter (the number of characters) appears in the
Parameter list and the Subset version is distinguished by the addition of a final S, so that the two
Versions tan coexist in the same implementation. In other cases the INTEGER Parameter is
4
---------------------- Page: 12 ----------------------
SIST EN 28651-1:1997
ISO 8651-1: 1988 (E)
already present and the FORTRAN 77 Subset version has the same name as the full FORTRAN
77 veraion.
A full FORTRAN 77 implementation shall include both subroutines in the case when the names
are distinct and only the full FORTRAN 77 Version when the names are the Same.
The enumeration values in this binding may be redefined for the Subset by replacing the
PARAMETER Statements with corresponding DATA Statements.
3.5 Error handling
There are two error routines in every GKS System, named GERLOG and GERHND. The User
may replace the latter with his own subroutine using the same name, GERHND, and calling
Furthermore, this user-defined error routine may cal1 the system-defined error logging
sequence.
procedure GERLOG.
5
---------------------- Page: 13 ----------------------
SIST EN 28651-1:1997
ISO 8651-1: 1988 (E)
4 Generafing FORTRAN subroutine names
For the binding of the GKS functions which inquire lists (Sets), the word element (member) is
added to the GKS function name before the subroutine name is generated from the resulting
terms.
The derivation of the abbreviation for the subroutine names is performed in several Steps. First,
Plurals are reduced to their Singular form, and grammatical derivations are unified. Next, some
compound terms are reduced. Finally, each remaining word is replaced by the null string or by
an abbreviation.
Plurals
ATTRIBUTES + ATTRIBUTE NUMBERS -+ NUMBER
DEVICES + DEVICE PRIMITIVES -+ PRIMITIVE
EVENTS -, EVENT PRIORITIES -+ PRIORITY
FACILITIES -+ FACILITY SEGMENTS + SEGMENT
FLAGS -, FLAG TYPES -, TYPE
INDICES + INDEX VALUES -* VALUE
NAMES -+ NAME WORKSTATIONS + WORKSTATION
Keeping Uniqueness
ACTIVE + ACTIVATE
-, DRAW
DRAWING
IDENTIFIER +
IDENTIFICATION
SPACING + SPACE
Reduce Compound Terms:
STATE TABLES -+ TABLES
TRANSFORMATION N-UMBER -+ TRANSFORMATION N
SET member -t member
CURRENT NORMALISATION -+ CN
MAXIMUM LENGTH -* LENGTH
Deletions
ALL FACTOR LIST OF TABLES
AND member ON
FROM TO
AVAILABLE GKSM MODIFICATION POINT TYPE
SIZE
CURRENT IN MORE VALUE
DATA INDICATOR STATES
NAME VECTOR
DEVICE LENGTH SUPPORTED
NUMBER WITH
EVENT
---------------------- Page: 14 ----------------------
SIST EN 28651-1:1997
ISO 86514 : 1988 (E)
Abbreviations
ACCUMULATE - AC LINETYPE + LN
ACTIVATE -, AC LINEWIDTH + LW
ALIGNMENT - AL LOCATOR -, LC
LOGGING + LOG
AREA -, A
-+ A LOGICAL + L
ARRAY
ASPECT -+ A MARKER + MK
ASSOCIATE + A MATRIX + M
ASSOCIATED -+ AS MAXIMUM + M
ATTRIBUTE -, A MESSAGE -, MSG
AWAIT + WAIT MODE + M
4 B NORMALIZATION
BASE + N
CATEGORY + CA OPEN -+ OP
CELL -* c OPERATING + OP
OVERFLOW 4 ov
CHARACTER -+ CH
CHOICE + CH PACK + P
CLASSIFICATION -+ CL PATH -, P
CLEAR + CLR PATTERN -+ PA
CLIPPING 3 CLIP PICK + PK
CLOSE -+ CL PIXEL -, PX
COLOUR -b c POLYLINE 3 PL
4 c + PM
CONNECTION POLYMARKER
COPY + c PRECISION + P
CREATE -, CR PREDEFINED -a P
DEACTIVATE -+ DA PRIMITIVE -, P
DEFAULT -+ D PRIORITY -, P
DEFERRAL -, D QUEUE
+ Q
DELETE -, D READ -, RD
+ REC
DETECTABILITY + DTEC RECORD
DIMENSIONS -. D REDRAW -. R
+ D REFERENCE -, RF
DISPLAY
DRAW -. D RENAME + REN
DYNAMIC - D REPRESENTATION + R
element -, E REQUEST
+ RQ
-+
EMERGENCY -, E SAMPLE SM
ERROR + ER SCALE -, sc
ESCAPE + ESC SEGMENT -. SG
EVALUATE -, EV SELECT -, SEL
EXPANSION -+ XP SET -, s
EXTENT -, x SIMULTANEOUS -+ SIM
FACILITY + F SOURCE -, s
FILL + F SPACE + SP
FLAG 4 F STATE - s
FONT -+ F + ST
STRING
GENERALISED -, G STROKE -, SK
+ s
GET + GT STYLE
GKS + KS SURFACE * s
HANDLING + HND TEXT
+ TX
HEIGHT + H TRANSFORMATION -+ T
-, u
HIGHLIGHTING -, HLIT UNPACK
IDENTIFICATION + ID UPDATE + u
INDEX -+ 1 USE + us
INITIALISE 4 IN VALUATOR -, VL
INPUT + 1 VIEWPORT -+ VP
INQUIRE VISIBILITY ‘-, VIS
+ Q
-, w
INSERT + IN WIDTH
INTERIOR + 1 WINDOW -, WN
INTERPRET
+ 1 WORKSTATION + WK
ITEM -. ITM WRITE + w
LINE
+ LN
---------------------- Page: 15 ----------------------
SIST EN 28651-1:1997
ISO 8651-1: 1988 (E)
6 Data types
In ISO 7942, Parameters of several types are used. The following Shows the correspondence
between the types used in ISO 7942 and their realisation in a FORTRAN implementation.
GKS Data Type FORTRAN Data Types
1 integer INTEGER
R real REAL
S string
In a full FORTRAN 77 subroutine:
i)
a) INTEGER containing the number of characters returned (for out-
put string argument only)
b) CHARACTER*(*) containing the string. In addition, if a charac-
ter string which is an input Parameter may reasonably contain no
characters, then an INTEGER (20) is used to give the number of
characters to be passed to the subroutine.
In a FORTRAN 77 Subset subroutine:
2)
a) INTEGER containing the number of characters passed to the sub-
routine (for input string only, i.e. only one INTEGER needed for
output).
containing the number of characters returned (for out-
b) INTEGER
put string argument only).
c) CHARACTER*80 containing the string.
P Point REAL, REAL containing the X- and Y-values
N name INTEGER
Workstation Identifier, Segment Name, Pick Identifier: An implemen-
1)
tation may restritt the range but must at least provide all non-
negative integers which are available at that implementation.
NOTE - the default value for pick identifler is Zero.
Workstation Type, Connection Identifier, Error File: The set of valid
2)
values is implementation dependent. The Connection Identifier and
Error File may be logical unit numbers.
GDP Identifier, Escape Identifier: The set of legal values is described
3)
in ISO 7942.
Identification of GKS procedure: The range is shown under
4)
‘Enumeration Types’.
E enumeration INTEGER
NOTE - All values are mapped to the range Zero to N-l, where N is the number of
enumeration alternatives. Except for null values, the Order of the enumeration alter-
natives is the same as in ISO 7942: null values always appear in the flrst Position. If
the integer value given by the application program is not in the range 0 to N-l,
there is a language binding error condition (error 2000).
const x simple-type where simple-type is 1 or R (vector of values, for example 2xR)
1) In non-inquiry functions, separate simple-type Parameters are used.
NOTE - in GKS, const 54
In inquiry functions, if const “3, separate simple-type Parameters arc
2)
used; if const 24, a simpletype array of dimension const is used.
8
---------------------- Page: 16 ----------------------
SIST EN 28651-1:1997
ISO 8651-1: 1988 (E)
const x P (only occurs in non-inquiry functions)
Separate REAL Parameters, with the X- and Y- coordinates of one Point
being followed by the X- and Y- coordinates of the next.
const x E (only occurrence in GKS is const = 13)
An array of INTEGER e 1 ements of dimension const is used, each element
being an enumeration alternative.
const 1 x const 2 x R (matrix of values, for example 2x3xR)
REAL array (const 1, const 2)
list of n values of one simple-type (for example nx1)
1) For input Parameter:
a) INTEGER (input Parameter) containing length n of the list (unless
the length is already present as a separate GKS Parameter, in which
case it is not duplicated)
b) array of dimension n, whose elements are of the appropriate
simple-type.
When the length could legally be eero within GKS, the binding indi-
cates the array dimension by *. The implementation Checks that
the given length is 20.
2) For output Parameter in non-inquiry functions:
a) INTEGER (input Parameter) containing the dimension of the array
b) INTEGER (output Parameter) containing the number of elements of
the array actually used.
c) an array whose elements are of the appropriate simple-type. The
input dimension being too small is a language binding error condi-
tion (error 2001).
In both cases (input or output), where the simple-type is a Point,
there is a REAL array for the X-coordinates and another for the Y-
coordinates.
3) For inquiry functions, a Single cal1 returns a Single element of the list.
For a complete list of length n,
a) INTEGER (input Parameter) containing the sequence number of
required list element (in the range O.n).
b) INTEGER (output Parameter) containing the number of items in
the list n.
a Parameter of the appropriate simple-type containing the requested
4
element.
If the sequence number given is 0, the requested element returned is
undefined, but an error is not indicated thereby; the number of
items in the list n is returned. If the sequence number given is <0
or >n, then error 2002 is indicated, the number of items in the list
is returned, but the requested element is undefined; the exception to
this is when the list siee is 0, and in that case an error is not indi-
cated thereby.
4) A complete inquired list is returned from a Single cal1 when the max-
imum siae of the list is a small constant m:
a) INTEGER (output Parameter) containing the number of elements of
the array actually used.
---------------------- Page: 17 ----------------------
SIST EN 28651-1:1997
ISO 86514 : 1988 (E)
elements are of the appropriate
b) an array of dimension m, whose
simple-type.
list of n values of a compound type (for example, nx4xR)
This only occurs in an inquiry function. A Single cal1 returns a Single ele-
1
ment of the list exactly as for the list of values of one simple-type, except
/
that here the requested element is several FORTRAN Parameters.
array of integers (for example, nxnx1)
This is described more fully below, where the representations of CELL
ARRAY, PIXEL ARRAY and PATTERN ARRAY are described.
an ordered pair of different types (for example 1;E)
The different types are represented in turn in the FORTRAN Parameter
.
11st
Represented as a set of scalar values and an array of type CHARAC-
DATA RECORD
TER*80 containing the data. In addition, an INTEGER input Parameter
is used to dimension the array. Where the data record is an output
an additional argument ‘number of array elements of data
Parameter,
record occupied’ is needed. There are no scalar values except where the
data record contains values which are compulsory in GKS.
Although data tan be read from and written into the data record with the
and WRITE Statements, special Utility functions arc
FORTRAN READ
defined to pack INTEGER, REAL, and CHARACTER data into the data
record and to unpack the data record to the individual data items
e content of the packed data records is implementa-
(GPREC, GUREC). Th
tion dependent, but GPREC must perform the inverse function to GUREC
and vice versa.
The representation of CELL ARRAY, PIXEL ARRAY, and PATTERN allows the user of the
routines requiring a cell array Parameter to pass any Portion of the array as an argument. Two
examples should make this clear.
The User tan pass an entire two-dimensional array. In this case the number of columns of the cell
array is the Same as the first dimension of the FORTRAN array:
INTEGER DIMX, DIMY, CELLS (DIMX,DIMY)
CALL GCA (XI, Yl, X2, Y2, DIMX, DIMY, 1, 1, DIMX, DIMY, CELLS)
. . .
9 9 ? (DI~J)
(1 1) (2 1) (3 1)
. l .
? 9 9 (DIMW)
(12) (2 2) (3 2)
.
.
(;,DIMY) . . . (bIMX,DIMY)
(1,DIMY) (i,DIMY)
To use an arbitrary Portion of an array the user Passes the upper left corner of the Portion as the
starting address and the dimensions of the entire array for the proper treatment of addresses. The
area inside the small box is the cell array being passed:
INTEGER STARTX, STARTY, DX, DY, DIMX, DIMY, CELLS (DIMX,DIMY)
DATA STARTX/3/, STARTY/6/, DX/2/, DY/31
CALL GCA (Xl,YI,X2,Y2,DIMX,DIMY,STARTX,STARTY,DX,DY,CELLS)
10
---------------------- Page: 18 ----------------------
SIST EN 28651-1:1997
ISO 8651-1: 1988 (E)
. . .
(1 9 (2 9 i) (3 9 1) (4 9 1) (DIMW)
1)
. . .
(i 9 2) (2 9 2) (3 9 2) (4 9 2) (D@fv)
0 0 . . .
. . . . .
.
.
. . . (DIdX,B)
9
(16) (3 9 6) (4 9 6)
. . .
$f/ 9 (3 9 9 (DIMW)
(17) 7) (4 7)
. . .
(DIMw9
9 (3 9 8) (4 9 8)
(18)
0
.
. . . .
. . . . .
(1,DIk) 1 ,Dr& (P,D&Y) (P,D&Y) (3,DILY) (3,DILY) (4,DIkY) (4,DIkY) . . . (DIMX,kY)
9
11
---------------------- Page: 19 ----------------------
SIST EN 28651-1:1997
ISO 8651-1: 1988 (E)
6 Enumeration types
All the enumeration types of GKS are mapped to FORTRAN INTEGERs. The correspondence
between GKS scalars and FORTRAN INTEGERs is shown below in a list of symbolic FOR-
TRAN constants which may be included in any application program. The following section con-
tains a method of mapping GKS enumeration types to FORTRAN variable names. In a FOR-
TRAN 77 Subset implementation, this mapping could be accomplished by the DATA Statement.
Also, a numbering of all GKS functions is given for use in the error handling procedures.
Mnemonic FORTRAN names and their values for GKS ENUMERATION type values:
individual
aspect Source bundled,
INTEGER GBUNDL, GINDIV
PARAMETER (GBUNDL=O, GINDIV-1 )
conditionally, always
clear control flag
INTEGER GCONDI, GALWAY
PARAMETER (GCONDI=O, GALWAY=l )
clipping indicator noclip, Clip
INTEGER GNCLIP, GCLIP
PARAMETER (GNCLIP=O, GCLIP-1 )
colour available monochrome, colour
INTEGER GMONOC, GCOLOR
PARAMETER (Gh40N0k0, GcoLoR-i )
coordinate switch NDC
WC,
INTEGER GWC, GNDC
GNDC-1)
PARAMETER (GWC=O,
deferral mode ASAP, BNIG, BNIL, AST1
(see ISO 7942, subclause 4.5.3)
INTEGER GASAP, GBNIG, GBNIL, GAST1
GBNIL=2, GASTI=3)
PARAMETER (GASAP=O, GBNIG=l,
detectability undetectable, detectable
INTEGER GUNDET, GDETEC
PARAMETER(GUNDET=O, GDETEC~)
device coordinate units metres, other
INTEGER GMETRE, GOTHU
PARAMETER (GMETRE=O, GOTHU-1 )
display surface empty notempty,
empty
GEMPTY
INTEGER GNEMPT,
PARAMETER (GNEMPT=O, GEMPTY-1 )
dynamic modification IRG,
(See ISO 7942, subcla use 4.5.3)
INTEGER GIRG, GIMM
GIRG=O, GIMM=l)
PARAMETER
echo switch noecho, echo
INTEGER GNECHO, GECHO
PARAMETER GNECHO=O, GECHO-1 )
fl11 area interior style hollow, solid, Pattern, hatch
INTEGER GHOLLO, GSOLID, GPATTR, GHATCH
GPATTR=2, GHATCH-3 )
PARAMETER GHOLLO=O, GSOLID=l,
highlighting normal, highlighted
GHILIT
INTEGER GNORML,
PARAMETER GNORML=O, GHILIT-1 )
12
---------------------- Page: 20 ----------------------
SIST EN 28651-1:1997
ISO 86514 : 1988 (E)
input device Status none, nopick, nochoice
Oh
GNONE, GOK, GNPICK, GNCHOI
INTEGER
PARAMETER (GNONE=O, GOK=l, GNPICK=L, GNCHOI-2 )
none, locator, stroke, valuator, c hoice,
input class pick,
string
GSTROK, GVALUA,
INTEGER GNCLAS, GLOCAT, GCHOIC, GPICK,
GSTRIN
PARAMETER (GNCLAS=O, GLOCAT=l, GSTROK=2, GVALUA=3, GCHOIC-4, GPICK-5,
GSTRIN=6 )
suppressed, allowed
implicit regeneration mode
INTEGER GSUPPD, GALLOW
PARAMETER (GSUPPD=O, GALLOW-1 )
level of GKS LOa, Lob, LOC, Lla, Llb, Llc,
LSa, L2b, L2c
GLOB, GLOC, GLlA, GLlB,
INTEGER GLOA, GLlC,
*
GL2A, GL2B, GL2C
GLOC=2, GLlA=3,
PARAMETER (GLOA=O, GLOB=l, GLlB-4, GLlC=S,
*
GL2A=6, GL2B=7, GL2C=8 )
new frame action necessary no,
YeS
INTEGER GNO, GYES
GYES=l )
PARAMETER (GNO=O,
operating mode request, Sample, event
GEVENT
INTEGER GREQU, GSAMPL,
GSAMPL=l, GEVENT-2 )
PARAMETER (G
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.