Skip to main content
  • Home
  • Documentation
  • FAQ
  • Downloads
  • Support
  • Current Release Notes
  • Ferret Users Guide
    • Users Guide Index
    • Commands Reference
    • 1. Introduction
    • 2. Data Set Basics
    • 3. Variables & Expressions
    • 4. Grids & Regions
    • 5. Animations & Gif Images
    • 6. Customizing Plots
    • 7. Handling String Data Symbols
    • 8. Working with Special Data Sets
    • 9. Computing Environment
    • 10. Converting to NetCDF
    • 11. Writing External Functions
    • Glossary
    • Appendix A: Functions
    • Appendix B: PPLUS Guide
    • Appendix C: Ferret-Specific PPLUS Enhancements
  • Previous Release Notes
  • Tutorials and Demos
    • Ferret Tour
    • DSG files: Discrete Sampling Geometries Demo
    • Ferret sorting demo
    • Fast Fourier Transforms demo
    • Empirical Orthogonal Functions demo
    • Ferret objective analysis demo
    • Ferret Palette Demo
    • Map projections
    • Ferret polygon vector demo
    • Ferret Graticules demo
    • Ferret Polytube Demo
    • Ferret Polymark Demo
    • Ferret Constant-Array demo
    • Ferret land_detail demo
    • COADS Tour
    • Levitus Tour
    • Use OPeNDAP
    • Ferret binary read demo
  • PyFerret
    • PyFerret Downloads and Install ../../faq/ferret-faqs.html
    • What is PyFerret?
    • Why use PyFerret?
    • PyFerret for the Ferret user
    • PyFerret command syntax: quick-start notes
    • PyFerret for the Python user
    • Graphics in PyFerret ?
    • New Ferret functionality
    • PyFerret Python functions and constants
    • PyFerret Python objects and methods
    • Ferret external functions in Python
    • Ferret Fortran external functions
    • PyFerret metadata-and-data dictionaries
  • OPeNDAP
    • OPeNDAP usage in Ferret
    • Use OPeNDAP Demo
    • Test OPeNDAP

GKS LINE BUNDLES

Appendix C Sec3

GKS LINE BUNDLES

GKS employees the concept of line bundles, where lines may be referred to by an index; the index determines the three characteristics of plotted lines, namely, line type, thickness, and color. Line type means whether the line is solid, dotted, dashed, dashed-dotted, etc. Thickness is measured in units beginning with one; two is twice as thick as one, followed by three, three times as thick. Colors are selected using a color index; the color associated with an index can be set using the PPL+ COLOR command.

The values of these characteristics together determine the line representation. One result of bundle use is that the same line bundle index may be defined to have different representations on different devices.

On X Windows devices color is usually used to distinguish lines; in that case the line type is always solid. When Postscript hard copy is made from PPL+ metafiles, lines may be rendered as color, but on monochrome printers the only available color is black. Consequently, when output is to a monochrome printer, gksm2ps uses differing line types to distinguish lines instead of color. Lines of differing thickness are available in both PPL+ X Window output and hard copy.

The table below presents the line thickness, color index and associated default color for color devices (assuming a white background), and line type for monochrome devices, for the 19 line bundles in PPL+. On color devices, the default color of line index 1 is black if the background is white, and white if the background is black; line bundle index 19 is the background color (the color index is 0).

Bundle index

Thickness

Color

Line type (Monochrome devices)

1

1

1, black

solid

2

1

2, red

dashed

3

1

3, green

dotted

4

1

4 , blue

dashed-dotted

5

1

5, cyan

long dashed

6

1

6, magenta

dashed and double-dotted

7

2

1, black

solid

8

2

2, red

dashed

9

2

3, green

dotted

10

2

4, blue

dashed-dotted

11

2

5, cyan

long dashed

12

2

6, magenta

dashed and double-dotted

13

3

1, black

solid

14

3

2, red

dashed

15

3

3, green

dotted

16

3

4, blue

dash-dotted

17

3

5, cyan

long dashed

18

3

6, magenta

dashed and double-dotted

19

1

0, white