Re: Display window causing a blank screen

The new display window works when called from "format 1", but not from
"format 2", so I was looking in the wrong places for the problem.

The format displayed when the window program is called and displays
correctly has:
A R COETOO1A
A N18 CF01
<lots of similar records snipped>
A 87 CF09
A RTNCSRLOC(&CSRREC &CSRFLD)
A BLINK
A 69 ALARM
A CSRLOC(CROW CCOL)
A OVERLAY

This is the format displayed when the window program is called and blanks
out the screen has:
A R COETOO12
A N56 CF02
<lots of similar records snipped>
A CF10
A KEEP
A RTNCSRLOC(&CSRREC &CSRFLD)
A BLINK
A 69 ALARM
A CSRLOC(CROW CCOL)

I took the KEEP keyword out of COETOO12 and still had the blank screen (as
expected) on the called window. I added the KEEP to COETOO1A and the
windows still display correctly with the COETOO1A display still visible
behind the window.

Does this give anyone any ideas?

In summary, a called program window when format COETOO1A is displayed,
displays correctly. The same called program window when format COETOO12 is
displayed, displays the window with a blank screen behind it. This makes me
think the problem is with the record format in the calling program.

Mark Plank

On Fri, Jun 3, 2011 at 11:44 AM, J M Plank <plank.computer@xxxxxxxxx> wrote:

I think I've been looking in the wrong places for the problem. I copied a
working display file window and renamed it to the problem window. This
window also causes the blank screen. So, I'm thinking the problem is in the
calling program, not in the called window.

Since windows display correctly when called from "format 1", I'll see if
this window displays correctly when it is called from that, rather than
"format 2".

Mark Plank


On Fri, Jun 3, 2011 at 10:52 AM, J M Plank <plank.computer@xxxxxxxxx>wrote:

A coworker is having problems getting a window to display properly. I
know we are missing something obvious. There is an interactive program with
a display file that can call other programs with windows. The problem is
with the called program and window. All the existing windows display
properly, but the new window blanks out the screen behind it. I've checked
the archives and Googled this, and had lots of hits - everything I've read
we either have in the code or tried unsuccessfully (which means we are
likely overlooking the obvious).

The calling program has two different record formats used when the windows
are called. Format 1 is used for the calls to existing programs with
windows that display correctly. Format 2 calls the new program which has
the window with the blank screen. The only difference I see between them is
that format 2 has the KEEP keyword. I've taken it out with the same result,
and added it to format 1, and the called windows there still display
correctly.

The new window has one field. The existing windows either have subfiles
or multiple fields, but I don't think that has any bearing on the problem.

We've compared the source for two correctly displaying windows to the
source for the new window and nothing obvious jumps out at us.

All the display files have RSTDSP *YES.

The new display file has the following record format (not called):
A R DUMMY
A ASSUME
A 15 1' '

This is the record format displaying with a blank screen:
A R DISPLAYR

A OVERLAY

A WINDOW(3 6 8 32)
<== (also used WINDOW(*DFT 8 32)
A KEEP

A WDWBORDER((*COLOR RED) (*DSPATR
RI)-
A (*CHAR ' '))

A USRRSTDSP

We have the same result with the overlay keyword removed, and with both
the KEEP and USRRSTDSP keywords removed.

This existing window displays correctly, even without the KEEP and
USRRSTDSP keywords. But the calling program uses Format 1 instead of Format
2.
A R COETCM01

A OVERLAY

A WINDOW(*DFT 11 60)

A WDWBORDER((*COLOR RED) (*DSPATR
RI)-
A (*CHAR ' '))


Any ideas of what else we should be looking for?

Thanks.
Mark Plank
Maple Leaf Farms
Milford, IN