Design: 04.02.02.02/P12

This is an abstract, language-independent design. Grim details may be found in the corresponding source code. You may return to the documentation for the module containing this program design, or to the entire hierarchical table of topics covered by the PVT.


PROGRAM 12: Network inheritance and initialization of polymarker
            index

CHARACTERISTICS: ynny

OPERATOR SCRIPT:

STRUCTURE NETWORK INHERITANCE FOR POLYMARKER INDEX: This screen
displays several left-right pairs of polymarkers.  Make sure that
all pairs except one have matching marker types, marker size, and
colors.  Identify the non-matching pair.

DESIGN:

All test cases use same basic structure network for testing
inheritance.  Five (distinct if possible) values for the
attribute to be tested are set up and propagated throughout the
network.  The first value is the system default from the PDT.
Note that structure #104 is executed by both #103 and #101.
Actual results are displayed on the left, expected results
on the right, with the 14th deliberately made incorrect.

default = val#1
  |                  102
  |                 /  prim 2
  |               /    attr = val#3   val#3
  V        val#1/      exec 103---------------103
101           /        prim 8                   prim 3
  prim 1    /                                   attr = val#4
  exec 102/                                     prim 4
  prim 9                                        exec 104\
  attr = val#2                                  prim 7    \ val#4
  prim 10                                                   \
  transform             val#2                                 \
  exec 104-----------------------------------------------------104
  un-transform                                                   prim 5/11
  prim 13                                                        attr = val#5
  prim 14                                                        prim 6/12
  exec 105---------->105
                       expected values

*** *** ***   inheritance for polymarker index *** *** ***

use <inquire polymarker facilities> to determine:
  nummt  = number of marker types
  nummw  = number of available marker sizes
  nommw  = nominal marker size (DC)
  minlw,maxlw = minimum,maximum marker size (DC)

get alternative marker size value:
altmw1 should not exceed .05 (WC) to avoid overlap - distance
  between markers will be 1/15 = .06666

call DISCOL to try to get 5 distinct foreground colors,
  returning fcol = actual number of foreground colors
colind[1..5] = [1,2,3,4,5]
if (fcol < 5) then
   copy 1st valid part of list to tail of list
endif

set up bundles 1-5

   bundle
   index     marker type marker size  color index
   ------    --------    ---------    -----------
     1          1          1.0        colind(1)
     2          2          altmw1     colind(2)
     3          3          1.0        colind(3)
     4          4          altmw1     colind(4)
     5          5          1.0        colind(5)

randomize location of polymarkers
set up CSS as described above
set all ASFs to BUNDLED

display 14 pairs of polymarkers, using bundles 1-5

TEST: #SR 3 5 6 8 9
      "The polymarker index should be saved and restored by
       <execute structure> during traversal."

OPQA/STRUCTURE NETWORK INHERITANCE FOR POLYMARKER INDEX:
  which pair of markers does NOT match?
pass/fail depending on response = position of polymarker 14

END PROGRAM 12