Chapter 3. Workstation Description Tables

The following tables contain default values for the graphic workstations and adapters based on a:

• 23 inch display for the X workstation
• 23 inch display for the 6090 workstation
• 19 inch display for the 5080 workstation

The right-hand column in the tables lists the subroutine that you can use when you want your application to know the value for the facility.

The data types of the returned values are identified by the following codes:

Data Type

Definition

I Integer

A whole number

R Real

A floating-point number

S String

A character string

E Enumeration

A data type comprised of a set of values. The set is defined by enumerating the identifiers denoting the values.

n Quantity

This specifies an undesignated quantity of data.

Note:

The notation of n (number) [default] t (data type) indicates a collection of data of that type. This can be indicated in one of two ways:

1. by using notation such as 3[default]R (three real numbers), which could specify something like the x, y, and z coordinates of a three-dimensional point or RGB values
2. by using a variable number such as n[default]I, which specifies a collection of n integers.

The values identified with the symbol * reflect the default value of a workstation configuration variable; that is, this may not be the value of the variable in the actual workstation description table after the workstation is opened. (See The graPHIGS Programming Interface: Understanding Concepts for a discussion of this concept.)

Some tables are preceded by workstation-dependent and/or adapter-specific information.

The tables in this section are arranged in this order:

General Workstation Facilities

All Workstations

• The maximum display surface size changes with various display hardware. Use the Inquire Maximum Display Surface Size (GPQDS) subroutine to obtain the maximum display surface of your workstation (in device coordinate units and address units)screen ID='maxdss' XREFTEXT='-*-'.
• The default number of views is 16. The number of views can be increased via the View Table Entries (VWTBLSZ ) procopt. (See "VWTBLSZ (View Table Entries)")screen ID='vwtabl' XREFTEXT='-*-'.
• If the Inquire Rendering Target (GPQART) subroutine returns a value of zero for the number of rendering targets, then the specified workstation does not support explicit traversal. 

X

General Information Applying to All Adapters:

• The LANG environment variable determines the primary character set. For more information on primary character sets, see "Opening the X Workstation"screen
• Explicit traversal control is supported. If the workstation is in single buffer mode, then the Inquire Rendering Target (GPQART) subroutine returns a value of one for the number of available rendering targets. If the workstation is in double buffer mode, then GPQART returns a value of two for the number of available rendering targets. 

6090 and 5080

• Primary character sets depend on the hardware configuration of your workstation. For information on how to customize your workstation, see The GDDM/graPHIGS Programming Interface: Installation and Problem Diagnosis screen ID='primcs' XREFTEXT='-*-'.

IMAGE

• You can set the width and height of the display device in Device Coordinate address units via the Device Coordinate Address Units (DCUNITS) procopt.
• You can set the width and height of the display device in Device Coordinate meters via the Device Coordinate Meters (DCMETERS) procopt.
• For more information on setting the width and height with the display device, see "The IMAGE Workstation"screen

GDF

• Characteristics of the 3270-PC/GX are assumed for the target display device. For more information, see "The GDF Workstation"screen
• You can change the size of the display area using the Escape (GPES) subroutine (Escape 1003: GDF/CGM Plot Size). However, the Inquire Maximum Display Surface Size (GPQDS) does not reflect this change. 

CGM

• Characteristics of the 3270-PC/GX are assumed for the target display device. For more information, see "The CGM Workstation"screen
• You can change the size of the display area using the Escape (GPES) subroutine (Escape 1003: GDF/CGM Plot Size). However, the Inquire Maximum Display Surface Size (GPQDS) does not reflect this change. 

Table 8. General Workstation Facilities - X Workstation Default Values

Table 9. General Workstation Facilities

General Output Facilities

X

General Information Applying to All Adapters:

• BNIL (Before Next Input Locally) deferral mode is treated as BNIG (Before Next Input Globally) deferral mode.
• Polygon with Data Primitives: The primitive supports optional data that indicates that the application determined the convexity of the polygon. Specifying this optional data with the primitive definition enables better performance because the system rendering code does not have to determine the convexity of the polygon each time the polygon is rendered. To determine the convexity of a set of polygons, the graPHIGS API on the RS/6000 contains a sample program under the AIX directory:

  /usr/lpp/graPHIGS/samples/convexcheck

• Component frame buffers have three components. Indexed frame buffers have one component.
• Pixel Primitives: The pixel primitive is not part of the PHIGS definition and needs special consideration when using it on devices with frame buffers that are not eight bits deep. Because the pixel primitive only specifies eight bits of pixel data, there is no clear method map those eight bits to frame buffers that have other than eight bits of memory.

  For frame buffers with component organizations (such as the 24-bit 3D adapter), the eight bits are replicated into each component by the graPHIGS APIscreen This normally produces grey-scale images, since the same bits are put into each of the red, green, and blue frame buffer components.

  To replicate the pixel data to each frame buffer component, use the Set Frame Buffer Write Protect Mask (GPFBM) subroutine and the Pixel 2 (GPPXL2) subroutine three times, specifying that a different component of the frame buffer be unprotected each time.

  If, for example, you have a 24-bit component frame buffer and image data arranged in three groups for red, green, and blue,

  To write the red data:

  GPFBM(0xff00ffff);
  GPPXL2(red data);

  To write the green data:

  GPFBM(0xffff00ff);
  GPPXL2(green data);

  To write the blue data:

  GPFBM(0xffffff00);
  GPPXL2(blue data);

  Restore write protect mask:

  GPFBM(0x00000000);

  The High Performance 3D Color Graphics Display Processor is usually run in 12-bit double buffer mode and this adapter has components in BGR order instead of RGB order. When running in 12-bit double buffer mode, the graPHIGS API puts only the most significant four bits of the 8-bit pixel primitive data into each component because each frame buffer has only four bits in this mode.

Direct Window Access (DWA) Capabilities on the RS/6000 ONLY: In addition to the general capabilities applying to all adapters:

• Lighting, depth cueing and HLHSR (hidden line, hidden surface removal) are available.
• HLHSR (hidden line, hidden surface removal) can be applied to primitives by setting HLHSR to 2=ON_THE_FLY if the optional z-buffer feature is installed.
• There is no polysphere tessellation limitation.

• High Performance 3D Color Graphics Processor (8 bit or 24 bit):
  • If lighting calculation mode is not none and depth cue mode is 2=ALLOWED , then only lighting calculation mode is applied.
  • Only HLHSR (hidden line, hidden surface removal) identifiers 1=VISUALIZE_IF_NOT_HIDDEN , 2=VISUALIZE_IF_HIDDEN , 3=VISUALIZE_ALWAYS , and 4=NOT_VISUALIZE are supported.
  • Transparency mode is not supported.
  • Antialiasing mode is not supported.
  • An 8-bit processor may be used as an 8-bit single buffer (the default) or as a 4-bit double buffer. (See "FBUFFER (Frame Buffer Configuration)" for more details).

    A 24-bit processor may be used as a 24-bit single buffer or as a 12-bit double buffer (the default). (See "FBUFFER (Frame Buffer Configuration)" for more details).  

  • Pixel data in obstructed window areas is not returned when read from the frame buffer. The graPHIGS API returns an error.
  • Not all optional data is supported. See The IBM graPHIGS Programming Interface: Subroutine Reference screen
• High Performance Graphics Subsystem (Model 730, 8 bit or 24 bit) or POWER GtO (8 bit or 24 bit):
  • HLHSR (hidden line, hidden surface removal) identifier 10 (NOT_EQUAL ) is not supported. HLHSR identifier 2 (VISUALIZE_IF_HIDDEN ) applies only to line primitives.
  • Shading is enabled by setting depth cue mode to 2=ALLOWED or lighting calculation mode to 2=PER_AREA or 3=PER_VERTEX
  • Transparency modes of 2=PARTIAL_TRANSPARENT and 3=BLEND are supported, however: 
    • when using 2=PARTIAL_TRANSPARENT mode, you must also have the lighting calculation mode set to 2=PER_AREA or 3=PER_VERTEX (transparency mode 3=BLEND does not have this requirement).
    • Concave Polygons, Composite Fill Areas, Trimmed NURB Surfaces, Polygons with edge flag set to 2=ON , and Polygon with Data may be rendered using multiple passes. This multiple rendering includes the 3=BLEND transparency processing. Therefore, some parts (such as shared edges) show the results of this double-blending.
    • transparency processing is not face-dependent. The transparency coefficient from the front-face surface properties (set by the Set Surface Properties [GPSPR] subroutine) is always used.
    • transparency processing is applied during the rendering of lines and geometric text, as well as area primitives. To prevent lines and text from having transparency applied, the application can reset the transparency coefficient before the line and/or text primitives.
  • Antialiasing is supported, however:
    • Antialiasing is supported only for polyline primitives. 
    • Antialiasing is not performed when any of the following facilities are also used to render the polylines:
      • HLHSR, depth cueing, transparency, or lighting
      • Wide lines (line width scale factor other than 1.0)
      • Line type other than 1=SOLID_LINE
      • Scaled-to-fit line type rendering
      • Polyline shading method of 2=POLYLINE_SHADING_COLOR
    • Refer to the directory

      /usr/lpp/graPHIGS/samples/antialiasing

      for a sample of antialiasing.
    • Antialiasing may degrade performance due to the additional processing involved. To control degradation, two antialiasing modes are available: 2=SUBPIXEL_ON_THE_FLY and 3=NON_SUBPIXEL_ON_THE_FLY screen 2=SUBPIXEL_ON_THE_FLY results in the highest quality rendering but 3=NON_SUBPIXEL_ON_THE_FLY is faster. For correct visual results, your application must use values in the display color table that vary from 0.0 to 1.0 for each color component. For best results, your application should use gamma-corrected color component values. (If you wish to initialize the display color table with a linear ramp of color component values, you can use the Direct Color ( DIRCOLOR ) procopt. (See "DIRCOLOR (Direct Color)")screen The antialiasing facility is supported with 8-bit and 24-bit pixel memory. Special consideration is needed for 8-bit pixel memory.
  • Pixel data in obstructed window areas can be returned with unexpected results when read from the frame buffer.
• POWER Gt4x (8 bit or 24 bit):
  • Only transparency modes 1=NONE and 2=PARTIAL_TRANSPARENT are supported. 
  • Antialiasing is supported, however:
    • Only antialiasing mode 2=SUBPIXEL_ON_THE_FLY is supported. 
    • Antialiasing is supported only for polyline primitives.
    • Antialiasing is not performed when any of the following facilities are also used to render the polylines:
      • Wide lines (line width scale factor other than 1.0)
      • Line type has depth cueing set to 2=ALLOWED (this limitation applies to POWER Gt4x 8 bit only).
    • Refer to the directory

      /usr/lpp/graPHIGS/samples/antialiasing

      for a sample of antialiasing.
    • Antialiasing may degrade performance due to the additional processing involved. For correct visual results, your application must use values in the display color table that vary from 0.0 to 1.0 for each color component. For best results, your application should use gamma-corrected color component values. (If you wish to initialize the display color table with a linear ramp of color component values, you can use the Direct Color (DIRCOLOR ) procopt. (See "DIRCOLOR (Direct Color)")screen The antialiasing facility is supported with 8-bit and 24-bit pixel memory. Special consideration is needed for 8-bit pixel memory.

Non-Direct Window Access (non-DWA) Capabilities on the RS/6000 ONLY: In addition to the general capabilities supported by all adapters:

• Polysphere Primitives: The data generated by tessellation of polyspheres is limited to 65,000 bytes. If the generated data exceeds this amount, then part of your polysphere will not be displayed.

XSOFT

• Lighting, depth cueing and HLHSR (hidden line, hidden surface removal) are available.
• There is no polysphere tessellation limitation.

6090

• BNIL (Before Next Input Locally) deferral mode is treated as BNIG (Before Next Input Globally) deferral mode.
• Only HLHSR (hidden line, hidden surface removal) identifiers 1=VISUALIZE_IF_NOT_HIDDEN , 2=VISUALIZE_IF_HIDDEN , 3=VISUALIZE_ALWAYS , and 4=NOT_VISUALIZE are supported. HLHSR identifier 2 ( VISUALIZE_IF_HIDDEN ) applies only to line primitives.
• If you are using the optional shading feature:
  • You can process geometrical data if the HLHSR (hidden line, hidden surface removal) is set to 2=ON_THE_FLY , or depth cue mode is set to 2=ALLOWED , or lighting calculation mode is set to 2=PER_AREA or 3=PER_VERTEX screen
  • Line width is not supported.
• If you are not using the shading feature (HLHSR is set to 1=OFF , depth cue mode is set to 1=SUPPRESSED , and lighting calculation mode is set to 1=NONE ), then:
  • line style defaults to 2=SOLID and no shading is performed, if polyline end type is set to 2=ROUND or 3=SQUARE screen
  • the boundary flags defined in some primitives are ignored.
• Transparency mode is only applied when transparency mode is set to 2=PARTIAL_TRANSPARENT in the view table entry and lighting calculation mode is set to 2=PER_AREA or 3=PER_VERTEX screen

5080

• Only the nominal line width scale for circle, arc, and ellipse GDPs are supported.
• Pixel Primitives and Attributes: Pixel elements cannot be clipped to viewport or window boundaries. When a pixel element extends beyond a boundary, the element is replaced by a rectangle of the same size that is filled with the highlighting color.
• The number of pixel color indexes in one pixel primitive is limited to approximately 32,000.

IMAGE

• Lighting, depth cueing and HLHSR (hidden line, hidden surface removal) are available.
• There is no polysphere tessellation limitation.

GDF

• BNIL (Before Next Input Locally) deferral mode is treated as BNIG (Before Next Input Globally) deferral mode.
• Polysphere Primitives (AIX environment only): The data generated by tessellation of polyspheres is limited to 65,000 bytes. If the generated data exceeds this amount, then part of your polysphere will not be displayed.
• Pixel Primitives: Pixel primitives are not supported.

CGM

• BNIL (Before Next Input Locally) deferral mode is treated as BNIG (Before Next Input Globally) deferral mode.
• Polysphere Primitives (AIX environment only): The data generated by tessellation of polyspheres is limited to 65,000 bytes. If the generated data exceeds this amount, then part of your polysphere will not be displayed.
• For CGM metafile and picture descriptor element information, see "Delimiter Elements"screen For graphical primitives information, see "CGM Elements for Graphical Primitives"screen

Table 10. General Output Facilities - X Workstation Default Values

Table 11. General Output Facilities Default Values

Polyline Facilities

X

General Information Applying to All Adapters:

• Nominal, minimum, and maximum line widths and the size of the line pattern unit depend on the hardware configuration of your workstation. Use the Inquire Polyline Facilities (GPQPLF) subroutine to obtain the values supported on your workstation. 
• You can set the number of polyline table entries that can be active at any one time up to 128 via the Polyline Bundle Table (PLBTES ) procopt. (See "PLBTES (Polyline Bundle Table)")screen ID='Xpbunt' XREFTEXT='-*-'.

Direct Window Access (DWA) Capabilities on the RS/6000 ONLY: In addition to the general capabilities supported by all adapters:

• High Performance 3D Color Graphics Processor (8 bit or 24 bit), POWER GXT500, POWER GXT250P or GXT255P:
  • The line pattern is restarted at each vertex for wide lines that are greater than one pixel. 
• High Performance Graphics Subsystem (Model 730, 8 bit or 24 bit), POWER Gt4x (8 bit or 24 bit), POWER GtO (8 bit or 24 bit), POWER GXT500, POWER GXT250P or GXT255P:
  • When drawing a wide line with a line type other than 1=SOLID_LINE , the line end type is always 1=FLAT screen

Non-Direct Window Access (non-DWA) Capabilities on the RS/6000 ONLY: In addition to the general capabilities supported by all adapters:

• Color Graphics Display Adapter:
  • The line pattern unit is the same as the nominal line width. 
  • No line widths other than the nominal line width are supported. 

XSOFT

• Nominal, minimum, and maximum line widths and the size of the line pattern unit depend on the hardware configuration of your workstation. Use the Inquire Polyline Facilities (GPQPLF) subroutine to obtain the values supported on your workstation.
• You can set the number of polyline table entries that can be active at any one time up to 128 via the Polyline Bundle Table (PLBTES ) procopt. (See "PLBTES (Polyline Bundle Table)")screen
• The line pattern is restarted at each vertex for wide lines that are greater than one pixel.
• When drawing a wide line with a line type other than 1=SOLID_LINE , the line end type is always 1=FLAT screen

6090

• You can set the number of polyline table entries that can be active at any one time up to 128 via the Polyline Bundle Table (PLBTES ) procopt. (See "PLBTES (Polyline Bundle Table)")screen ID='6pbunt' XREFTEXT='-*-'.
• Nominal, minimum, and maximum line widths depend on the hardware configuration of your workstation. Use the Inquire Polyline Facilities (GPQPLF) subroutine to obtain the values supported on your workstation. 
• When an end type of 2=ROUND or 3=SQUARE is applied to wide lines, only a line type of 1=SOLID_LINE is supported. 

5080

• Nominal, minimum, and maximum line widths depend on the hardware configuration of your workstation. Use the Inquire Polyline Facilities (GPQPLF) subroutine to obtain the values supported on your workstation. 
• The number of vertexes in one polyline primitive is limited to approximately 5,000 for two-dimensional and 4,000 for three-dimensional polyline primitives.

GDDM*

• Nominal, minimum, and maximum line widths depend on the hardware configuration of your workstation. Use the Inquire Polyline Facilities (GPQPLF) subroutine to obtain the values supported on your workstation. 

IMAGE

• Nominal, minimum, and maximum line widths and the size of the line pattern unit depend on the hardware configuration of your workstation. The nominal line is the width of the pixel which can be modified by using the DCUNITS or DCMETERS procopts.

GDF

• The nominal line width is 0.000269 meters regardless of how the GDF file is scaled (i.e., the nominal line width for the graPHIGS API is independent of the metric scale factor of the resultant GDF file). This results in a line width of 0.96 Virtual Device Coordinates (VDC). The effective maximum line width is the size of the workstation display area (0.2582728 meters). However, the size of the display area can be modified using the Escape (GPES) subroutine. 
• Wide lines are clipped to their center.

CGM

• The nominal line width is 0.000258 meters regardless of how the CGM file is scaled (i.e., the nominal line width for the graPHIGS API is independent of the metric scale factor of the resultant CGM file). This results in a line width of 0.96 Virtual Device Coordinates (VDC). See "Picture Descriptor Elements" for more information about VDCs. The effective maximum line width is the size of the workstation display area (0.2582728 meters). However, the size of the display area can be modified using the Escape (GPES) subroutine. 
• Wide lines are clipped to their center.
• For CGM picture descriptor element information on line width specification mode, see under "Picture Descriptor Elements"screen
• For CGM attribute information on line types, see "CGM Line Attributes"screen

Table 12. Polyline Facilities - X Workstation Default Values

Table 13. Polyline Facilities Default Values

Table 14. Predefined Polyline Bundle Table

Table 15. Predefined Line Types

Polymarker Facilities

X

General Information Applying to All Adapters:

• Nominal, minimum, and maximum marker sizes depend on the hardware configuration of your workstation. Use the Inquire Polymarker Facilities (GPQPMF) subroutine to obtain the values supported on your workstation. 
• You can set the number of polymarker bundle table entries that may be active at any one time up to 128 via the Polymarker Bundle Table (PMBTES ) procopt. (See "PMBTES (Polymarker Bundle Table)")screen ID='Xpmbt' XREFTEXT='-*-'.

6090

• Nominal, minimum, and maximum marker sizes depend on the hardware configuration of your workstation. Use the Inquire Polymarker Facilities (GPQPMF) subroutine to obtain the values supported on your workstation. 
• You can set the number of polymarker bundle table entries that may be active at any one time up to 128 via the Polymarker Bundle Table (PMBTES ) procopt. (See "PMBTES (Polymarker Bundle Table)")screen ID='6pmbt' XREFTEXT='-*-'.

5080

• Nominal, minimum, and maximum marker sizes depend on the hardware configuration of your workstation. Use the Inquire Polymarker Facilities (GPQPMF) subroutine to obtain the values supported on your workstation. 
• The number of polymarkers in one polymarker primitive is limited to approximately 8,000 for the 2D primitive and 5,000 for the 3D primitive.
• The marker size scale factors supported are:
  • 1.50 (5080 large markers)
  • 1.25 (5080 medium markers)
  • 1.00 (5080 basic markers)
  • 0.75 (5080 small markers)

• Nominal, minimum, and maximum marker sizes depend on the hardware configuration of your workstation. Use the Inquire Polymarker Facilities (GPQPMF) subroutine to obtain the values supported on your workstation. 

CGM

• The nominal marker width is 0.00258 meters regardless of how the CGM file is scaled (i.e., the nominal marker width for the graPHIGS API is independent of the metric scale factor of the resultant CGM file). The effective maximum marker width is the size of the workstation display area (0.2582728 meters). However, the size of the display area can be modified using the Escape (GPES) subroutine. 
• Polymarkers are represented as a series of CGM polylines. For more information, see line attributes "CGM Line Attributes"

Table 16. Polymarker Facilities - X Workstation Default Values

Table 17. Polymarker Facilities Default Values

Table 18. Predefined Polymarker Bundle Table

Table 19. Predefined Marker Types

Text Facilities

X

General Information Applying to All Adapters

• You can set the number of text bundle entries that may be active at any one time up to 128 via the Text Bundle Table (TXBTES ) procopt. (See "TXBTES (Text Bundle Table)")screen ID='genntbt' XREFTEXT='-*-'.

• Annotation Text Primitives and Attributes:
  • Annotation up vector, annotation alignment, and character positioning mode are not supported.
  • Character precision (CHAR_PREC ) is supported the same as string precision (STRING_PREC ) with the additional attribute support for annotation text path, character spacing, and character expansion factor.
  • Only font 1 of the primary character set is available. This may be character set 6, 8, 9, 10, 11 or 12. For a discussion of how to set the primary character set, see "Opening the X Workstation"screen  
  • Kanji (character set identifier 128), Hangul (character set identifier 129), Traditional Chinese (character set identifier 130), Simplified Chinese (character set identifier 132) and Unicode (character set identifier 131) are not supported.
• Geometric Text Primitives and Attributes:
  • Geometric proportional fonts are supported.

Direct Window Access (DWA) Capabilities on the RS/6000 ONLY: In addition to the general capabilities supported by all adapters:

• All annotation text attributes are supported.
• Geometric text culling is supported for 2D and 3D primitives.

• POWER GXT1000, POWER GXT500, POWER GXT250P or GXT255P, POWER GXT500P, or POWER GXT550P:
  • Character precision (CHAR_PREC ) produces the same result as stroke precision (STROKE_PREC )screen
• High Performance 3D Color Graphics Processor (8 bit or 24 bit) or POWER Gt4x (8 bit or 24 bit):
  • Character precision (CHAR_PREC ) produces the same result as stroke precision (STROKE_PREC )screen

Non-Direct Window Access (non-DWA) Capabilities on the RS/6000 ONLY: In addition to the general capabilities supported by all adapters:

• Geometric Text Primitives and Attributes:
  • Geometric text culling is supported for 2D primitives.

XSOFT

• Character precision (CHAR_PREC ) produces the same result as stroke precision (STROKE_PREC )screen

6090

Annotation Text Primitives and Attributes:

• Character precision (CHAR_PREC ) produces the same result as (STROKE_PREC )screen
• Only font 1 of the primary character set is available. This may be character set 6 or 8.
• Kanji (character set identifier 128), Hangul (character set identifier 129), Traditional Chinese (character set identifier 130), Simplified Chinese (character set identifier 132), and Unicode (character set identifier 131) are not supported.

Geometric Text Primitives and Attributes:

• You can set the number of text bundle entries that may be active at any one time up to 128 via the Text Bundle Table (TXBTES ) procopt. (See "TXBTES (Text Bundle Table)")screen
• All geometric text attributes are supported.
• Character precision (CHAR_PREC ) produces the same result as stroke precision (STROKE_PREC )screen
• Hangul (character set identifier 129), Traditional Chinese (character set identifier 130), Simplified Chinese (character set identifier 132), and Unicode (character set identifier 131) are not supported.

5080

Annotation Text Primitives and Attributes:

• The number of characters in one annotation text primitive is limited to approximately 32,000.
• Annotation text relative is not supported.
• Character positioning mode is ignored; the 5080 supports only constant-sized annotation characters. Character expansion factor, annotation up vector, and annotation alignment are not supported.
• Character precision (CHAR_PREC ) is the highest annotation precision supported. If you specify stroke precision (STROKE_PREC ), then CHAR_PREC is used.
• Only font 1 of the primary character set is available. This may be character set 1 through 7, or 9 depending on the current customized language feature of the 5080.
• Kanji (character set identifier 128), Hangul (character set identifier 129), Traditional Chinese (character set identifier 130), Simplified Chinese (character set identifier 132), and Unicode (character set identifier 131) are not supported. 
• The annotation height scale factors supported by the 5080 are:
  • 1.50 (5080 large characters)
  • 1.25 (5080 medium characters)
  • 1.00 (5080 basic characters)
  • 0.75 (5080 small characters)

Geometric Text Primitives and Attributes:

• The default number of geometric chraracter sets that may be active at any one time is three. You may set this number to any value up to ten via the Font Pool Size (FONTPSIZ ) procopt. (See "FONTPSIZ (Font Pool Size)")screen ID='58gcs' XREFTEXT='-*-'.
• The number of characters in one geometric text primitive is limited to approximately 32,000.
• Character precision (CHAR_PREC ) produces the same result as stroke precision (STROKE_PREC )screen
• Character positioning mode is not supported.
• For user-defined character sets, the default character is ignored; it is always the hyphen. For additional information on limitations for user-defined character sets, see "IBM 5080 Character Set Restrictions"screen

• Kanji: If you use Kanji (character set identifier 128), it must be available in the workstation prior to invocation of the graPHIGS API using the 5080 Japanese Language Feature. For information on how to customize your 5080 to support Kanji, The GDDM/graPHIGS Programming Interface: Installation and Problem Diagnosis screen

  On opening the workstation, if the graPHIGS API finds a valid memory area for output Kanji then output Kanji is made available for output to the workstation (although the application must still activate it). If the Kanji output and input memory areas are detected, and Katakana is the primary character set, then input is made available for input from the workstation. After opening the workstation, the Kanji font is never deleted.

• Hangul: If you use Hangul (character set identifier 129), it must be available in the workstation prior to invocation of the graPHIGS API using the 5080 Korean Language Feature. For information on how to customize your 5086 to support Hangul, The GDDM/graPHIGS Programming Interface: Installation and Problem Diagnosis screen

  On opening the workstation, if the graPHIGS API finds a valid memory area for output Hangul then output Hangul is made available for output to the workstation (although the application must still activate it). If the Hangul output and input memory areas are detected, and csid 9 is the primary character set, then Hangul is made available for input from the workstation. After opening the workstation, the Hangul font is never deleted.

• Traditional Chinese: Traditional Chinese (character set identifier 130) is not supported.
• Simplified Chinese: Simplified Chinese (character set identifier 132) is not supported.
• Unicode: Unicode (character set identifier 131) is not supported.

GDDM

Annotation Text Primitives and Attributes:

• Character expansion factor, annotation up vector, annotation alignment and character positioning mode are not supported.
• Annotation text relative is not supported.
• Character precision (CHAR_PREC ) is the highest precision supported. If you specify stroke precision (STROKE_PREC ), then CHAR_PREC is used.
• Only font 1 of the primary character set is available.
• The number of available annotation height size scale factors is one.

Geometric Text Primitives and Attributes:

• The number of characters in one geometric text primitive is limited to approximately 32,000.

• In CHAR_PREC and STRING_PREC precision, characters are clipped on a character basis. If any part of a character is clipped, the entire character is not visible.
• Traditional Chinese (character set identifier 130) is not supported.
• Unicode (character set identifier 131) is not supported.

IMAGE

• Character precision (CHAR_PREC ) produces the same result as stroke precision (STROKE_PREC )screen

GDF

Annotation Text Primitives and Attributes:

• Character expansion factor, annotation up vector, annotation alignment, and character positioning mode are not supported.
• Character precision (CHAR_PREC ) produces the same results as stroke precision (STROKE_PREC )screen
• Only font 1 of the primary character set is available.
• Character code points are written directly into the CGM file. The characters drawn depend on your interpreter. The output metafile does not specify a character set or font. It uses the default of the interpreter.
• The number of available annotation height scale factors is one. The size is determined by the output system default.
• Pixel primitives and annotation text are not clipped to the exterior of obscuring views, even if the obscuring view has view shielding set to 2=ON screen

Geometric Text Primitives and Attributes:

• Traditional Chinese (character set identifier 130) is not supported.

CGM

Annotation Text Primitives and Attributes:

• Character precision (CHAR_PREC ) produces the same results as stroke precision (STROKE_PREC )screen
• Available annotation text character sets supported depend on the configuration of your workstation. Use the Inquire Primary Character Set (GPQPCS) subroutine to obtain the values supported on your workstation.
• Only font 1 of the primary character set is available.
• Character code points are written directly into the CGM file. If the nucleus is running in an EBCIDIC environment, then code points are first translated to ASCII using the translation table for character set 1. The characters drawn depend on your interpreter. The output metafile does not specify a character set or font. It uses the default of the interpreter.
• Kanji (character set identifier 128), Hangul (character set identifier 129), Traditional Chinese (character set identifier 130), and Unicode (character set identifier 131) are not supported.
• The nominal height scale factor is 1/100 of the default display surface size. Use the Escape Subroutine (1010: Inquire Mapped Display Surface Size) to determine the size of your display. An annotation height scale factor of zero would result in 0.0000001* nominal height which is minute in size (i.e., a point). For more information on scaling, see scaling mode under "Picture Descriptor Elements"screen
• Pixel primitives and annotation text are not clipped to the exterior of obscuring views, even if the obscuring view has view shielding set to 2=ON screen
• For CGM attribute information on text, see "CGM Text Attributes"screen

Geometric Text Primitives and Attributes:

• Traditional Chinese (character set identifier 130) is not supported.

Table 20. Text Facilities - X Workstation Default Values

Table 21. Text Facilities Default Values

Table 22. Predefined Text Bundle

Interior Facilities

For performance reasons, some graPHIGS API workstations choose not to draw the boundary of a polygon if the edge flag is set to 2=ON screen This may avoid drawing the polygon outline twice. If you use a non-solid edge type, then you may get different output on different devices, since the boundary color may or may not be visible between the edge segments.

X

General Information Applying to All Adapters:

• You can set the number of interior bundle table entries that may be active at any one time up to 128 via the Interior Bundle Table (IBTES ) procopt. (See "IBTES (Interior Bundle Table)")screen ID='xmnibte' XREFTEXT='-*-'.

Non-Direct Window Access (non-DWA) Capabilities on the RS/6000 ONLY: In addition to the general capabilities supported by all adapters:

• Availability of hatch representation is NONE screen
• There are six available hatch styles.
• Available hatch styles are 1-6.
• There is no hatch definition format.
• There is no pattern definition format.
• There are no pattern indexes.
• There are a total of four interior styles.
• The available interior styles are 1=HOLLOW , 2=SOLID , 4=HATCH , 5=EMPTY screen
• Hatch styles 21 and 22 (see Table 26) are predefined as vertical lines. These hatch styles are similar in appearance to hatch style 1.

6090

• Patterns are not transformable.
• If you are using the shading feature (HLHSR is set to 2=ON_THE_FLY , or depth cue mode is set to 2=ALLOWED , or lighting calculation is set to 2=PER_AREA or 3=PER_AREA ), then interior styles 1=HOLLOW , 3=PATTERN and 4=HATCH are not supported. Interior style 1=HOLLOW defaults to 5=EMPTY screen Interior styles 3=PATTERN and 4=HATCH default to 2=SOLID screen
• You can set the number of interior bundle table entries that may be active at any one time up to 128 via the Interior Bundle Table (IBTES ) procopt. (See "IBTES (Interior Bundle Table)")screen ID='69via' XREFTEXT='-*-'.

5080

• The number of vertices in one polygon primitive is variable and depends on factors such as the coordinate distances when converted to 5080 coordinate units and the number of subareas. When subareas are used, the number of vertexes supported decreases by the number of subareas. The area fill is limited to 350 polygon points; if this maximum is exceeded, then the graPHIGS API does not fill the polygon.
• Hatch styles 21 and 22 (see Table 26) are predefined as vertical lines. These hatch styles are similar in appearance to hatch style 1.
• For an interior style of 4=HATCH , the polygon is first filled using color index 0 and then the hatch pattern is overlaid in the specified color. In other words, 4=HATCH interior style is similar to 3=PATTERN in that you cannot see primitives behind the hatching pattern.
• Patterns are not transformable.
• When the projection type is set to 2=PERSPECTIVE , then interior styles 2=SOLID , 3=PATTERN , and 4=HATCH remain in parallel projection. They are always displayed using 1=PARALLEL projection type. For example, your application defines a polygon with an interior style, with edge flag set to 2=ON and with projection type set to 1=PARALLEL screen If you change the projection type from 1=PARALLEL to 2=PERSPECTIVE , then the graPHIGS API displays only the edge in perspective. The filled interior style does not change.
• The graPHIGS API clips polygon edges in the z direction; however, the graPHIGS API does not clip polygon interiors.

GDDM

• Patterns are not transformable.
• Interior style 3=PATTERN is not available on plotter devices; 1=HOLLOW is used instead. Only a monochrome pattern is available on 3270 PC/G, GX devices.
• The maximum pattern size depends on the device cells. The Set Pattern Representation (GPPAR) subroutine function repeats or truncates the specified pattern to achieve a maximum pattern.

GDF

• All hatch styles are supported. However, the hatch displayed is dependent on the post-processing routine and device.
• Many interpreters do not support patterns, especially when the output device is a post-processing device, such as a pen plotter. When patterns are supported, the pattern definition is not preserved in the file. The pattern displayed is dependent on the post-processing routine and device.

  Device

  Size

  3270-PC/G

  8 by 15

  3270-PC/GX

  8 by 15

  3279-Display

  9 by 16

CGM

• There is no limit on the maximum pattern size (x size, y size). A logical limit would be 960[default]960, but this may exceed memory constraints. 
• Many interpreters do not support patterns, especially when the output device is a post-processing device, such as a pen plotter.
• For CGM attribute information on hatch and interior styles, see "CGM Interior Attributes"screen

Table 23. Interior Facilities - X Workstation Default Values

Table 24. Interior Facilities Default Values

Table 25. Predefined Interior Bundle Tables

Table 26. Default Hatch Table

Table 27. Predefined Pattern Table

Edge Facilities

X

General Information Applying to All Adapters

• Nominal, minimum, and maximum edge widths supported depend on the hardware configuration of your workstation. Use the Inquire Edge Facilities (GPQEF) subroutine to obtain the values supported on your workstation. 
• You can set the number of edge bundle table entries that may be active at any one time up to 128 via the Edge Bundle Table (EBTES ) procopt. (See "EBTES (Edge Bundle Table)")screen ID='giaebt' XREFTEXT='-*-'.

Direct Window Access (DWA) Capabilities on the RS/6000 ONLY: In addition to the general capabilities supported by all adapters:

• POWER GXT1000, POWER GXT500, or POWER GXT250P or GXT255P:
  • Only nominal edge line width is supported.
• High Performance 3D Color Graphics Processor (8 bit or 24 bit):
  • Surface primitives do not support edge attributes.
• High Performance Graphics Subsystem (Model 730, 8 bit or 24 bit) or POWER GtO (8 bit or 24 bit):
  • Only nominal edge line width is supported. 
  • Edge line style is not applied in the following cases:
    • when rendering the Triangle Strip 3 primitive
    • when rendering trimmed surface primitives
    • when rendering Quadrilateral Mesh 3
• POWER Gt4x (8 bit or 24 bit):
  • If edge line style other than SOLID_LINE is specified, then the edge line width defaults to a value of 1.0.

Non-Direct Window Access (non-DWA) Capabilities on the RS/6000: In addition to the general capabilities supported by all adapters:

• Color Graphics Display Adapter
  • Only nominal edge line width is supported. 

XSOFT

• Only nominal edge line width is supported.

6090

• Surface primitives do not support edge attributes.
• Only nominal edge line width is supported.
• Nominal, minimum, and maximum edge widths supported depend on the hardware configuration of your workstation. Use the Inquire Edge Facilities (GPQEF) subroutine to obtain the values supported on your workstation. 
• You can set the number of edge bundle table entries that may be active at any one time up to 128 via the Edge Bundle Table (EBTES ) procopt. (See "EBTES (Edge Bundle Table)")screen ID='x69ebt' XREFTEXT='-*-'.

5080

• Only nominal edge line width is supported.

GDDM

• Nominal, minimum, and maximum edge widths supported depend on the hardware configuration of your workstation. Use the Inquire Edge Facilities ( GPQEF) subroutine to obtain the values supported on your workstation. 

IMAGE

• Only nominal edge line width is supported.

CGM

• The nominal edge width is 0.000258 meters regardless of how the CGM file is scaled (i.e., the nominal edge width for the graPHIGS API is independent of the metric scale factor of the resultant CGM file). The effective maximum edge width is the size of the workstation display area (0.2582728 meters). However, the size of the display area can be modified using the Escape (GPES) subroutine. 
• For CGM attribute information on edge types, see "CGM Edge Attributes"screen

Table 28. Edge Facilities - X Workstation Default Values

Table 29. Edge Facilities Default Values

Table 30. Predefined Edge Bundle

Color Facilities

X

General Information Applying to All Adapters

• The number of available colors or intensities supported depend on the hardware configuration of your workstation. Use the Inquire Color Facilities (GPQCF) subroutine to obtain the color facilities supported on your workstation. 
• The default color table identifier is -1=DISPLAY_COLOR_TABLE , with the following exceptions: 
  • When the Direct Color (DIRCOLOR ) procopt (see "DIRCOLOR (Direct Color)") or the Do Not Create an X Color Map (XNOCLRMP ) procopt (see "XNOCLRMP (Do Not Create an X Color Map)") and the X Window Identifier (XWINDID ) procopt (see "XWINDID (X Window Identifier)") are specified, the default color table identifier is 0=RENDERING_COLOR_TABLE screen
  • On the High Performance 3D Color Graphics Processor (24 bit), the default color table identifier is 0=RENDERING_COLOR_TABLE screen

Direct Window Access (DWA) Capabilities on the RS/6000 ONLY: In addition to the general capabilities supported by all adapters:

• High Performance 3D Color Graphics Processor (8 bit):
  • The order of color components for color quantization is Red, Green, Blue (RGB) for 4 bit double-buffer mode and is Blue, Green, Red (BGR) for all other modes.
  • The number of color processing table entries you can define is zero; however, 15 are supported for 4 bit double-buffer mode. For a description of color on this processor, see The graPHIGS Programming Interface: Understanding Concepts screen ID='sabcpt' XREFTEXT='-*-'.
• High Performance 3D Color Graphics Processor (24 bit):
  • The order of color components for color quantization is Blue, Green, Red (BGR) for 12 bit double-buffer mode and is Red, Green, Blue (RGB) for all other modes. 
  • The number of color processing table entries you can define is zero. For a description of color on this processor, see The graPHIGS Programming Interface: Understanding Concepts screen
• POWER GXT500 or POWER GXT250P or GXT255P
  • The list of colors for each frame buffer component is dependent on the visual class.
• Color Graphics Display Adapter (8-bit)
  • The list of colors for each frame buffer component is 3,3,2; however, the list is 1,2,1 for 4 bit double-buffer mode. 

Non-Direct Window Access (DWA) Capabilities on the RS/6000 ONLY: In addition to the general capabilities supported by all adapters:

• Color availability depends on the hardware configuration of your workstation.
• The maximum number of display color table entries you can define is 256; however, 16 are supported for a 4 bit display device. 

XSOFT

• The list of colors for each frame buffer component is dependent on the visual class.

6090

• The number of definable color processing table entries supported depends on the hardware configuration of your workstation. Use the Inquire Color Facilities (GPQCF) subroutine to obtain the color facilities supported on your workstation. 
• The list of colors for each frame buffer component is 8,8,8 for 24 bit single-buffer mode and 3,3,2 for 8 bit double-buffer mode. 

5080

• The number of available colors or intensities, color availability, and the maximum number of predefined display color table entries supported depend on the hardware configuration of your workstation. Use the Inquire Color Facilities (GPQCF) subroutine to obtain the color facilities supported on your workstation. 
• The use of any of the 5086 windowing features or selective pick through SETUP panel 01-01 will reserve color table entries 120-127 for hardware use. Applications using these color table entries with this feature will produce unexpected display results.

GDDM

• The number of available colors or intensities, and color availability supported depend on the hardware configuration of your workstation.  Use the Inquire Color Facilities (GPQCF) subroutine to obtain the color facilities supported on your workstation.

IMAGE

• The maximum number of available colors or intensities that can be represented in the output file is 255³ screen displayed is dependent on the output device and the image output format. You can set the image output format via the Image Output Format (IMAGEFMT) procopt.
• For more information on color and the IMAGE workstation, see "The IMAGE Workstation"screen

GDF

• The maximum number of available colors or intensities that can be represented in the output metafile is 16. The actual number displayed is dependent on the output device and the metafile interpreter. 

CGM

• The maximum number of available colors or intensities that can be represented in the output metafile is 10⁹ screen The actual number displayed is dependent on the output device and the metafile interpreter. 
• The line color, text color (for annotation text only), fill color, and edge color each has a value between 0 and the maximum color index.
• For CGM metafile and picture descriptor element information on color, see "Delimiter Elements" and under "Picture Descriptor Elements"screen

Table 31. Color Facilities - X Workstation Default Values

Table 32. Color Facilities Default Values

Table 33. Default Color Tables

Generalized Drawing Primitive (GDP) Facilities

X

General Information Applying to All Adapters:

• Polygon with Data Primitives: The primitive supports optional data that indicates that the application determined the convexity of the polygon. Specifying this optional data with the primitive definition enables better performance because the system rendering code does not have to determine the convexity of the polygon each time the polygon is rendered. To determine the convexity of a set of polygons, the graPHIGS API on the RS/6000 contains a sample program under the AIX directory: 

  /usr/lpp/graPHIGS/samples/convexcheck

   

Direct Window Access (DWA) Capabilities on the RS/6000 ONLY: In addition to the general capabilities supported by all adapters:

• The list of Generalized Drawing Primitives (GDPs) including the advanced Drawing Primitives are supported.

• POWER GT4 family and the POWER GXT1000:
  • Composite Fill Areas are supported on AIX 3.2.x and AIX 4.1.3 and earlier. GDP 1027 is not supported on AIX 4.1.4 and later.
• High Performance Graphics Subsystem (8 bit or 24 bit) or POWER GtO:
  • Composite Fill Areas with edge flag set to 1=OFF , will display edges.
• POWER Gt4x (8 bit or 24 bit):
  • Polyline Set 3 With Data (GPD 1014) is not supported. 

6090

• If you are using the shading feature (HLHSR mode is set to 2=ON_THE_FLY , or depth cue mode is set to 2=ALLOWED , or lighting calculation mode is set to 2=PER_AREA or 3=PER_VERTEX ) with Polygon 2/3 with Data, the boundary of the polygon that is defined by the vertex data is assumed to be non-intersecting. If the boundary intersects itself, the visual effect is indeterminate.

  See The graPHIGS Programming Interface: Understanding Concepts for more details.

• Composite Fill Areas with edge flag set to 1=OFF , will display edges.

5080

• The number of available generalized drawing primitives supported depends on the hardware configuration of your workstation. Use the Inquire List of Generalized Drawing Primitives (GPQGD) subroutine to obtain the generalized drawing primitives supported on your workstation. 

Table 34. Generalized Drawing Primitives (GDP) Facilities - X Workstation Defaults

Table 35. Generalized Drawing Primitives (GDP) Facilities Default Values

Table 36. Available Generalized Drawing Primitives

Generalized Structure Element (GSE) Facilities

X

General Information Applying to All Adapters:

• The z-buffer protect mask is not supported except on the POWER Gt4x (8 bit or 24 bit), XSOFT, POWER GXT500screen and on POWER GXT250P or GXT255Pscreen  

Direct Window Access (DWA) Capabilities on the RS/6000 ONLY: In addition to the general capabilities supported by all adapters:

• POWER Gt4x (8 bit or 24 bit):
  • Frame Buffer Comparison: The mask parameter specified on this structure element is not supported. 
  • The z-buffer protect mask is supported.

Non-Direct Window Access (non-DWA) Capabilities on the RS/6000 ONLY: In addition to the general capabilities supported by all adapters:

• Only the set frame buffer protect mask is supported.

XSOFT

• The z-buffer protect mask is supported.

IMAGE

• The z-buffer protect mask is supported.

Table 37. Generalized Structure Element (GSE) Facilities - X Default Values

Table 38. Generalized Structure Element (GSE) Facilities Default Values

Table 39. GSE Values

Escape Facilities

5080

• When a user switches the 5080 between S/390 host interactive mode and PC mode, the workstation state (display storage, color look-up table, memory management control, etc.) is not preserved.

  Your application should ensure that no functions are performed while the user is in non-host or PC mode. By closing and re-opening the workstation when a user switches, you avoid unpredictable results and I/O errors.

  Your application can monitor the link switch status by using Escape identifier 1002, Enable/Disable (GPES). When a user switches to PC mode, keep the workstation open but allow no update or I/O operations. When the user switches back to host mode, close and re-open the workstation immediately.

GDF/CGM

• Escape identifier 1003 (GDF/CGM Plot Size) allows your application to directly specify the width of the plotted output. The plotting utility provided with the graPHIGS API uses this information to correctly plot the GDF/CGM contents.

CGM

• Escape identifier 1014 (Workstation-Dependent Output) allows your application to directly render data to the workstation. It is the application's responsibility to ensure that the data is valid (proper length(s), identifiers, padding, etc.)screen For more information, see "Workstation Dependent Output" or the Escape (GPES) subroutine in The graPHIGS Programming Interface: Subroutine Reference screen

Table 40. Escape Facilities - X Workstation Default Values

Table 41. Escape Facilities Default Values

Table 42. Escape Values

Image Facilities

For image facilities that may be supported by the graPHIGS API, see the Image Board Facilities in Table 93screen

Table 43. Image Facilities - X Workstation Default Values

Table 44. Image Facilities

Advanced Output Facilities

X

Direct Window Access (DWA) Capabilities on the RS/6000 ONLY:

• The number of light source table entries can be increased via the Light Source Table (LSTES ) procopt. (See "LSTES (Light Source Table)").  
• The number of definable depth cue table entries can be increased via the Depth Cue Table (DCTES ) procopt. (See "DCTES (Depth Cue Table)").  

• High Performance 3D Color Graphics Processor (8 bit or 24 bit):
  • An ambient light source plus eight other light sources are available. 4=SPOT light source type is not supported. 
  • If lighting calculation mode is not set to 1=NONE and depth cue mode is 2=ALLOWED , then only lighting calculation mode is applied.
  • The Set Face Lighting Method (GPFLM) subroutine is not supported. Lighting processing is always face lighting method 1=FACE_INDEPENDENT screen
  • The method for calculating the specular lighting term differs (for the X Workstations) from the method documented in the The graPHIGS Programming Interface: Understanding Concepts screen The effect is that specular lighting falls off slower, causing highlights to appear less focused. To achieve the normal specular effects, an application should specify a specular coefficient that is four times greater than the normal value.
• High Performance Graphics Subsystem (Model 730, 8 bit or 24 bit), POWER GtO (8 bit or 24 bit), or POWER Gt4x (8 bit or 24 bit):
  • An ambient light source plus eight other light sources are available. Up to four of the eight light sources can be spotlight sources. 
  • The POWER GtO is limited to 64 control points in the u direction for a NURB or trimmed NURB surface. A NURB surface primitive with more than 64 control points in the u direction is ignored at traversal.
  • The POWER GtO supports spot light concentration exponent values that are a power of 2. Any value specified will be mapped to the closest power of 2 supported.
  • The POWER GtO performs lighting calculations in View Coordinates rather than World Coordinates. These calculations are adjusted to account for the difference in the coordinates. However, if the view transformation is not isotropic ( i.e. is not a uniform mapping in X, Y, and Z), then the adjustment is not sufficient and the lighting results may differ from other workstations that perform lighting in World Coordinates.

XSOFT

• The number of light source table entries can be increased via the Light Source Table (LSTES ) procopt. (See "LSTES (Light Source Table)").
• The number of definable depth cue table entries can be increased via the Depth Cue Table (DCTES ) procopt. (See "DCTES (Depth Cue Table)").

6090

• The number of light source table entries can be increased via the Light Source Table (LSTES ) procopt. (See "LSTES (Light Source Table)").  
• The number of definable depth cue table entries can be increased via the Depth Cue Table (DCTES ) procopt. (See "DCTES (Depth Cue Table)").  
• An ambient light source plus eight other light sources are available. Up to four of the eight light sources can be spotlight sources. 
• The specular reflection exponent is mapped to a power of 2.
• The Set Face Lighting Method (GPFLM) subroutine is not supported. Lighting processing is always face lighting method 2=FACE_DEPENDENT screen

Table 45. Advanced Output Facilities - X Workstation Default Values

Table 46. Advanced Output Facilities Default Values

Curve and Surface Facilities

Table 47. Curve and Surface Facilities - X Default Values

Table 48. Curve and Surface Facilities Default Values

Advanced Attribute Facilities

X

Direct Window Access (DWA) Capabilities on the RS/6000 ONLY:

• The advanced rendering attributes are supported.

• High Performance 3D Color Graphics Processor (8 bit or 24 bit):
  • Spheres do not support lighting calculation mode 2=PER_AREA screen ID='sablcm' XREFTEXT='-*-'.
  • If lighting calculation mode is not none and depth cue mode is 2=ALLOWED , then only lighting calculation mode is applied.
  • Only polyhedron edge culling modes 1=NONE , 2=BOTH_BACK , 3=BOTH_FRONT , and 4=BOTH_BACK_OR_BOTH_FRONT are supported.
  • Polyline end type 2=ROUND is not supported.
  • Not all optional data is supported. See The IBM graPHIGS Programming Interface: Subroutine Reference screen
• High Performance Graphics Subsystem (Model 730, 8 bit or 24 bit), POWER GtO (8 bit or 24 bit), or POWER Gt4x (8 bit or 24 bit):
  • When drawing a wide line with a line type other than 1=SOLID_LINE , the line end type is always 1=FLAT screen ID='xplee' XREFTEXT='-*-'.
  • On the POWER Gt4x, the specified end type is ignored for lines of width <=5 pixels. These lines are drawn "stacked" on top of each other, so that the lines resemble a parallelogram with the ends always being verticle.

Non-Direct Window Access (non-DWA) Capabilities on the RS/6000 ONLY:

• The advanced rendering attributes are not supported.

• Color Graphics Display Adapter:
  • Only polyhedron edge culling mode 1=NONE is supported.

XSOFT

• The advanced rendering attributes are supported.

6090

• The lighting calculation modes supported depend on the hardware configuration of your workstation. Use the Inquire Advanced Attribute Facilities (GPQAAF) subroutine to obtain the lighting calculation modes supported on your workstation. 
• When an end type of 2=ROUND or 3=SQUARE is applied to wide lines, only a line type of 1=SOLID_LINE is supported. 

Table 49. Advanced Attribute Facilities - X Workstation Default Values

Table 50. Advanced Attribute Facilities Default Values

General Input Facilities

This section provides a description of the input device classes and the associated input trigger capabilities and echo characteristics. For each supported device, the triggers are listed in the order the workstation processes them (from the highest number secondary trigger proceeding toward and ending with the primary trigger).

If the cursor controller is not in the echo area of an active device, an asterisk '*' indicates the position of the input device. However, if a user-defined cursor from the cursor shape table is in use, there is no change in the appearance of the cursor when it leaves the echo area.

The default echo color on all workstations is white. The default prompt/echo on all workstations is type=1.

X and XSOFT

General Information Applying to All Adapters:

• The number of available triggers, the range of qualifiers of your cursor controller or stylus, and the number of valuator logical, choice logical, button physical and scalar physical input devices supported depend on the hardware configuration of your workstation. If you do not have the lighted program function keys (LPFKs) installed, then trigger type 1 is not available. 
• Fixed cursor type -1 (cross hair) extends to the limits of the graPHIGS API window.
• The cursor shape table has two predefined shapes that are defined as follows:
  • Entry 1 contains a cursor shape of a pointing hand.
  • Entry 2 contains a cursor shape of a pointing arrow.
• Input character sets 1-5 and 7 are supported through character set 8 (multi-language).
• You can set the number of locator devices via the Locator Devices (LOCDEVS ) procopt. (See "LOCDEVS (Locator Devices)")screen ID='xloc' XREFTEXT='-*-'. To set the number of string devices, use the String Devices (STRDEVS ) procopt. (See "STRDEVS (String Devices)")screen ID='xstrg' XREFTEXT='-*-'.
• The IBM 6094 Dial Model 10 and the IBM 6094 LPFKs Model 20 are supported through the Graphic Input Device Adapter (2810) and its attachment cable (4015). These dials and LPFKs are also supported through the serial port adapter (4060) and the direct attachment (4061).
• X workstations running with AIX 3.2 support a mouse or tablet attachment, but not both. If both are physically attached, the tablet is ignored.
• Engineering symbols are defined in the graPHIGS API font files for character sets 6 (Japanese Katakana), 8 (Multi-Language), and 9 (Single-byte Korean), although no keyboard engineering symbols are engraved on the RS/6000 keyboard. These engineering symbols are available for input through the Alt + key sequence for English, Japanese, and Korean language environments, and the Alt-Gr + key sequence for European language environments.

  The graPHIGS API determines your language environment and keyboard from the AIX environment variable LANG screen The following tables shows how the engineering symbols map to the keyboard for a given set of LANG variable values and X keysym values. Table 51 shows these symbols for AIX 3.2, and Table 52 shows these symbols for AIX 3.1. For LANG variable values not listed, the En_US (U.S. English) mapping is the default.
  

  Table 51. Available Keysyms for Completion of Engineering Symbol Sequence / AIX 3.2 and AIX 4.1
  

  LANG
  En_US	q	w	e	r	t	y	u	i	o	a	s	d
  En_GB	q	w	e	r	t	y	u	i	o	a	s	d
  De_DE	f	w	engr	r	t	z	u	m	o	a	s	d
  Fr_FR	a	z	engr	r	t	y	u	engr	o	q	s	d
  It_IT	q	w	engr	r	t	y	u	i	o	a	s	d
  En_JP	q	w	e	r	t	y	u	i	o	a	s	d
  Sv_SE	q	w	e	r	t	y	u	i	o	a	s	d
  ko_KR	q	w	e	r	t	y	u	i	o	a	s	d
  Nl_BE Fr_BE	a	z	e,engr	r	t	y	u	i,engr	o	q	s	d
  De_CH Fr_CH	q	w	e,engr	r	t	z	u	i	o	a	s	d
  zh_TW zh_CN	q	w	e	r	t	y	u	i	o	a	s	d

  
  

  Table 52. Available Keysyms for Completion of Engineering Symbol Sequence / AIX 3.1
  

  LANG
  En_US	q	w	e	r	t	y	u	i	o	a	s	d
  En_UK	q	w	e	r	t	y	u	i	o	a	s	d
  Gr_GR	f	w	engr	r	t	z	u	m	o	a	s	d
  Fr_FR	a	z	engr	r	t	y	u	engr	o	q	s	d
  It_IT	q	w	engr	r	t	y	u	i	o	a	s	d
  En_JP	q	w	e	r	t	y	u	i	o	a	s	d
  Sv_SV	q	w	e	r	t	y	u	i	o	a	s	d
  Gr_BE	q	w	e	r	t	y	u	i	o	a	s	d
  Du_BE Fr_BE	a	z	e,engr	r	t	y	u	i,engr	o	q	s	d
  Fr_SW Gr_SW	q	w	e,engr	r	t	z	u	i	o	a	s	d
  Note: When an engineering symbol is engraved on the keyboard (indicated by engr), the engineering symbol measure follows the key sequence as indicated on the key top, not necessarily the Alt keysym or Alt+Gr keysym sequence.

  The keysyms degree, mu, and plusminus exist in the X11 keysym definitions and can be considered to correspond to the engineering symbols they best represent. Since you can map these keysyms to any key position you want, the engineering symbols follow these keysym definitions to their mapped position.

  To map the keys on a keyboard to a specific language keyboard engraving, use the X utility, xmodmap screen Language key map files can be found in the directory

  /usr/lpp/X11/defaults/xmodmap/<=LANG>
  =

  The file, keyboard, corresponds to the RS/6000 default mapping. The file, keyboard.alt, if it exists, corresponds to the 5080 default mapping.
• For character set 6 (Katakana) the engineering symbols defined by keysyms may not be remapped. Also, if the keyboard is mapped to a language in which the engineering symbols correspond only to engraved positions on a keyboard (such as degree for French keyboards), then the engineering symbols are not available in a Katakana character set.
• On the PS/2, Kanji (character set identifier 128), Hangul (character set identifier 129), Simplified Chinese (character set identifier 132) and Traditional Chinese (character set identifier 130) are not available.
• On the PS/2, dials and Lighted Program Function Keys (LPFKs) are not available.

6090

• The qualifiers supported by your cursor controller or stylus depends on the hardware configuration of your workstation. 
• Fixed cursor type -1 (cross hair) extends to the limits of the screen.
• The cursor shape table has two predefined shapes that are defined as follows:
  • Entry 1 contains a cursor shape of a pointing hand.
  • Entry 2 contains a cursor shape of a pointing arrow.
• Input character sets 1-5 and 7 are supported through character set 8 (multi-language).
• For input Kanji, the primary character set must be set to Katakana through the customization panel.

5080

• The number of available triggers, the range of qualifiers of your cursor controller or stylus, and the number of valuator logical, choice logical, button physical and scalar physical input devices supported depend on the hardware configuration of your workstation. If you do not have the lighted program function keys (LPFKs) installed, then trigger type 1 is not available. 
• The number of available input character sets depend on the configuration of your workstation. 
• Use the IBM 5080 Japanese Language Feature to assign input to either Kanji (character set identifier 128) or Katakana (character set identifier 6). Use the IBM 5080 Korean Language Feature to assign input to Hangul (character set identifier 129). 
• Traditional Chinese (character set identifier 130) is not supported.
• Simplified Chinese (character set identifier 132) is not supported.

GDDM

• The number of stroke logical, choice logical, string logical, and button physical input devices supported depend on the hardware configuration of your workstation. 
• 3=EVENT mode input from GDDM-supported workstations must be handled differently by the graPHIGS API from EVENT mode input from asynchronous workstations.

  A synchronous interface is used to obtain input from a workstation. GDDM issues a WAIT for input, and no other processing can be done until the I/O has been received from the workstation. If an application has several workstations open simultaneously, some of which are asynchronous and some of which are GDDM-supported, then a call to Await Event (GPAWEV) only waits for event input from the asynchronous workstations.

  If only GDDM-supported workstations are open and have input devices in EVENT mode, then GDDM is called to process the AWAIT I/O processing. In this case, the time-out value in the await event is ignored as GDDM waits until an I/O operation is completed. If several GDDM-supported workstations are open with input devices in EVENT mode, event input is solicited from the workstations in the order that they were opened by the application.

• The input device echo is not clipped to the echo area on GDDM workstations.

Table 53. General Input Facilities - X Workstation Default Values

Table 54. General Input Facilities Default Values

Table 55. Available Cursor Definition Formats for X

Table 56. Available Cursor Definition Formats for the 6090

Available Triggers

Table 57. Available Triggers for X

 
1) Cursor controller button #1
   is released or stylus tip switch is released
2) Cursor controller button #2
   is released
3) Cursor controller button #3
   is released
4) Cursor controller button #4
   is released
5) Cursor controller button #1
   is pressed down or stylus tip switch down
6) Cursor controller button #2
   is pressed down
7) Cursor controller button #3
   is pressed down
8) Cursor controller button #4
   is pressed down

Table 58. Available Triggers for the 6090

 
1) Cursor controller button #1
   is released or stylus tip switch is released
2) Cursor controller button #2
   is released
3) Cursor controller button #3
   is released
4) Cursor controller button #4
   is released
5) Cursor controller button #1
   is pressed down or stylus tip switch down
6) Cursor controller button #2
   is pressed down
7) Cursor controller button #3
   is pressed down
8) Cursor controller button #4
   is pressed down

Table 59. Available Triggers for the 5080

1) Cursor controller button #1
   is released or stylus tip switch is released
2) Cursor controller button #2
   is released
3) Cursor controller button #3
   is released
4) Cursor controller button #4
   is released
5) Cursor controller button #1
   is pressed down or stylus tip switch down
6) Cursor controller button #2
   is pressed down
7) Cursor controller button #3
   is pressed down
8) Cursor controller button #4
   is pressed down

Table 60. Available Triggers for GDDM

Locator Devices

Only one locator device is provided by default. For those workstations that support up to two locator devices, use the Locator Devices (LOCDEVS ) procopt to modify the number of locators. See "LOCDEVS (Locator Devices)"screen ID='xginol' XREFTEXT='-*-'.

Locator devices do not have secondary triggers. For most workstations, the primary trigger defaults to the release of the buttons on the puck.

The default echo area supported depends on the maximum display surface of your workstation. The maximum display surface changes with various display hardware. Use the Inquire Default Locator Device Data (GPQDLC) subroutine to obtain the default echo area of your workstation. 

X, and XSOFT

General Information Applying to All Adapters:

• Attributes specified in the data record are ignored for locator input echo attributes (GPINLC).
• Locator Echo Type 7 (structure drag) ignores color and interior attributes specified in the structure network.
• The default high qualifier and available trigger types depend on the hardware configuration of your workstation. If you do not have lighted program function keys (LPFKs) installed, then trigger type 1 is not available. 

6090

• The color attribute is ignored for locator input echo attributes (GPINLC).

5080

• All attributes are ignored for locator input echo attributes (GPINLC).
• The default high qualifier and available trigger types depend on the hardware configuration of your workstation. If you do not have lighted program function keys (LPFKs) installed, then trigger type 1 is not available. 
• Locator Echo Type 7 (structure drag) drags pixel primitives by setting all of the pixels to the echo color.

GDDM

• If a mouse or tablet is configured (they are mutually exclusive), this is the locator device. If no mouse or tablet is configured, the cursor keys are used. The locator device trigger is not programmable. The Enter key and the PF keys act as the triggers.
• The locator echo area may not be changed and defaults to full screen.
• All attributes are ignored for location input echo attributes (GPINCL)screen

Table 63 provides the default triggers for locator devices, which include releasing any of the four cursor controller buttons or releasing the stylus tip switch.

Table 61. Locator Logical Devices - X Default Values

Table 62. Locator Logical Devices Default Values

Table 63. Locator Trigger Types

Stroke Devices

There are two types of stroke devices:

• Stroke device #1 is the streaming stroke device and has two secondary triggers.
  • Secondary trigger #2 initiates the accumulation of stroke points into the stroke buffer.
  • Secondary trigger #1 ends the accumulation of points into the stroke buffer.

  By default, the primary trigger corresponds to the same event as the secondary trigger #1. Therefore, upon the release of a cursor control button, accumulation of input stops and input is fired to the application.

• Stroke device #2 is a discrete stroke device and has four secondary triggers that act upon the point at the edit position.

  The edit position can be from 0 to n+1 where 0 refers to the position before the first stroke point and n+1 refers to the position after the last stroke point. The four secondary triggers act as follows:

  • Secondary trigger #4 deletes the point at the edit position and moves the edit position backward one point (that is, toward the first point in the list).

    If the list is not empty and the edit position is neither before the first point nor after the last point, this trigger deletes the point at the edit position. If the edit position is not before the first point, this trigger moves it back one.

  • Secondary trigger #3 inserts the point identified by the current cursor location into the list after the edit position and moves the edit position forward one point (that is, toward the last point in the list).

    If there are fewer points in the list than the application will accept, it inserts the new point into the list. Otherwise, this trigger sounds the alarm and does not change either the buffer or the edit position.

    If the edit position is not beyond the end of the list, this trigger moves all points above the current point up one, opening the slot above the current point. It inserts the new point in that slot and advances the edit position to the new point.

    If the edit position is beyond the end of the list, this trigger appends the new point to the list and leaves the edit position unchanged (that is, pointing at the new point).

  • Secondary trigger #2 moves the edit position forward one point (that is, toward the last point in the list).

    If the list is not empty and the edit position is not after the last point, this trigger moves the edit position.

  • Secondary trigger #1 moves the edit position backward one point (that is, toward the first point in the list).

    If the list is not empty and the edit position is not before the first point, this trigger moves the edit position.

When the echo method uses polylines or polymarkers and the edit position is within the range 1-n, the current point is indicated with a diamond around the point.

When the echo method uses polylines and the edit position is 0 or n+1, a rubberband line is displayed from the first or last stroke point to the current cursor position.

The time interval parameter in the Initialize Stroke (GPINSK) data record is ignored.

The default echo area supported depends on the maximum display surface of your workstation. The maximum display surface changes with various display hardware.  Use the Inquire Default Stroke Device Data (GPQDSK) subroutine to obtain the default echo area of your workstation.

The default high qualifier and available trigger types depend on the hardware configuration of your workstation. If you do not have lighted program function keys (LPFKs) installed, then trigger type 1 is not available. It also depends on the number of mouse buttons provided. 

X, and XSOFT

General Information Applying to All Adapters:

• The color attribute is ignored for stroke input echo attributes (GPINSK).

6090, 5080

• The color attribute is ignored for stroke input echo attributes (GPINSK).

GDDM

• Stroke device #1 is only available if a mouse or tablet is configured. When a mouse or tablet button is pressed, the stroke device is activated and points are sampled at fixed intervals. Pressing a mouse or puck button or stylus switch a second time deactivates the device and suspends stream sampling. You can only trigger this device when it is not accumulating points.

  The data record, the editing position, and the echo area are not evaluated. Only the first point of the initial stroke is displayed.

• Stroke device #2 is only available if a mouse or tablet is configured. One stroke point is sampled each time a mouse or puck button or stylus switch is pressed.

  The data record, the editing position, and the echo area are not evaluated. Only the first point of the initial stroke is displayed.

Table 64. Stroke Logical Devices - X Default Values (Stroke 1 and 2)