Re: Window border display attributes mess up overlaid display

On Wed, Aug 9, 2017 at 9:20 AM, Charles Wilt <charles.wilt@xxxxxxxxx> wrote:

In my experience, funky windows come from them being to small.

Interesting. I should note that I am using the same display record
definitions in the service program's display file as they exist in the
legacy applications (maintenance programs with prompt screens/logic
included in the program), and we have never had this problem in the legacy
applications. The one window in the service program is 11 lines x 80
columns. Not sure how big is big enough.

Make it a bit bigger and make sure you've got at least 2 (?) characters

from the window border to the start or end of any field.

Yeah, see, we use the *DFT option to let the system determine the
location. This is even more important in a service program that will be
called by multiple programs for which the field being prompted may be in
different locations. I thought about passing the x,y coordinates from the
calling program to try what you're suggesting, but that would be a
maintenance nightmare.

- Dan