Re: Window erasing background screen issue with service program

Does your window program understand if it is displaying on DS3 or DS4?  Part of the issue may be that it doesn't know how to put a DS4 window on a DS3 screen so it just blows away the underlying screen?

Are you retrieving the screen size?

DSPF:

**

*DSPSIZ(*DS3 *DS4) R FMT001 90 DSPMOD(*DS4) -------------------------------------------------------------------- RPGLE: *

**

**

*d SetScreenSize pr 10i 0 extproc('QsnRtvScrDim') d NbrRows 10i 0 options(*omit) d NbrCols 10i 0 options(*omit) d Handle 10i 0 options(*omit) d ErrorCode 32767 options(*varsize: *omit) d NbrColumns s 10i 0 ... // =============================================================== // == Mainline == // =============================================================== /free //check current screen size, configure to match SetScreenSize(*omit:NbrColumns:*omit:*omit); if nbrColumns = 132; *in90 = *on; else; *in90 = *off; endif;*

**


On 7/19/2018 4:23 PM, Paul Therrien wrote:

My window display file is *DS3 and *DS4.

And the window program displays the QCMD screen in the background when i
call it directly from the command line.

For testing the service program I have an RPG program that only and
simply invokes a procedure in the service program and the service
program then invokes the window program. In this scenario the QCMD
screen is erased when the window is displayed.

Both the Service program and the window RPG program are in activation
group QILE.

I am stumped.

Paul

On 2018-07-19 16:45, Carel wrote:

Well, QCMD is a *DS3 (24*80) screen.

And tour window is also *DS3?

If not, the background turns black and does not show the first screen the window was displayed on, as a background.

Kind regards,

Carel Teijgeler

Op 19-7-2018 om 21:28 schreef Paul Therrien: I am currently in development mode so I am calling the test program
directly from a command line.

In one instance I am calling the window program directly from the
command line.

in the other instance I am calling an rpg program from the command line
that executes a procedure in a service program that invokes the window
program.

So in both cases the underlying screen is QCMD.

Paul

On 2018-07-19 15:18, Carel wrote:

Does the previous screen has a different format then the new screen? *DS3 v. *DS4.

Kind regards,

Carel Teijgeler

Op 19-7-2018 om 15:33 schreef Paul Therrien:

I have a window display program that, when called directly, the window
pops and the screen behind remains on the display. - All good.

When I call this same program from within a service program the window
pops, but the screen behind is erased; so all i see is the window, with
a blank screen behind.

The window operates fine in both circumstances, it is the erasing of the
screen behind the window that is an issue.

Is there a way to retain the screen data behind from within a service
program?

Am I, again, misunderstanding something?

Thanks for any help.

Paul