Cluster Alignment in QDESIGN

[Murray Scholz]

Here's a QDESIGN query, concerning how to organise a cluster (vertical),
so
that maximum use of an 80-column screen layout is achieved with three
columns
of data.

Code segment is...

 temp t-fld1 char*11 occurs 30
 temp t-fld2 char*8 occurs with t-recip
 temp t-fld3 char*2 occurs with t-recip

 align (1,,4)(,,16)(,,25)
 cluster occurs with t-fld1 vertical for 1,26
 field t-fld1
 field t-fld2
 field t-fld3
 cluster

Which produces the following layout...

07 xxxxxxxxxxx xxxxxxxx xx17 xxxxxxxxxxx xxxxxxxx xx27 xxxxxxxxxxx
xxxxxxxx xx
08 xxxxxxxxxxx xxxxxxxx xx18 xxxxxxxxxxx xxxxxxxx xx28 xxxxxxxxxxx
xxxxxxxx xx
09 xxxxxxxxxxx xxxxxxxx xx19 xxxxxxxxxxx xxxxxxxx xx29 xxxxxxxxxxx
xxxxxxxx xx
10 xxxxxxxxxxx xxxxxxxx xx20 xxxxxxxxxxx xxxxxxxx xx30 xxxxxxxxxxx
xxxxxxxx xx
11 xxxxxxxxxxx xxxxxxxx xx21 xxxxxxxxxxx xxxxxxxx xx31 xxxxxxxxxxx
xxxxxxxx xx
12 xxxxxxxxxxx xxxxxxxx xx22 xxxxxxxxxxx xxxxxxxx xx32 xxxxxxxxxxx
xxxxxxxx xx
13 xxxxxxxxxxx xxxxxxxx xx23 xxxxxxxxxxx xxxxxxxx xx33 xxxxxxxxxxx
xxxxxxxx xx
14 xxxxxxxxxxx xxxxxxxx xx24 xxxxxxxxxxx xxxxxxxx xx34 xxxxxxxxxxx
xxxxxxxx xx
15 xxxxxxxxxxx xxxxxxxx xx25 xxxxxxxxxxx xxxxxxxx xx35 xxxxxxxxxxx
xxxxxxxx xx
16 xxxxxxxxxxx xxxxxxxx xx26 xxxxxxxxxxx xxxxxxxx xx36 xxxxxxxxxxx
xxxxxxxx xx

Which is fine, and uses 78 (3x26) columns of the screen.

Now, in order to draw two vertical lines between the columns of
fields/data , I
need to have a gap between the end of fld-3 and the ID# of the next
column,

But as soon as the cluster statement is modified to say "for 1,27"....
(which
is what you would normally do to introduce an inter-column space),
QDESIGN
complains with the message
      *E* The screen limit has been exceeded.
      *W* This cluster may be incomplete.
(3x27 is greater than 80).

I can see its point !!, but I don't need the 'inter-column gap' at the
end of the
third row; I just want to have a gap between rows one and two.  I just
want to
'fully utilize' the entire 80-column screen.

Unfortunately I cannot reduce the size of any of the field items, nor do
I want
to split my table up into two 'part-tables', one part being occurs 20,
then a
'second part' being occurs 10... then have two different clusters on the
screen.... etc. etc.  Doing this makes the procedural code in the screen
a nightmare.

If someone has handled this situation in the past, I'd appreciate their
ideas.

Murray Scholz
Agricultural Business Research Institute
University of New England
Armidale NSW 2351 Australia
(ps. Environment is Powerhouse 710G1 on OpenVMS 6.2 or 7.1 if it's
relevant)
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
powerh-l@lists.swau.edu is gatewayed one-way to bit.listserv.powerh-l
This list is closed, thus to post to the list, you must be a subscriber.