GDDM V3R2 Base Application Programming Guide
|
Previous topic |
Next topic |
Contents |
Index |
Contact z/OS |
Library |
PDF |
BOOK
Overlapping partitions GDDM V3R2 Base Application Programming Guide SC33-0867-01 |
|
You can overlap partitions. Partitions are opaque, so the part of a partition that is overlapped by another partition is completely obscured by the top partition. The next example contains the skeleton code to produce a partition that overlaps another partition:
________________________________________________________________________
PARTLAP: PROC OPTIONS(MAIN);
________________________________________________________________________
A program based on the above skeleton program produced the screen output
shown in Figure 125. All that is added to the program is the alphanumeric
code for the panel in partition 1, the graphics calls to produce the chart
in partition 2, and the code to draw a line around the border of each
partition.
The PTSCRT call at A defines the partition-set grid, using the parameters in SET_ARRAY. The PTNCRT call at B creates partition 1, using the parameters in P1_ARRAY. This partition fills the screen. The PTNCRT call at C creates partition 2, using the parameters in P1_ARRAY. These parameters place the top-left-hand corner of partition 2 in row 5 and column 3. The advantages of overlapping partitions are:
If you specify on the PTSCRT call that partitions can overlap, you always get emulated partitions (even when the partitions do not actually overlap) on all devices including those that support real partitions. Partitions are also always emulated when user control or operator windows are available. A display showing a partition containing a business graphics chart in one partition overlapping on another partition that contains the data from which the chart is composed. |
Copyright IBM Corporation 1990, 2012 |